Website build

Author: colinjcotter

Computationallinearalgebracourse.pdf

@@ -682,7 +682,7 @@ <h2><span class="section-number">2.6. </span>Householder triangulation<a class="
 done so, you will need to modified
 <a class="reference internal" href="cla_utils.html#cla_utils.exercises3.householder" title="cla_utils.exercises3.householder"><code class="xref py py-func docutils literal notranslate"><span class="pre">cla_utils.exercises3.householder()</span></code></a> to use the <code class="docutils literal notranslate"><span class="pre">kmax</span></code>
 argument. You may make use of the built-in triangular solve
-algorithm <a class="reference external" href="http://scipy.github.io/devdocs/reference/generated/scipy.linalg.solve_triangular.html#scipy.linalg.solve_triangular" title="(in SciPy v1.8.0.dev0+1756.0364a40)"><code class="xref py py-func docutils literal notranslate"><span class="pre">scipy.linalg.solve_triangular()</span></code></a> (we shall consider
+algorithm <a class="reference external" href="http://scipy.github.io/devdocs/reference/generated/scipy.linalg.solve_triangular.html#scipy.linalg.solve_triangular" title="(in SciPy v1.8.0.dev0+1775.93c7e94)"><code class="xref py py-func docutils literal notranslate"><span class="pre">scipy.linalg.solve_triangular()</span></code></a> (we shall consider
 triangular matrix algorithms briefly later). The test script
 <code class="docutils literal notranslate"><span class="pre">test_exercises3.py</span></code> in the <code class="docutils literal notranslate"><span class="pre">test</span></code> directory will also test this
 function.</p>
@@ -794,7 +794,7 @@ <h2><span class="section-number">2.7. </span>Application: Least squares problems
 appropriate augmented matrix <span class="math notranslate nohighlight">\(\hat{A}\)</span>, calling
 <a class="reference internal" href="cla_utils.html#cla_utils.exercises3.householder" title="cla_utils.exercises3.householder"><code class="xref py py-func docutils literal notranslate"><span class="pre">cla_utils.exercises3.householder()</span></code></a> and extracting appropriate
 subarrays using slice notation, before using
-<a class="reference external" href="http://scipy.github.io/devdocs/reference/generated/scipy.linalg.solve_triangular.html#scipy.linalg.solve_triangular" title="(in SciPy v1.8.0.dev0+1756.0364a40)"><code class="xref py py-func docutils literal notranslate"><span class="pre">scipy.linalg.solve_triangular()</span></code></a> to solve the resulting upper triangular
+<a class="reference external" href="http://scipy.github.io/devdocs/reference/generated/scipy.linalg.solve_triangular.html#scipy.linalg.solve_triangular" title="(in SciPy v1.8.0.dev0+1775.93c7e94)"><code class="xref py py-func docutils literal notranslate"><span class="pre">scipy.linalg.solve_triangular()</span></code></a> to solve the resulting upper triangular
 system, before returning the solution <span class="math notranslate nohighlight">\(x\)</span>. The test script
 <code class="docutils literal notranslate"><span class="pre">test_exercises3.py</span></code> in the <code class="docutils literal notranslate"><span class="pre">test</span></code> directory will also test this
 function.</p>

L2_QR_factorisation.html

@@ -20,7 +20,7 @@ Setting up your repository
 
 We're using a tool called `GitHub classroom <https://classroom.github.com>`_ to automate the creation of your
 copies of the repository.
-To create your repository, click `here <https://classroom.github.com/a/OY_NHMeU>`_.
+To create your repository, click `here <https://classroom.github.com/a/RDyDLTSf>`_.
 
 
 Cloning a local copy
@@ -88,9 +88,7 @@ build the :doc:`cla_utils` web documentation.
 As you do the exercises, **commit your code** to your repository. This
 will build up your computational exercise solution sets. You should
 commit code early and often - small commits are easier to understand
-and debug than large ones. **Never** commit back to the ``master``
-branch of your fork, that should always remain a clean copy of the
-main repository.
+and debug than large ones.
 
 Pull requests for feedback
 --------------------------

_sources/exercises.rst.txt

@@ -63,7 +63,7 @@ <h2>Obtaining the skeleton code<a class="headerlink" href="#obtaining-the-skelet
 <h3>Setting up your repository<a class="headerlink" href="#setting-up-your-repository" title="Permalink to this headline">¶</a></h3>
 <p>We’re using a tool called <a class="reference external" href="https://classroom.github.com">GitHub classroom</a> to automate the creation of your
 copies of the repository.
-To create your repository, click <a class="reference external" href="https://classroom.github.com/a/OY_NHMeU">here</a>.</p>
+To create your repository, click <a class="reference external" href="https://classroom.github.com/a/RDyDLTSf">here</a>.</p>
 </section>
 <section id="cloning-a-local-copy">
 <h3>Cloning a local copy<a class="headerlink" href="#cloning-a-local-copy" title="Permalink to this headline">¶</a></h3>
@@ -124,9 +124,7 @@ <h2>How to do the computational exercises<a class="headerlink" href="#how-to-do-
 <p>As you do the exercises, <strong>commit your code</strong> to your repository. This
 will build up your computational exercise solution sets. You should
 commit code early and often - small commits are easier to understand
-and debug than large ones. <strong>Never</strong> commit back to the <code class="docutils literal notranslate"><span class="pre">master</span></code>
-branch of your fork, that should always remain a clean copy of the
-main repository.</p>
+and debug than large ones.</p>
 </section>
 <section id="pull-requests-for-feedback">
 <h2>Pull requests for feedback<a class="headerlink" href="#pull-requests-for-feedback" title="Permalink to this headline">¶</a></h2>