FORS2 SCI_HIT CALSELECTOR calibration cascade

Mouse over ...
- a RAW_TYPE to see the classification rule (M marks a multiple definition)
- a grouping rule to see the complete grouping rule
- a matching rule (e.g. '1,1') to see the product matching rule.
Product tags etc. might be cut off, in that case mouse over the cell to see the full entry.
EXPOSE: marks those non-SCIENCE RAW_TYPEs which can be exceptionally exposed to CALSELECTOR.

Time match rules:
GT: no validity for this static mcalib defined
T: no validity for this mcalib defined
< PREVIOUS time match
||-7.0/+7.0  calib_plan validity (best mjd_obs time difference) and extended validity defined
(-2.0/+2.0)  calib_plan validity not defined, only extended validity (maximum mjd_obs time difference)
[-2.0/+2.0]  calib_plan validity defined, but no extended validity

bottom | right	left
RAW_TYPE	ACQ_HIT_SKY	ACQ_HIT_SLIT	BIAS	FLAT_SKY	SCI_HIT
DO_CLASS	ACQUISIT_HIT	ACQUISIT_HIT_MS	BIAS	SKY_FLAT_IMG	SCIENCE_HIT
CATG	ACQUISITION	ACQUISITION	CALIB	CALIB	SCIENCE
Grouping rule	single	single	TPL_A	TPL_A	single
Recipe	none	none	fors_bias	fors_img_sky_flat	none
Index	1	2	3	4	5
Calibration cascade:
static mcalibs:	master calibs:
			14 MASTER_BIAS	1,1 ||-5/+5	1,1 ||-5/+5
				15 MASTER_SKY_FLAT_IMG	1,1 ||-14/+14
					16 MASTER_SCI_HIT
Comments:
Analysis (technical consistency checks):
raw_type* (CALIB only)	n/a	n/a	OK	OK	n/a
mcalibs**	n/a	n/a	n/a	OK	OK
powered by QC [createCalibMap v2.1.1] last update: 2024-06-06T10:33:39

*raw_type: is raw_type used in cascade? (CALIB only)
**mcalibs: are all required mcalibs, per raw_type, somewhere listed as products?
top