Quality Control and
Data Processing

The names of all calibration pipeline products follow a certain naming convention. This is done to have human-readable rather than technical file names. The naming scheme has been chosen to have the type of product, its date of creation, and its pipeline-relevant setup values recognizable in the product name.

The general format of user-oriented product file names is the same for all VLT/VLTI instruments.

On the archive interface, the master calibrations can be associated to science files and downloaded. Then they carry technical filenames (the archive filename ARCFILE). In order to rename them to the original filenames, search for the fits header key ORIGFILE. The naming scheme of ORIGFILE is described here.

Instrument code

All product names start with two letters which are specific for the instrument. For instance: UVES product names start with 'UV', VISIR names with 'VR'.

Product category

The full value of the product category is coded in the FITS header key HIERARCH.ESO.PRO.CATG. A short form of this tag is encoded in four characters being unique per instrument:

1st letter	M or P	calibration product
	G	general (static) calibration product
2nd to 4th letter	...	type of product

Calibration products come in two flavours: dynamic ones (being updated regularly, short validity), and static ones (never or rarely updated). The static ones are also called 'general' because they often are not derived from raw data (like e.g. a line catalogue).

Both product types are stored in the archive and are available for download through the calSelector service. All HAWK-I pipeline product names start with "HI_".

Dynamic calibrations. The following types of dynamic calibration products of HAWK-I exist:

Code	type of file	PRO_CATG
MDRK	master dark	MASTER_DARK
MFLT	master twilight flat	MASTER_TWILIGHT_FLAT
PBPM	bad pixel map	MASTER_BPM
PCON	confidence map	MASTER_CONF
MFRG	gain	MASTER_READGAIN
PZIM	calibrated, processed image	BASIC_CALIBRATED_STD
PZSR	catalogue of detected objects	BASIC_CAT_STD
PZVM	corresponding variance map	BASIC_VAR_MAP
PZMP	table of objects from the external catalogues that were used to calibrate the astrometry and photometry	MATCHSTD_PHOTOM
PZSK	mean sky image	MEAN_SKY
PZSV	corresponding sky variance map	MEAN_SKY_VAR
PDBM	bad pixel map	BP_MAP_NL
PDLT	linearity table	DET_LIN_INFO
PDGT	gain table	GAIN_INFO
PDCC	linearity coefficients cube	COEFFS_CUBE

Static calibrations. These are the codes for the static calibrations:

Code	type of file	PRO_CATG
GSMN	Schlegel_map_north	SCHLEGEL_MAP_NORTH
GSMS	Schlegel_map_north	SCHLEGEL_MAP_SOUTH
GPHT	phot map	PHOTCAL_TAB
GCAS	2mass astrometric catalog	MASTER_2MASS_CATALOGUE_ASTROM
GCAP	2mass photometric catalog	MASTER_2MASS_CATALOGUE_PHOTOM
MFRG	readgain	MASTER_READGAIN

The remaining part of the names follow the same convention as for the dynamic products (see below).

Date of origin, version

The date of origin is identical to the date of the raw data measurement. It is coded like, e.g., 191015 for Oct 15, 2019.

The version of a file is indicated by capital letters, starting with A. Versioning is supported when reasonable, otherwise it is always A.

Instrument parameters

The instrument parameters characterizing a setup are included in the product name. Most HAWK-I products have the following scheme:

<FILTER> or <DET_DIT>_<DET_NDIT> for DARKs;
where

• FILTER is INS.FILT1.NAME or INS.FILT2.NAME keyword, the BB or NB filter used
• DET_DIT is the dark integration time
• DET_NDIT is the number of sub-integrations

Static calibration products either have some setup part, or contain some self-explanatory string like e.g. HI_GPHT_151001A_hawki_phot.fits for the photometric table.

Extension

All product files have extension .fits. They have either image format or binary table format.

NOTE: HAWK-I pipeline products are either a traditional FITS file (i.e. single Header-Data Units (HDUs), e.g. the Stitched product of the hawki_img_jitter recipe) or Multi-Extensin FITS files (MEFs) with a primary HDU containing a header only and then four extension HDUs (one for each chip of the mosaic). The order is normally, but not necessarily chips 1,2,4,3.

Examples

HI_MFLT_180608B_Ks.fits filter Ks twilight flat ; taken on date 2018-06-08 (second one).

HI_MDRK_180620A_300.0_1.fits: 300 s DIT, 1 NDIT master dark; taken on 2018-06-20 (first one on that date).