minor

docs/index.html

@@ -7518,6 +7518,7 @@
 </div><div class="jp-RenderedHTMLCommon jp-RenderedMarkdown jp-MarkdownOutput" data-mime-type="text/markdown">
 <h1 id="PHYSICS-267:-Statistical-Methods-in-Astrophysics">PHYSICS 267: Statistical Methods in Astrophysics<a class="anchor-link" href="#PHYSICS-267:-Statistical-Methods-in-Astrophysics">¶</a></h1><p>All about Stanford University graduate course Physics 267, Fall 2024 edition.</p>
 <p>(Prior to this year, the course was numbered 366. This renumbering does not reflect any change in content or rigor.)</p>
+<p><strong>Note:</strong> Due to a late-breaking change in file organization, there may be a number of broken links between internal pages (excepting links from the front page). It should always be clear in context what page is being referred to, and it should be possible to get there from here.</p>
 </div>
 </div>
 </div>
@@ -7538,7 +7539,7 @@ <h3 id="Additional-quick-links">Additional quick links<a class="anchor-link" hre
 <li><a href="https://explorecourses.stanford.edu/search?view=catalog&amp;filter-coursestatus-Active=on&amp;page=0&amp;catalog=&amp;academicYear=&amp;q=physics267&amp;collapse=">Stanford course catalog entry</a></li>
 <li><a href="https://canvas.stanford.edu/courses/198587">Canvas site</a></li>
 <li><a href="https://drive.google.com/drive/folders/1XHFb-RKXuJ2-wvn4SVZmenhe5YIW4_Y1?usp=share_link">Google drive</a> (for tutorial notebooks)</li>
-<li><a href="https://drive.google.com/file/d/1Xsahog9pETHXqJLTlMSAc6OI2l8VGRVV/view?usp=sharing">Tentative schedule</a></li>
+<li><a href="https://drive.google.com/file/d/1Xsahog9pETHXqJLTlMSAc6OI2l8VGRVV/view?usp=sharing">Tentative schedule</a> (see Canvas for the official schedule)</li>
 <li><a href="notes/getting_started.html">Getting Started</a> and <a href="tutorials/demo/demo.html">Demo tutorial</a></li>
 </ul>
 </div>

docs/notes/syllabus.html

@@ -7611,7 +7611,7 @@ <h3 id="Class-participation">Class participation<a class="anchor-link" href="#Cl
 <ul>
 <li>promoting questions - we <em>all</em> have questions when seeing something new, and it's usually pointless to forge ahead without addressing them. Asking provides all of us the opportunity to pause, consider and digest, rather than blundering forward with misconceptions intact, and then having to find our way back later. (This includes the ur-question, which goes, "Wait... could you explain that again?")<a href="#Note-1">$^1$</a></li>
 <li>avoiding interrupting or talking over others - it can take more or less time to turn thoughts into words, especially when trying to simultaneously absorb new information. Before inserting yourself into or diverting a discussion, check whether others are still engaged with the last point.</li>
-<li>being respectful - while of course you <em>are</em> respectful, we all sometimes need a little reminder of how to best interact with others. We especially like the description of the "lightweight social rules" of the <a href="https://www.recurse.com/manual#sec-environment">Recurse Center</a>, since linking to it allows us to keep this bullet list relatively short.</li>
+<li>being respectful - while of course you <em>are</em> respectful, we all sometimes need a little reminder of how to best interact with others. We especially like the description of the "lightweight social rules" of the <a href="https://www.recurse.com/manual#sub-sec-social-rules">Recurse Center</a>, since linking to it allows us to keep this bullet list relatively short.</li>
 </ul>
 </div>
 </div>
@@ -7653,7 +7653,7 @@ <h3 id="Tutorials">Tutorials<a class="anchor-link" href="#Tutorials">¶</a></h3>
 </ul>
 <p>It is not <em>strictly</em> necessary to answer non-code questions in the notebook itself, although we strongly encourage it. This will help you if you ever need to refer back to it, and will help us help you if you run into any problems.</p>
 <p>Tutorial notebooks will be turned in on Canvas. We encourage you to leave the outputs from a top-to-bottom run in the notebook file you submit. This is again not strictly required, but will help to identify any issues if something is incorrect.</p>
-<p>Like quizzes, tutorials are graded on a complete/not complete basis. The final due date for all tutorials is the last day of classes for the quarter (except for projects, which can be turned in during the exam period); until then they can be revised and resubmitted without penalty. We might send a submitted notebook back with a requested revision or fix required for it to be deemed complete (usually with some advice about how to proceed). However, please do not turn in notebooks that you <em>know</em> are not complete in order to get feedback from us. Reaching out on Slack or in class is much more efficient for all of us.</p>
+<p>Like quizzes, tutorials are graded on a complete/not complete basis. The final due date for all tutorials, including the project, is at the end of the quarter; until then they can be revised and resubmitted without penalty. We might send a submitted notebook back with a requested revision or fix required for it to be deemed complete (usually with some advice about how to proceed). However, please do not turn in notebooks that you <em>know</em> are not complete in order to get feedback from us. Reaching out on Slack or in class is much more efficient for all of us.</p>
 <p>While the final due date for completed tutorials is late, we do have a schedule of when we will collectively begin and review each tutorial (usually a week apart), and we require evidence of bona fide effort put in before the review date. The admittedly fuzzy term "bona fide effort" should be taken to mean substantial progress towards a complete notebook and/or attempts to get help with sticking points <em>before the last minute</em>. Very simply, you will not be able to participate effectively in the review if you are seeing the tutorial for the first time at that point.</p>
 <p>This might all sound intimidating, but our aim with these notebooks is to make them illuminating rather than onerous. We want you to get your hands dirty analyzing data, and as long as that happens we'll be happy. Given all this flexibility, and since everyone should have working and complete notebooks by the time we're done, we are not planning on providing "solutions". You can, however, find html pages showing the outputs of solved tutorials linked from the main github.io page, to compare your work to.</p>
 </div>
