Looking down to the MCS actor, the file name is given by the getNextFilename function. This function calls gen2Actor in line 218.

This needs to be changed for Subaru:

• iic gets the visit from gen2
• iic sends visit= to fps for all the top-level commands (motor maps, convergence, etc.). iic already does that for SPS, btw.
• iic sends visit= and frame= down to mcs for each exposure.

getNextFilename is only for standalone testing.

This is actually slightly more involved than I stated. Because it is so informative to group data by action (motor map, convergence), cobraCharmer has been creating a directory for each of these, with subdirectories for PFxC and stack files, logs, and output files (.xml and the file versions of the opdb tables, mainly).

I think we should continue doing this. Which essentially boils down to telling the mcsActor where to save the PFxC files. For now I propose being explicit (path=/data/raw/$date/fps/$runName), though we could also send the name of the "run directory" (run=$runName) and use a/the butler to instantiate the file path.

I was wrong. Mcs should dumbly save PFxC files in /data/raw/mcs. They partition into runs nicely by visit. Fps can make structured directories separately, and can have symbolic links to the read data files.

We might want to add mcs commands to control the generation of the very useful stack image files – with 100 Mpix cameras it does pay to avoid round trips to disk over the network.

Basics done. Depends on unmerged opdb changes.

Merged at a2bb35a, tagged 1.5.0