fix: forgot to rebuild website again :(

Author: cosmic-cortex

build/doctrees/content/examples/Active-regression.doctree

@@ -20,7 +20,7 @@ For this example, we shall try to learn the *noisy sine* function:
 Uncertainty measure and query strategy for Gaussian processes
 -------------------------------------------------------------
 
-For active learning, we shall define a custom query strategy tailored to Gaussian processes. More information on how to write your custom query strategies can be found at the page `Extending modAL <../overview/Extending-modAL>`__. In a nutshell, a *query stategy* in modAL is a function taking (at least) two arguments (an estimator object and a pool of examples), outputting the index of the queried instance and the instance itself. In our case, the arguments are ``regressor`` and ``X``.
+For active learning, we shall define a custom query strategy tailored to Gaussian processes. More information on how to write your custom query strategies can be found at the page `Extending modAL <../overview/Extending-modAL.html>`__. In a nutshell, a *query stategy* in modAL is a function taking (at least) two arguments (an estimator object and a pool of examples), outputting the index of the queried instance and the instance itself. In our case, the arguments are ``regressor`` and ``X``.
 
 .. code:: python
 

build/doctrees/content/examples/Ensemble-regression.doctree

@@ -25,8 +25,7 @@ For the sake of this example, we are going to learn the *noisy absolute value* f
 Measuring disagreement with CommitteeRegression
 -----------------------------------------------
 
-If you have several regressors, measuring disagreement can be done by calculating the standard deviation of the predictions for each point. This of course cannot be achieved with classifier algorithms, where averaging the class labels doesn't make sense. (Or it is undefined even, if the class labels are strings for example.) In the simplest setting, this is implemented in the function
-``modAL.disagreement.max_std_sampling``. For more details on this, see the `disagreement sampling API reference <Disagreement-sampling-API>`__.
+If you have several regressors, measuring disagreement can be done by calculating the standard deviation of the predictions for each point. This of course cannot be achieved with classifier algorithms, where averaging the class labels doesn't make sense. (Or it is undefined even, if the class labels are strings for example.) In the simplest setting, this is implemented in the function ``modAL.disagreement.max_std_sampling``.
 
 This measure is default for CommitteeRegressors, so we don't need to specify this upon initialization.
 

build/doctrees/environment.pickle

@@ -195,7 +195,7 @@ <h2>The dataset<a class="headerlink" href="#the-dataset" title="Permalink to thi
 </div>
 <div class="section" id="uncertainty-measure-and-query-strategy-for-gaussian-processes">
 <h2>Uncertainty measure and query strategy for Gaussian processes<a class="headerlink" href="#uncertainty-measure-and-query-strategy-for-gaussian-processes" title="Permalink to this headline">¶</a></h2>
-<p>For active learning, we shall define a custom query strategy tailored to Gaussian processes. More information on how to write your custom query strategies can be found at the page <a class="reference external" href="../overview/Extending-modAL">Extending modAL</a>. In a nutshell, a <em>query stategy</em> in modAL is a function taking (at least) two arguments (an estimator object and a pool of examples), outputting the index of the queried instance and the instance itself. In our case, the arguments are <code class="docutils literal notranslate"><span class="pre">regressor</span></code> and <code class="docutils literal notranslate"><span class="pre">X</span></code>.</p>
+<p>For active learning, we shall define a custom query strategy tailored to Gaussian processes. More information on how to write your custom query strategies can be found at the page <a class="reference external" href="../overview/Extending-modAL.html">Extending modAL</a>. In a nutshell, a <em>query stategy</em> in modAL is a function taking (at least) two arguments (an estimator object and a pool of examples), outputting the index of the queried instance and the instance itself. In our case, the arguments are <code class="docutils literal notranslate"><span class="pre">regressor</span></code> and <code class="docutils literal notranslate"><span class="pre">X</span></code>.</p>
 <div class="code python highlight-default notranslate"><div class="highlight"><pre><span></span><span class="k">def</span> <span class="nf">GP_regression_std</span><span class="p">(</span><span class="n">regressor</span><span class="p">,</span> <span class="n">X</span><span class="p">):</span>
     <span class="n">_</span><span class="p">,</span> <span class="n">std</span> <span class="o">=</span> <span class="n">regressor</span><span class="o">.</span><span class="n">predict</span><span class="p">(</span><span class="n">X</span><span class="p">,</span> <span class="n">return_std</span><span class="o">=</span><span class="kc">True</span><span class="p">)</span>
     <span class="n">query_idx</span> <span class="o">=</span> <span class="n">np</span><span class="o">.</span><span class="n">argmax</span><span class="p">(</span><span class="n">std</span><span class="p">)</span>

build/html/_sources/content/examples/Active-regression.rst.txt

@@ -198,8 +198,7 @@ <h2>The dataset<a class="headerlink" href="#the-dataset" title="Permalink to thi
 </div>
 <div class="section" id="measuring-disagreement-with-committeeregression">
 <h2>Measuring disagreement with CommitteeRegression<a class="headerlink" href="#measuring-disagreement-with-committeeregression" title="Permalink to this headline">¶</a></h2>
-<p>If you have several regressors, measuring disagreement can be done by calculating the standard deviation of the predictions for each point. This of course cannot be achieved with classifier algorithms, where averaging the class labels doesn’t make sense. (Or it is undefined even, if the class labels are strings for example.) In the simplest setting, this is implemented in the function
-<code class="docutils literal notranslate"><span class="pre">modAL.disagreement.max_std_sampling</span></code>. For more details on this, see the <a class="reference external" href="Disagreement-sampling-API">disagreement sampling API reference</a>.</p>
+<p>If you have several regressors, measuring disagreement can be done by calculating the standard deviation of the predictions for each point. This of course cannot be achieved with classifier algorithms, where averaging the class labels doesn’t make sense. (Or it is undefined even, if the class labels are strings for example.) In the simplest setting, this is implemented in the function <code class="docutils literal notranslate"><span class="pre">modAL.disagreement.max_std_sampling</span></code>.</p>
 <p>This measure is default for CommitteeRegressors, so we don’t need to specify this upon initialization.</p>
 </div>
 <div class="section" id="active-regression">