@@ -7689,7 +7689,7 @@ <h4 id="Use-of-generative-AI-and-other-internet-resources">Use of generative AI
 </div>
 <div class="jp-InputArea jp-Cell-inputArea"><div class="jp-InputPrompt jp-InputArea-prompt">
 </div><div class="jp-RenderedHTMLCommon jp-RenderedMarkdown jp-MarkdownOutput" data-mime-type="text/markdown">
-<h3 id="Course-schedule">Course schedule<a class="anchor-link" href="#Course-schedule">¶</a></h3><p>You can find a tentative schedule <a href="https://drive.google.com/file/d/1Xsahog9pETHXqJLTlMSAc6OI2l8VGRVV/view?usp=sharing">here</a>. You should interpret this as showing the recommended time to work on various reading and tutorials, with the last day for a given task being the class when we will discuss it. However, of necessity, Canvas shall be the ultimate arbiter of when things are due.</p>
+<h3 id="Course-schedule">Course schedule<a class="anchor-link" href="#Course-schedule">¶</a></h3><p>You can find a tentative schedule <a href="https://drive.google.com/file/d/1Xsahog9pETHXqJLTlMSAc6OI2l8VGRVV/view?usp=sharing">here</a>. You should interpret this as showing the recommended time to work on various reading and tutorials, with the last day for a given task being the class when we will discuss it. However, of necessity, Canvas shall be the ultimate arbiter of when things are due. If changes are necessary, the file linked above may not be updated</p>
 </div>
 </div>
 </div>

notes/syllabus.ipynb

@@ -95,7 +95,7 @@
     "**Classroom norms:** Regardless of the mode of communication involved, we expect everyone to contribute to a positive and collaborative culture by\n",
     "* promoting questions - we _all_ have questions when seeing something new, and it's usually pointless to forge ahead without addressing them. Asking provides all of us the opportunity to pause, consider and digest, rather than blundering forward with misconceptions intact, and then having to find our way back later. (This includes the ur-question, which goes, \"Wait... could you explain that again?\")[$^1$](#Note-1)\n",
     "* avoiding interrupting or talking over others - it can take more or less time to turn thoughts into words, especially when trying to simultaneously absorb new information. Before inserting yourself into or diverting a discussion, check whether others are still engaged with the last point.\n",
-    "* being respectful - while of course you _are_ respectful, we all sometimes need a little reminder of how to best interact with others. We especially like the description of the \"lightweight social rules\" of the [Recurse Center](https://www.recurse.com/manual#sec-environment), since linking to it allows us to keep this bullet list relatively short."
+    "* being respectful - while of course you _are_ respectful, we all sometimes need a little reminder of how to best interact with others. We especially like the description of the \"lightweight social rules\" of the [Recurse Center](https://www.recurse.com/manual#sub-sec-social-rules), since linking to it allows us to keep this bullet list relatively short."
    ]
   },
   {
@@ -130,7 +130,7 @@
     "\n",
     "Tutorial notebooks will be turned in on Canvas. We encourage you to leave the outputs from a top-to-bottom run in the notebook file you submit. This is again not strictly required, but will help to identify any issues if something is incorrect. \n",
     "\n",
-    "Like quizzes, tutorials are graded on a complete/not complete basis. The final due date for all tutorials is the last day of classes for the quarter (except for projects, which can be turned in during the exam period); until then they can be revised and resubmitted without penalty. We might send a submitted notebook back with a requested revision or fix required for it to be deemed complete (usually with some advice about how to proceed). However, please do not turn in notebooks that you _know_ are not complete in order to get feedback from us. Reaching out on Slack or in class is much more efficient for all of us.\n",
+    "Like quizzes, tutorials are graded on a complete/not complete basis. The final due date for all tutorials, including the project, is at the end of the quarter; until then they can be revised and resubmitted without penalty. We might send a submitted notebook back with a requested revision or fix required for it to be deemed complete (usually with some advice about how to proceed). However, please do not turn in notebooks that you _know_ are not complete in order to get feedback from us. Reaching out on Slack or in class is much more efficient for all of us.\n",
     "\n",
     "While the final due date for completed tutorials is late, we do have a schedule of when we will collectively begin and review each tutorial (usually a week apart), and we require evidence of bona fide effort put in before the review date. The admittedly fuzzy term \"bona fide effort\" should be taken to mean substantial progress towards a complete notebook and/or attempts to get help with sticking points _before the last minute_. Very simply, you will not be able to participate effectively in the review if you are seeing the tutorial for the first time at that point.\n",
     "\n",
@@ -162,7 +162,7 @@
    "source": [
     "### Course schedule\n",
     "\n",
-    "You can find a tentative schedule [here](https://drive.google.com/file/d/1Xsahog9pETHXqJLTlMSAc6OI2l8VGRVV/view?usp=sharing). You should interpret this as showing the recommended time to work on various reading and tutorials, with the last day for a given task being the class when we will discuss it. However, of necessity, Canvas shall be the ultimate arbiter of when things are due."
+    "You can find a tentative schedule [here](https://drive.google.com/file/d/1Xsahog9pETHXqJLTlMSAc6OI2l8VGRVV/view?usp=sharing). You should interpret this as showing the recommended time to work on various reading and tutorials, with the last day for a given task being the class when we will discuss it. However, of necessity, Canvas shall be the ultimate arbiter of when things are due. If changes are necessary, the file linked above may not be updated "
    ]
   },
   {