paulmking
commented
4 years ago I would not want to change the prex-respin2 branch to be code and settings that we did not use for prex-respin2. Alternately, pulling the changes from prex-respin2 (or develop) into crex-respin1 may be sensible.
This is an intermediate step along the way to a full CREX respin 1 branch. As such I'd suggest merging it onto PREX respin 2 deployment and just running with it from there. It really is only the last few commits, as crex-respin1 branch was already merged into develop before the PREX respin 2 was performed.
I noticed that the data handlers that were in use during CREX running were still in that configuration (switching from 4aX to 1X analysis midway though the run), which is a bit concerning and indicates there may still be some prompt-era choices that need to be smoothed out for respinning (I thought we'd done so already). This change will need to be back propagated to the beginning of CREX to give us a comparative dataset, which I have gone ahead and done in this branch. I think this change would even be good to merge into the adaq/prompt deployment, as our online plotting scripts are now capable of smoothing out inconsistent device lists, which was the only concern for back-propagating map file updates previously.