You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 34 Next »

Checklist for SRDP calibrations of VLA data, based heavily on the VLASS one.

Also relevant: requirements for the AQUAReport  SRDP-194 - Getting issue details... STATUS

Checklist (in order of pipeline stage), to be done after the initial pipeline run that is performed for all EBs:

  1. Overview of MS: check calibration of EB as executed is SRDP compliant (many of these problems may have been caught at the SB submission stage, but some observers may choose to ignore recommendations anyway). If any of the conditions below are violated the pipeline should be run only once and no SRDP QA should be set (jump to step 15):
    1. The EB uses only Ku-band or above for science.
    2. The project is A or B-ranked (check against list with link on this page - or just do all??)
    3. intents for bandpass, amplitude and gain calibration all present.
    4. the amplitude (flux) calibrator is appropriate for the frequency and configuration (i.e. a good model exists). See  https://science.nrao.edu/facilities/vla/docs/manuals/oss/performance/fdscale
    5. all science spw are calibrated
    6. all science spw are in the frequency range deemed in scope for SRDP (>12GHz for the pilot).
    7. gain calibrations are at appropriate intervals for the frequency being observed i.e. <10-60min <12GHz, <2-20min >12GHz, depending on configuration (see https://science.nrao.edu/facilities/vla/docs/manuals/obsguide/calibration#CalibrationCycle for details), and bracket the science observations.
    8. appropriate setup scans were performed: see https://science.nrao.edu/facilities/vla/docs/manuals/obsguide/set-up
    9. antenna reference pointing calibrations were performed for high frequency (>15GHz) observations.
  2. hifv_flagdata - online flags. Notify scientist if >20% flagged - maybe should be 35%?
  3. hifv_priorcals - check for gain compression due to severe RFI - is hifv_syspower part of the regular pipeline yet? If not, probably need to flag.
  4. hifv_testBDdcals - check for Data Transmission System (DTS) problems.
  5. hifv_flagbaddef - check that any DTS issues have been flagged.
  6. hifv_semiFinalBPdcals - check for any remaining DTS issues.
  7. hifv_solint - check solints for calibrators are reasonable (< a few mins for the long interval, > 0.05s for the short interval) - if in doubt check with a scientist.
  8. hifv_fluxboot2:
    1. check the input tables look clean 
    2. check that  the model is reasonable and covers all spw.
    3. make a note of the phase calibrator flux densities.
  9. hifv_finalcals:
    1. check for delay outliers
    2. check for unusual bandpass shapes
    3. check for outlying bandpass phases
    4. phase (short) gain solution: check for large phase scatter
    5. final amp/time: check for outliers
    6. final amp/freq: check that outliers fall into known bad spw
    7. Final phase - check there are no phase jumps > 90deg
  10. hifv_applycals: check end of CASA log and note final % flagged. If over 50%? check with a scientist
  11. hifv_plotsummary:
    1. phase vs time plots: check all are centered on zero
    2. amp vs uvwave:
      1. check calibrators are point-like (constant flux)
      2. check there is no evidence of decorrelation (strong "waterfall")
      3. check RFI is fully flagged
    3. amp vs frequency:
      1. check for residual RFI on calibrators
      2. check for residual RFI on targets
  12. Update google spreadsheet with run details
  13. Rerun with additional flagging if needed.
  14. Once satisfied, write a short overall evaluation suitable for archiving and transmission to the PI (no cuss words!)
    1. need a template for this
  15. Trigger archive ingest with appropriate SRDP QA level set (Pass/Fail/Null not SRDP compliant])
  16. Send user an email via the helpdesk? with the summary from step (14) and instructions on how to obtain their calibrated data.


  • No labels