github-actions[bot]
The wednesday cycle, Victor Alves's. Three steps: last session onto Canvas, next lecture released, next module published. - [ ] **Embed L10 on Canvas**, delivered Monday Sep 28, "The machine learning (ML) workflow III: Classification, experiment tracking and hyperparameter search/tuning". Notes: https://kitchingroup.cheme.cmu.edu/f26-06763/lectures/l10/notes.html . Deck: https://kitchingroup.cheme.cmu.edu/f26-06763/slides/l10/ . - [ ] **Release L13**, "Surrogates, physics-informed models, and uncertainty quantification", which meets Wednesday Oct 7. Notes, deck and quiz go public together, and it also releases nothing else. Quiz bank: will publish. - [ ] **Update the Canvas module for L13** with links to its notes (https://kitchingroup.cheme.cmu.edu/f26-06763/lectures/l13/notes.html) and deck (https://kitchingroup.cheme.cmu.edu/f26-06763/slides/l13/), then publish the module. Do this after the release PR has merged and CI has deployed, or the links will 404. > **L13 cannot be released yet.** Still held ahead of it: L12. A released lecture may cross-reference an earlier one, so publishing L13 first would fail the build. That is the other lane's release, so this cycle waits on it. ## Step 2, in commands ```bash git fetch origin && git checkout -b release-l13 origin/main # --check first if you want to see what it touches without changing anything python tools/release_lecture.py 13 # Verify locally the way CI will python game/validate.py python tools/world.py --check python tools/pool_archive.py --check jupyter-book build . --warningiserror git add -A && git commit -m 'Release Lecture 13' git push -u origin release-l13 ``` ## Worth knowing - **`git add -A` has to pick up `game/src/map/world.json`.** `release_lecture.py` regenerates it, and CI's `tools/world.py --check` fails the build if the regenerated map is not committed. - **A lecture with an empty quiz bank still releases**, notes, deck and all, and its map room opens with them. Only the practice module stays hidden, because the room follows `_toc.yml` and the module follows the bank's `status:`. Expect `stays held, no quiz written yet` for L6, L8, L10, L12, L14 and L16; re-run `release_lecture.py` for that lecture once its bank is written. - **Step 3 waits on the deploy.** CI publishes on merge to `main` and the `verify` job reads `https://kitchingroup.cheme.cmu.edu/f26-06763/build-info.json` back off the live site. A green build is not the same as a live page, so check that before pasting links into Canvas. - **Never** set `only_build_toc_files: false` or add `course/modules` to `_toc.yml`. That setting is the only thing keeping unreleased lectures off guessable URLs (CLAUDE.md sections 1 and 10). - To undo a release: re-comment its `_toc.yml` lines and any assignment line it uncommented, set the bank back to `status: unwritten`, and run `python tools/world.py --write`. Full procedure: [`RELEASING.md`](https://github.com/jkitchin/f26-06763/blob/main/RELEASING.md).