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

Compare with Current View Page History

« Previous Version 4 Current »

The overall goal of the VLA QA criteria is to create a 'fast' vs. 'slow' lane dichotomy. In this scenario, fast could go through to accept and archive without needed to look at specific stages, while slow lane would go through the standard, in-depth weblog review that has typically accompianied the 'SRDP treatment' of VLA EBs. Precise QA scoring is not necessarily required, but could be helpful, in general anything that triggers slow lane should make the score drop below 0.5.

  1. hifv_importdata
    1. Include a plot of the API data during the observation
      1. if API or wind missing or out of spec, trigger slow lane
    2. Check for missing scans
      1. always look at
    3. If flux.csv is used, always triggers slow lane
  2. hifv_hanning
    1. simple QA, it either worked or didn't; automatic score of 0 if hanning smooth didn't work for some reason
  3. hifv_flagdata
    1. if a flag template use, always triggers low land
    2. look for endtime = 0 in flag.xml (can pipeline do this?)
      1. look for '1858/' in online flags - trigger slow lane
    3. clipping > 1% with spectral line windows
    4. clipping > 5% with only continuum windows
    5. total flagging >30% 
  4. hifv_setjy
    1. QA score of zero if no flux calibrator intent or non-standard flux calibrator
  5. hifv_priorcals
    1. add API information to the weather plot here
    2. weather station not functioning
    3. missing switched power data
    4. TEC maps presence can be safely ignore
  6. hifv_syspower
    1. >50% of all dataoutside the 0.7-1.2 range per band
    2. needs per Baseband selection syntax for mixed 8 and 3 bit setups
  7. hifv_testBPdcals
    1. >4 antennas have a DTS issue
      1. indicates bad reference antenna
    2. median delay per BB > 15 ns
  8. hifv_checkflag (both for bpdcal and allcals)
    1. > 75% of data flagged
  9. hifv_semifinalBPdcals
    1. remove warnings for single antenna and single spw being completely flagged
    2. if delays > 15 ns per baseband give a warning
    3. some number of spws on some number of antennas newly flagged gets a warning
  10. hifv_solint
    1. short solint > long solint
    2. calculated median calibrator scan time, if long solint > 1.5x the median calibrator scan time provide warning
      1. fix gain calibrator long solint calculation (refine what's already in the pipeline using medians rather than means)
  11. hifv_fluxboot
    1. >50% of spws are fully flagged in the flux gain table
    2. >50% of all data flagged
    3. spindex > +/- 5
    4. flux scale fails on 1 calibrator out of several
    5. look for unity in CGC model column (indicator of flux density not being measured
  12. hifv_finalcals
    1. suppress the per spw flagging warnings
    2. delays>15ns
    3. very little TOS on BP calibrator left in gains vs. time for BP cal
      1. very low amps in some BBs/spws?
    4. BB for antenna has high phase spread (indicative of DTS that got through)
    5. phase scatter of short solint vs. long solint to determine coherence
      1. warn if >2 antennas have < 0.6 coherence on average
    6. look for large > 50 degree phase jumps between scans on the same complex gain calibrator
      1. would be nice to tie this in to API information
    7. high or low gains for whole polarization or >=2/3 spws in a single BB per polarization
  13. hifv_applycals
    1. have a cumulative table
    2. have a table per band
    3. in each table break out by CGC and target(s)
    4. >85% of data flagged
    5. >30% additional data flagged per target or CGC
    6. jumping of flagging of target > CGC
  14. hifv_checkflag(target)
    1. huge amount of additional flagging
    2. >10% antennas have excessive flagging deltas
    3. lose whole BB or high res. spectral windows completely
  15. hifv_statwt
    1. gigantic weights
      1. mean > 1,000,000
      2. when variance goes to scientific notation in weblog(explicit OOM? 10^4?)
    2. high weights
      1. individual weights > 150
    3. high variance
      1. variances > 1000*mean
      2. variance in scientific notation (need to know when)
    4. high increase in flagging
      1. current scoring may be based on flagging and need ot understand what is happening currently
    5. heuristic development to flag outliers would be desirable
    6. per-field/per-spw weight characterizations may be necessary too
  16. hifv_plotsummary
    1. devidations >10% of mean in amp vs. freq
      1. for > X% of the data ~10%?
      2. per spw, per antenna
    2. phase spread vs. freq - implies resolved calibrator
      1. plot of real vs. imaginary instead?
        1. round=ok, point-like
        2. structured = resolved
  • No labels