QC documentation system: QC procedure qc_DARK for VIRCAM

This documentation is intended both for QC scientists and SciOps astronomers (who may want to ignore the technical information displayed in grey).
 
HOME
 
CRIRES
FORS1
FORS2
KMOS
NACO
 
GIRAFFE
UVES
XSHOOTER
 
ISAAC
SPHERE
VIMOS
VISIR
 
HAWKI
MUSE
SINFONI
 
AMBER
GRAVITY
MIDI
PIONIER
 
ESPRESSO
 
OMEGACAM
VIRCAM
[best viewing with style sheets and javascript enabled]
qc_RESET qc_GAIN qc_LINE qc_CURRENT
qc_DARK qc_DOME qc_TWIL qc_STD
 
bottom  plots   |   contact
NAME qc_DARK.sh
VERSION 1.0 -- 2006-10-11
2.0 -- 2008-06-10
2.1 -- 2009-12-17, reference frames read from AB
3.0 -- 2010-01-27, docu updated for start of operation
3.1 -- 2017-08-30, docu updated
SYNTAX SHELL
CALL called by processQC
from $DFS_PRODUCT/DARK/$DATE:
CALL_SYNTAX DARK 0000.fits &&qc_DARK -a $AB -u vircam -e 0 -level 3 2\>\&1 \> $DFS_LOG/$AB.qclog&&
INSTRUMENT VIRCAM
RAWTYPE DARK
PURPOSE quality control script for VIRCAM DARK product frames
-level 0 : Reads QC parameters from product fits headers and writes them into the QC1 DB.
-level 1 : Fits a Gaussian to the histogram of the product to obtain robust median and rms.
-level 2 : Generates a QC graphical report.
-level 3 : Generates a hot pixel map,
a cold pixel map, a deviant pixel map, and a deviant product.
level 3 includes all steps of level 2, level {n} includes all steps of level {n-1}. This shell script calls a number of python scripts.
PROCINPUT There are three command line paramaters:
-a {AB}
-e {extensions}
-level {processing category}
use -e -1 for final QC processing requirering all detectors (equivalent to joinAB)
use -e 0 to process all extension sequentially (1..16) and thereafter the QC that requires all extension
This means using -e 0 is the same as calling one after the other with -e 1 .. -e 16 and thereafter one call with -e -1
a) -e 1..16 -level 0 : for an individual extension do : writeQC
b) -e 1..16 -level 1 : for an individual extension do : writeQC + histogram fit
c) -e 1..16 -level 2 : for an individual extension do : writeQC + histogram fit + QC report
d) -e 1..16 -level 3 : for an individual extension do : writeQC + histogram fit + QC report + extras
where extras are the number of hot pixels, the number of cold pixel and th the number of deviant pixel
e) -e -1 -level 0 : writeQC -m AVERAGE
f) -e -1 -level 1 : writeQC -m AVERAGE
g) -e -1 -level 2 : writeQC -m AVERAGE
h) -e -1 -level 3 : writeQC -m AVERAGE + extras
where extras are : generate a hot a cold and a deviant pixel map as fits product
REFERENCE_DARK DIFFIMG_DARK products are read from the AB.
QC1TABLE trending | table(s) in QC1 database:
vircam_dark
TRENDPLOT trending | HealthCheck plot(s) associated to this procedure:
trend_report_DARKMED_1_10011_AVG_HC.html | trend_report_DARKMED_1_120_AVG_HC.html | trend_report_DARKRMS_1_10011_AVG_HC.html | trend_report_DARKRMS_1_120_AVG_HC.html | trend_report_STRIPERMS_1_10011_AVG_HC.html | trend_report_STRIPRMS_1_120_AVG_HC.html | trend_report_RON12_1_10011_AVG_HC.html | trend_report_RON12_1_120_AVG_HC.html
QC1PAGE trending | associated documentation:
qc_VC_dark.html
QC1PLOTS
top

masterdark.png
master dark product, snapshot from SkyCat
differencedark.png
difference dark product, snapshot from SkyCat
dark_qcreport_0.png
QC report for individual detector
UL: cross sections of the MASTER_DARK
UC: cross section of the MASTER_DARK
UR: histogram and fit of the MASTER_DARK
LL: cross section of the DIFFIMG_DARK
LC: cross section of the DIFFIMG_DARK
LR: image of the DIFFIMG_DARK

dark_qcreport_1.png
QC report for individual detector
UL: stripe pattern, cross section of raw darks
UC: zoom view
QC1PARAM QC1 parameters generated by pipeline and written into QC1 table and scored:
The many more QC1 parameters ingested into the QC1 DB, that do not show up in any HC plot and are not score, are not listed here.
NameInHeader, DBNAME , typical value, description:
QC.DARKMED qc_darkmed
QC.DARKRMS qc_darkrms RMS of master dark (measures FPN)
QC.STRIPERMS qc_stripe_rms
QC1 parameters generated by qc_DARK and written into QC1 table:
DBNAME , typical value, description:
qc_post_man , dark median from histogram fit
qc_post_mdm , dark stddev from histogram fit
qc_num_hp , number of hot pixel
qc_num_cp , number of cold pixel
qc_num_dp , number of deviant pixel
qc_dev_mean , mean of all pixel deviations
qc_dev_std , stdev of all pixel deviations
qc_ron12 , RON from (raw2 minus raw1)
, (the only script-based QC parameter, that is scored)
qc_ron23 , RON from (raw3 minus raw2)
qc_ron34 , RON from (raw4 minus raw3)
qc_ron45 , RON from (raw5 minus raw4)
ALGORITHM Description of algorithms:
qc_darkmed, median, for details, see the pipeline manual
qc_darkrms, MAD, for details, the see pipeline manual
qc_stripe_rms rms from single detector, for details, the see pipeline manual
qc_postman, fit MASTER_DARK density histogram by Gaussian, get mu
qc_postmdm, fit MASTER_DARK density histogram by Gaussian, get sigma
qc_num_hp, qc_num_cp, qc_num_dp, number of hot cold and deviant pixel
qc_dev_mean, fit DEVIANT product density histogram by Gaussian, get mu
qc_dev_std, fit DEVIANT product density histogram by Gaussian, get sigma
qc_ron12, qc_ron23, qc_ron34, qc_ron45, read noise from consecutive raw frames
CERTIF NONE
COMMENTS The aggregate (AVG and RMS over 16 detectors) values of only four QC parameters are scored. (see score report):
median, rms, ron and stripes
The read out noise of the detector can not be measured.
The value of qc_ron12 is composed of the detector read noise plus the variations of the stripes.
The stripe_rms turned out to be less significant for strong stripes events than the qc_ron12.
Thresholds are documented in the plot tutorial.
top [2022-02-28T08:09:47]         created by qcDocu v1.1.2, a tqs tool