This documentation is intended both for QC scientists and SciOps astronomers (who may want to ignore the technical information displayed in grey).
|
|
|
|
|
bottom
plots
|
contact
|
|
NAME |
fmtcheck_blue.prg
|
|
VERSION |
2.3
|
|
SYNTAX |
MIDAS
|
|
CALL |
from $DFS_PRODUCT/BIAS_RED/$DATE:
uves.MeasureQuality -a <AB> -c fmtcheck_blue.prg [-i|--NOingestQC1pars]
where
<AB> is the Association Block
[-i] forces QC1 parameter ingestion (default)
[--NOingestQC1pars] prevents QC1 parameter ingestion
|
|
INSTRUMENT |
UVES
|
|
RAWTYPE |
FMTCHK_ECH_BLUE
|
|
PURPOSE |
Comparison of raw, master and/or reference FMTCHK_ECH_BLUE 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 |
RAW frame from AB; ORDER_GUESS_TAB_BLUE, LINE_GUESS_TAB_BLUE & BACKGR_TABLE_BLUE products
|
|
QC1TABLE |
trending | table(s) in QC1 database:
uves_fmtchk
|
|
TRENDPLOT |
trending | HealthCheck plot(s) associated to this procedure:
HEALTH/trend_report_ECH_FMTCHK_GratPos_PhysM_BLUE_346_2x3_DHC_HC.html
|
|
QC1PAGE |
trending | associated documentation:
fmtchk_qc1.html
|
|
QC1PLOTS
top |
fmtchk_ech_blue.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.
fmtchk_ech_blue.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.
fmtchk_ech_blue_0001.fits.png
From left to right, top to bottom:
plot 1:trace across the central row of the RAW frame
plot 2:trace across the central column of the RAW frame
plot 3:XDIFF vs YDIFF plot, where XDIFF & YDIFF are the differences measured positions of each line with respect to the positions expected from the physical model. Ideally the points in this plot should clusted about 0,0, but the pipeline seems capable to cope with deviations of upto -10,+10 in both axes (the pipeline developer expects 'problems' at values much larger than +/-10 however this range has not been 'explored' in normal operations). Jumps (of completely unpredicatable nature) are often seem in these parameters due to earthquakes and any other influence (e.g. maintenance/intervention operations) which 'disturb' the instrument. Jumps in BLUE and RED arms can be completely UNCORRELATED.
plot 4:Distribution of located lines by echelle order
plot 5:XDIFFs (as above) as a function of position along each order
plot 6:YDIFFs (as above) as a function of position along each order
fmtchk_ech_blue_0001.fits_1.ima.png
MIDAS display of the RAW frame with the located emission lines indicated by squares and all squares within a given order joined by a line.
fmtchk_ech_blue_0001.fits_2.ima.png
Same as previous but closeup of central region with lines indicated by crosses. Note also that the "joining lines" only show joined up to the points within the display, so short lines or orders without any points at all in the displayed central region does NOT indicated no points at all (or no more) in the order, outside the displayed region.
|
|
QC1PARAM |
QC1 parameters written into QC1 table:
QC1db names: lambda_min | lambda_max | order_min | order_max | mean_dx | sigma_dx | mean_dy | sigma_dy | median_shftx | median_shfty | nlin_all | nlin_sel | ins_temp4_mean | ins_temp1_mean | ins_press_mean
FITS key names: QC.WLENMIN | QC.WLENMAX | QC.ORDMIN | QC.ORDMAX | QC.MODEL.DIFFXAVG | QC.MODEL.DIFFXRMS | QC.MODEL.DIFFYAVG | QC.MODEL.DIFFYRMS | QC.SHFTXMED | QC.SHFTYMED | QC.MODEL.NLINALL | QC.MODEL.NLINSEL | INS.TEMP4.MEAN | INS.TEMP1.MEAN | INS.SENS26.MEAN
QC1 params created by pipeline: lambda_min | lambda_max | order_min | order_max | mean_dx | sigma_dx | mean_dy | sigma_dy | median_shftx | median_shfty | nlin_all | nlin_sel
QC1 params created by this procedure: None
|
|
ALGORITHM |
Description of algorithms: Algorithms for pipeline created keywords are (in principal) described in the pipeline user's manual
- lambda_min: minimum wavelength [Angstrom], product keyword QC.WLENMIN
Description: minimum wavelength
- lambda_max: maximum wavelength [Angstrom], product keyword QC.WLENMAX
Description: maximum wavelength
- order_min: minimum order number, product keyword QC.ORDMIN
Description: minimum order number detected
- order_max: maximum order number, product keyword QC.ORDMAX
Description: maximum order number detected
- mean_dx: difference of X positions to physical model, product keyword QC.MODEL.DIFFXAVG
Description: The physical model used in Formatcheck step allows
to measure the difference between model predicted
and detected line positions. This is useful to verify
precision of physical model prediction and instrument
spectral format stability.
- sigma_dx: rms of difference of X positions to physical model, product keyword QC.MODEL.DIFFXRMS
Description: The physical model used in Formatcheck step allows
to measure the difference between model predicted
and detected line positions. This is useful to verify
precision of physical model prediction and instrument
spectral format stability.
- mean_dy: difference of Y positions to physical model, product keyword QC.MODEL.DIFFYAVG
Description: The physical model used in Formatcheck step allows
to measure the difference between model predicted
and detected line positions. This is useful to verify
precision of physical model prediction and instrument
spectral format stability.
- sigma_dy: rms of difference of Y positions to physical model, product keyword QC.MODEL.DIFFYRMS
Description: The physical model used in Formatcheck step allows
to measure the difference between model predicted
and detected line positions. This is useful to verify
precision of physical model prediction and instrument
spectral format stability.
- median_shftx: median of difference in X to reference frame, product keyword QC.SHFTXMED
Description: mmeasured median shift in x from stability check
- median_shfty: median of difference in Y to reference frame, product keyword QC.SHFTYMED
Description: measured median shift in y from stability check
- nlin_all: total number of lines found, product keyword QC.MODEL.NLINALL
Description: The physical model used in the Formatcheck step allows
to predict line positions on the formatcheck frame.
This is the total number of predicted matching lines.
- nlin_sel: number of lines selected, product keyword QC.MODEL.NLINSEL
Description: The physical model used in the Formatcheck step allows
to predict line positions on the formatcheck frame.
The selected number of lines is the subset of the total
number of lines which fall in the physical model plot
limits.
- ins_temp4_mean: average temperature inside air [C], 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 INS.TEMPi.MEAN.
Description: Propagated directly from RAW frame
- ins_temp1_mean: average temperature of camera [C], 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 INS.TEMPi.MEAN.
Description: Propagated directly from RAW frame
- ins_press_mean: barometer pressure, 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 INS.SENS26.MEAN.
Description: Propagated directly from RAW frame
|
|
CERTIF |
Reasons for rejection:
- No light or low light level (meaning too few lines can be found)
- Severe Saturation, there will often be some saturation in some lines which is fine, but if most lines were saturated such that too few non saturated lines could be found (never actually seen in 'recorded history' of normal operatiuons)
- Failure to find expected orders
- Deviation from physical model by significantly more than +/-10 pixels (though this has not been seen in 'recorded history' of normal operatiuons)
|
|
COMMENTS |
None
|
top |
[2015-10-30T08:20:43] created by qcDocu v1.1.2, a tqs tool
|