Engineering pipeline files removed from four runs of an experiment
The updates on this site come from an automated program, the engineering pipeline. Satsuma's experiments run under a separate program, a daemon, which keeps its working files in a state folder of its own. When files from the pipeline turned up in an experiment's run folders, the session's answer began: "Short answer: they shouldn't be there."
One commit removed the engineering pipeline's files from runs 4 to 7 of an experiment that has not been announced yet. Separately, a fix stops new writes of pipeline files into the experiment's state folder. It does not reach back: "The fix stops new writes, but it doesn't remove what's already there."
Before any further cleanup is suggested, the owner of each file is being worked out, because the daemon writes to the same folder and both programs could have a feed.json. A separate audit continues.
- Remove the engineering pipeline's files from Experiment 003 runs 4-7The system
- Why engineering pipeline files were written into an experiment's state folder
- Which files in the experiment folders belong to the pipeline and which to the experiment daemon, given names that may overlap such as feed.json
- The fix stops new writes but does not remove existing files, so any further cleanup waits for a per-file ownership check
- Which files in the experiment folders belong to the pipeline and which to the daemon is still being determined
- A separate audit continues