Execution Blocks:
Calibrations:
Calibration Conditions:
We require the ASDM(s) and the calibration products for an MOUS before we can process a restore. However, calibrations for ALMA are not considered official until there are archived images for them. Thus, we know that we can use a calibration for a restore when:
select count(*) from ALMA.ASA_PRODUCT_FILES where FILE_CLASS='science' and ASA_OUS_ID=?; > 0
and it is primarily a pipeline-calibration:
select count(*) from ASA_PRODUCT_FILES where ASA_OUS_ID='.....' and FILE_CLASS='script' and NGAS_FILE_ID LIKE '%scriptFor%Cal%'; == 0
then we can proceed. If both of these conditions are true, then the calibration_status can be set to 'Calibrated' (i.e. a restore is an option). Otherwise, the calibration_status should stay at 'Ready' which is already our default for ALMA data.
What was that second condition?
Some ALMA data requires manual intervention in order to calibrate correctly. The fraction of data for which this is required is fairly small by late Cycle 5 (15%?), but if there are indicators that our basic restore process won't work, the system should catch & report that fact early on, rather than running the pipeline and letting it fail. There is a more comprehensive methodology used at the Alma Regional Centers (ARCs), but they combine both restores & complete recalibrations. Those more complicated cases have been excluded from being restored in the AAT-PPI system.