One project, several places#
Two students are studying how a beam bends. Their program and measurements are not the same kind of file, and the computer that runs a calculation need not be the place that keeps its result.
| Fictional item | Why the project needs it |
|---|---|
analyse.py |
Program both students will edit |
measurements.csv |
Approved input that must remain available |
| Working mesh | Replaceable file built for the calculation |
report.pdf |
Result the thesis must retain |
Before reading the steps, choose one item that could safely be recreated after its working copy disappears. What would you need to record to rebuild it? There is no file to upload for this question. The steps help you check your reasoning.
See a possible route through the project
Code is reviewed on GitHub from each student's separate clone. The approved input stays in its owner-approved durable store. A working copy can travel to an approved compute location; a scheduled job produces the result. The result returns to approved durable storage and is verified before working copies are cleaned. Blade supplies the approved Windows interface when needed; it is not a replacement for scheduled heavy compute or durable storage.
A folder called archive is still temporary if the service's lifetime rules say
so. Decide from ownership and retention, rather than a folder name or free space.