Is a short term, is this meant to be a proposal of a place for created pfsDesign files (in no matter what processes they are made by whom) to be stored, so that an operator can pick one up for next test/observation?

This is the location for the fpsActor, etc to search for pfsDesign files: the input pfsDesign files for the ICS. A place where there could be many more files than actually get observed. The place where the outputs from shuffle get put.

Thanks. So this is a replacement with /data/pfsDesign that was used during the September run in terms of storage place, and in addition things should be set up so that the software component can refer to to do its jobs.

We could keep using /data/pfsDesign/ instead of the more explicit /data/plan/pfsDesign/, but I do think we should separate the collection of "available" pfsDesigns from the ones which are actually moved to/guided on/observed.

Let's leave them as /data/pfsDesign for now.  In the longer run we might want to avoid having one flat directory, but it isn't obvious how to do this (e.g. there is no natural data associated with a calibration pfsDesign that we'll observe every year).

/data/pfsDesign is the location until further notice.