@IanHeywood pointed out the following useful scenario which needs to be supported:
FLAG/FLAG_ROW is copied to "legacy" bitflag as usual
CubiCal is run in solve-only (perhaps rebinned mode), generates solutions, and outputs some new flags into the "cubical" parset, but doesn't touch FLAG/FLAG_ROW
CubiCal is run in apply-correct mode -- but now we want legacy+cubical to go into FLAG/FLAG_ROW
Step 3 is not presently supported (as CubiCal only updates FLAG/FLAG_ROW if new flags are generated), but should be easy to add. Perhaps as --flags-save-legacy apply.
@IanHeywood pointed out the following useful scenario which needs to be supported:
FLAG/FLAG_ROW is copied to "legacy" bitflag as usual
CubiCal is run in solve-only (perhaps rebinned mode), generates solutions, and outputs some new flags into the "cubical" parset, but doesn't touch FLAG/FLAG_ROW
CubiCal is run in apply-correct mode -- but now we want legacy+cubical to go into FLAG/FLAG_ROW
Step 3 is not presently supported (as CubiCal only updates FLAG/FLAG_ROW if new flags are generated), but should be easy to add. Perhaps as --flags-save-legacy apply.