WEEK 35 · LABDOCS, PART 3
This week the instruments start talking to each other. When batchlens raises an alarm (week 3), a QA person must write a deviation report: what happened, which SOP applies, what the corrective action is. labdocs drafts it: alarm + relevant SOP paragraph → draft → human approval → signed record in eLabFTW. The human stays in the loop, like a pilot who reviews the autopilot's plan before accepting it. Then the argumen…
THE NEXT BLOCK
Tuesday · after Es et al. (2023), "RAGAS: Automated Evaluation of Retrieval Augmented Generation"
Stanford CS224N lecture on retrieval/RAG (web.stanford.edu/class/cs224n; verify current lecture list) (30 min)
In: LABLOOP-W34 Notebook
By Sunday you should be able to say: “I can show an alarm becoming a signed deviation, and a table of what a lab can run without sending data anywhere." --- # ACT VIII · Peer review and the crossroads (weeks 36-40) > Act VIII story. The expedition comes home. The maps go to the geographical society, where reviewers you have never met will check them. You give the lecture. A fund asks whether you can survey all its territories at once. And at the end, standing at the crossroads, you decide where to settle: your own office with long-term clients, a salaried seat at a map-making company, or both. The decision is written down, because a decision in your head is a mood”
MOMENTUM
2026-09-29 18:29 Finished: SciPy docs, scipy.integrate.solve_ivp2026-09-29 17:44 Finished: LearnChemE (CU Boulder) · "Monod Cell Growth Example (Bio)"2026-09-28 22:11 Finished: Crash Course Biology #3 · "Biological Molecules2026-09-28 21:50 Finished: OpenStax Biology 2e2026-09-25 11:16 Finished: OpenStax Biology 2e