[ ESO ]
VISIR:
Pipeline product naming scheme

CAL | HC | refs | QC
QUALITY CONTROL
    HOME
VISIR QC
Trending & QC1
Pipeline
Data Packages
Data Management
QC links:
general VISIR

LIST OF PIPELINE PRODUCTS CODES

The names of all 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 parameter values all recognizable from the product name.

Since the begin of period 75 (April 2005), both science and calibration product files are renamed. (Actually, there was a transition phase extending for some instruments from April towards the end of the year 2005).

Before that date only calibration products followed the common scheme which is described here. (Some instruments had their own naming scheme which is described below, if applicable).

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

Instrument code

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

Type of product

Next, the product type is coded. The full value is coded in the fits header key HIERARCH.ESO.PRO.CATG. A short form of this tag is coded in four characters being unique per instrument:
1st letter M or P calibration product
  S science product
  G general calibration product (as of P82)
2nd to 4th letter ... type of product

top VISIR INSTRUMENT CODE

All VISIR pipeline product names start with "VR_".

top SCIENCE PIPELINE PRODUCTS

Science products have the following scheme:

VR_S<PPP>_<OBS_ID>_<DATE_TIME>_<parameter_string>.<ext>

e.g.

VR_SICP_186898_2005-03-29T06:48:12_px0.075_filtJ7.9.fits

where:

  • S<PPP> is the four letter code uniquely describing the type of SCIENCE product (the first letter is always S for SCIENCE)
  • OBS_ID is the OB number read from the OBS.ID fits key
  • DATE_TIME is the UT date and time of the first raw frame measured for the OB (e.g. 2005-04-01T04:31:12); this information is required since OBs can be executed several times
  • parameter_string is a string containing the instrument setup information (e.g. pixel field of view, filter; calibration products use similar string)
  • ext is fits

The following types of science products presently exist:
CODE TYPE OF FILE PRO_CATG
SICP chop-nodd-jitter science image combined IMG_OBS_COMBINED_CNJ
SICM chop-nodd-jitter science image contribution map IMG_OBS_CONTRIB_CNJ
SICJ chopping-jitter science image combined IMG_OBS_COMBINED_CJ
PICJ chopping-jitter science image contribution map IMG_OBS_CONTRIB_CJ
SINJ nodding-jitter science image combined IMG_OBS_COMBINED_NJ
PINJ nodding-jitter science image contribution map IMG_OBS_CONTRIB_NJ
SIDJ dirrect-jitter science image combined IMG_OBS_COMBINED_DJ
PIDJ dirrect-jitter science image contribution map IMG_OBS_CONTRIB_DJ
SSCP science spectroscopy combined SPC_OBS_LMR_COMBINED
SSCW science spectroscopy combined weight map SPC_OBS_LMR_WEIGHT
SSCT science spectroscopy combined table SPC_OBS_LMR_TAB
SSHP science spectroscopy combined echelle SPC_OBS_HRG_COMBINED
SSHW science spectroscopy combined weight map echelle SPC_OBS_HRG_WEIGHT
SSHT science spectroscopy combined table echelle SPC_OBS_HRG_TAB

For the instrument parameter string see below.

top CALIBRATION PIPELINE PRODUCTS

VISIR calibration products come in two flavours: dynamic ones (being updated regularly, short validity), and static ones (never or rarely updated). Both product types are delivered in the data packages and stored in the archive. The static ones (also called general calibration products) are also delivered in the public pipeline releases.

Dynamic calibrations. The following types of dynamic calibration products of VISIR presently exist:
CODE TYPE OF FILE PRO_CATG VERSIONING?
MDIA dark imaging average IMG_DARK_AVG yes
MDIH dark imaging, hot pixel map IMG_DARK_HOT yes
MDIC dark imaging cold pixel map IMG_DARK_COLD yes
MDID dark imaging deviant pixel map IMG_DARK_DEV yes
 
MFIC flat field imaging IMG_FF yes
MBIC flat field imaging bad pixel map IMG_BPM yes
MFSC flat field spectroscopy IMG_FF yes
MBSC flat field spectroscopy bad pixel map IMG_BPM yes
 
MSIC standard star imaging IMG_PHOT_COMBINED yes
MSIM standard star imaging contribution map IMG_PHOT_CONTRIB_MAP yes
 
MSSC standard star spectroscopy SPC_PHOT_COMBINED yes
MSSW standard star spectroscopy weight SPC_PHOT_WEIGHT yes
MSST standard star spectroscopy table SPC_PHOT_TABLE yes
 
MSEC standard star spectroscopy echelle SPC_PHOT_HRG_COMBINED yes
MSEW standard star spectroscopy echelle weight SPC_PHOT_HRG_WEIGHT yes
MSET standard star spectroscopy echelle table SPC_PHOT_HRG_TABLE yes

top Static calibrations. With P81 (April 2008), the static calibration products are also named according to the standard VISIR naming scheme. Before that date, their names did not follow a strict naming scheme. The following table lists the codes in the new name scheme:

CODE TYPE OF FILE PRO_CATG VERSIONING?
GICT imaging standard star catalog IMG_STD_CATALOG no
GSCT spectroscopy standard star catalog SPEC_STD_CATALOG no
GSLN atmospheric emission lines calibration file SPEC_CAL_LINES no
GSQE quantum efficiency calibration file SPEC_CAL_QEFF no

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

top Date of origin, version

The date of origin is identical to the date of the raw data measurement. It is coded as, e.g., 051015 for Oct 15, 2005.

The version of a file is indicated by capital letters always starting with A. Versioning is supported for certain types of files, see the above table. In all other cases, only one version per day is created (always A).

top Instrumental parameters

The instrument parameters characterizing a setup are included in the product name. Imaging products have the following scheme:

<PFOV><FILTER>

where

  • PFOV is pixel-field-of-view, e.g. pix0.075 or pix0.127
  • FILTER is e.g. filtPAH1_1.

Spectroscopy products follow different scheme:

<RESOLUTION><GRAT1.WLEN><FILTER>

where

  • RESOLUTION is LR, MR, or HRS,
  • GRAT1.WLEN is the central grating wavelength, e.g. 8.8um,
  • FILTER is e.g. filtN_SW, or filtNEII_2.

Static calibration products contain some self-explanatory string like e.g. VR_GICT_070808A_IMG_STD_CATALOG.fits for the imaging standard star catalog table.

Suffix

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

top Examples

VR_MFIC_090909A_px0.127_filtPAH1.fits: imaging master flat field, pixel-field-of-view 0.127, filter PAH1; taken on date 2009-09-09 (first one on that date).

VR_MSSC_090909B_LR_12.40um_filtN_LW.fits: spectroscopic standard star, low resolution - LR, grating central wavelength 12.40 um, filter N_SW; taken on date 2009-09-09 (second one on that date).


 
[ESO][Index][Search][Help][News]