QC documentation system: QC procedure dark

QC documentation system: QC procedure dark_red.prg for UVES

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
MIDI
PIONIER

OMEGACAM
VIRCAM
[best viewing with style sheets and javascript enabled]

bias_blue.prg	bias_red.prg	dark_blue.prg	dark_red.prg	zeroflat.prg
fmtcheck_blue.prg	fmtcheck_red.prg	orderdef_blue.prg	orderdef_red.prg	flat_blue.prg	flat_red.prg	wave_blue.prg	wave_red.prg
std_blue.prg	std_red.prg
fmtcheck_fib.prg	orderdef_fib.prg	sflat_fib.prg	fflat_fib.prg	wave_fib.prg

bottom plots | contact

NAME dark_red.prg

VERSION 1.5

SYNTAX MIDAS

CALL

from $DFS_PRODUCT/BIAS_RED/$DATE:
uves.MeasureQuality -a <AB> -c dark_red.prg [-i|--NOingestQC1pars]
where

<AB> is the Association Block

[-i] forces QC1 parameter ingestion (default)

[--NOingestQC1pars] prevents QC1 parameter ingestion

INSTRUMENT UVES

RAWTYPE DARK_RED & PDARK_RED

PURPOSE Comparison of raw, master and reference DARK and PARSITIC-DARK files for UVES QC assessment; QC1 values are calculated and fed into the QC1 table. QC1 plot(s) and/or display(s) are generated, and later reviewed within certifyProducts.
The generated plots stored in $DFO_PLT_DIR/$DATE with the name r.<DPid>_tpl_0000.fits.png where <DPid> is the Data Product Identification of the first frame of the template.

PROCINPUT first raw DARK frame from AB; MASTER_DARK_REDU & MASTER_DARK_REDL or MASTER_PDARK_REDU & MASTER_PDARK_REDL, and MASTER_BIAS_REDU & MASTER_BIAS_REDL from AB

QC1TABLE trending | table(s) in QC1 database:
uves_dark

TRENDPLOT trending | HealthCheck plot(s) associated to this procedure:
HEALTH/trend_report_DARK_SM_HC.html

QC1PAGE trending | associated documentation:
detmon_qc1.html

QC1PLOTS
top

dark_red.montage.png
A montage image made up of the following individual reports simply for the purposes of easier/better display in XV during the certification process. Created together with the reference montage (see below) within the uves.MeasureQuality script. Can be recreated manually by calling the script uves.makeQCreportMontage -a <AB>, see uves.makeQCreportMontage -h for more details.
dark_red.montage.ref.png
A montage image made up from the individual QC reports of the reference AB located by the script uves.getRefAB. During certification, the two montage images are blinked to facilitate identification of unusual features. This reference montage created at the same time as the AB montage (see above).The montage of the reference AB is easily identified during the blinking as the one with the grey background.
dark_red_0000.fits.png
box1: comparison of master DARK (red row, blue column) <-> raw DARK (black) <-> master BIAS (green); upper panel: LOWER chip, middle row and middle column, full pixel range, in ADU; lower panel: UPPER chip, middle row and middle column, full pixel range, in ADU;
box 2: histogram: all pixel values in log frequency histogram; raw DARK: black, master BIAS: green and red; there should be a dominant peak with Gaussian shape (which translates to parabola shape in this log freq diagram)
box 3: histogram: log frequency histogram; master DARK: upper panel: LOWER chip all pixel values; lower panel UPPER chip all pixel values, there should be a dominant peaks with Gaussian shapes (which translates to parabola shapes in this log freq diagram)
top panel: name of analyzed master DARK frame and name of the master BIAS frame used for comparison (and by the pipeline)
bottom panel: some template properties and QC1 parameters
dark_red_0000.fits_1.ima.png
full display of raw frame
dark_red_0000.fits_2.ima.png
full display of LOWER chip master frame (box: area to be displayed in bias_red_0000.fits_3.png)
dark_red_0000.fits_3.ima.png
closeup display of LOWER chip master frame
dark_red_0000.fits_4.ima.png
full display of UPPER chip master frame (box: area to be displayed in bias_red_0000.fits_5.png)
dark_red_0000.fits_5.ima.png
closeup display of UPPER chip master frame

ALGORITHM

Description of algorithms:
Algorithms for pipeline created keywords are (in principal) described in the pipeline user's manual

mean_raw: mean value of raw frame, this QC parameter is currently calculated by the QC report script, not by the pipeline.
Description: Not currently calculated, instead the value NULL is written into the table. Possibly because in the original implementation of the QC report the statistics area spanned the two chips, therefore the mean value calculated was not of either chip in particular, so not written.
mean_dark: mean value across master dark, this QC parameter is currently calculated by the QC report script, not by the pipeline.
Description: computed for each chip with the MIDAS command:
```
 stat/ima <PRO.CATG=MASTER_[P]DARK_RED[L|U]> [@1,@1:@{XEND},@{YEND}] bins=1 exc={lower_master},{upper_master}
```
XEND & YEND are the full sizes of the chips.
lower_master & upper_master are the min and max values of half of and twice the means of the central regions of the UPPER and LOWER MASTER DARK frames.
current_dark: mean_dark normalized to 3600 secs exposure time (i.e. ADU/hr), this QC parameter is currently calculated by the QC report script, not by the pipeline. Description: computed for each chip with the MIDAS command:
```
current_dark = mean_dark/EXPTIME*3600 
```
exptime: exposure time in secs., this QC parameter is taken directly from the header of the first RAW file, it propagates to the PRODUCT file(s) unchanged by the pipeline, product keyword EXPTIME.

CERTIF

Reasons for rejection:
For DARKs:

less than three frames in a DARK frame set
differing exposure times in the frame set (often because the last frame is stopped early)
very short exposure times (less than 1000sec, normal exposure time is 3600 sec, anything less than this is probably a TEST frame or similar)

PDARKs are never rejected as these are technical calibrations.
Remnants from previous 860nm wave calibratuion exposures are sometimes seen, especially in PDARKs which are normally single frames data-sets..

COMMENTS See also the PDARK trending plot here.

top [2015-10-30T08:20:36] created by qcDocu v1.1.2, a tqs tool