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

CALIBRATION PRODUCT CODES

Naming scheme

The naming scheme has the product type, the date of creation, and pipeline-relevant parameter values all recognisable from its name. The general scheme is:

UV_<TYPE>_<DATE><VERSION>_<PARAMS>.<SUFFIX> .

Instrument code

All UVES and UVES-MOS calibration product names start with UV. All VLT instruments follow the same scheme, i.e. their calibration products also start with a two letter instrument code.

Type of product

The product type is given by the fits key HIERARCH.ESO.PRO.CATG. A short form of this is coded in the name using a four character scheme:

1st letter M or P master file or product file 2nd to 4th letter ... type of product

The following types of calibration products presently exist:

Date of origin, version

The date of origin is identical to the date of the raw data measurement. It is coded as, e.g., 011015 for Oct 15, 2001. The version of a file is indicated by capital letters always starting with A. Versioning is supported for certain types of files only (see table above). In all other cases, only one version per day is created (version is always A).

Instrumental parameters

Those parameters which are relevant for the specific type of calibration product are included in its name. The following schemes are used:

PARAMETER CODE USED FOR FILE TYPES UVES MODE <CCD>_<BIN> MBIA, MDRK ECH, MOS <CCD><WLEN><MODE>_<BIN>_<SLTW> PDRS, PLI1,2,3, MFLT, MDFT, MIFT ECH <CCD><WLEN><MODE>_<BIN> PORD, PBKG, PGUE, PEFC, PRSP ECH <CCD><WLEN> MRSP ECH <CCD><WLEN><MODE>_SI<SIMCAL>_PL<PLATE> MFxx, MSxx, PDRS, PORD, PLIN MOS <CCD><WLEN><MODE>_PL<PLATE> PGUE, PODF, POGU MOS <CCD><WLEN><MODE> MSFT MOS

where

PARAMETER EXPLANATION VALUES <CCD> CCD designation BLUE, REDL, REDU <WLEN> wavelength in nm (e.g. 580) <MODE> observation mode (INS.MODE keyword) bl: blue arm; re: red arm; d1: dichroic#1, d2: dichroic#2; fi: fibre mode <BIN> detector binning (x times y) 1x1, 2x2, 1x2, 2x3 <SLTW> slit width in arcsec * 10 (e.g. 0.5 arcs are coded as 05, and 2.1 arcs as 21) MOS only: <PLATE> observation plate 1 or 2 <SIMCAL> SimCal mode 0: calibrations for science that do not use the simultaneous calibration fibre; 1: for science that use the simultaneous calibration fibre

<SIMCAL> is set according to the value of the INS.SLIT3.MODE keyword (from the fits headers): 6FIB or 8FIB means SIMCAL=0, 7+1FIB means SIMCAL=1.

Extension

All products have extension .fits.

Master products from slit and fibre flats (UVES-MOS)

There is a large number of pipeline products that are derived from combining slit and fibre flat fields. From Period 74 on (i.e. from 1 October 2004), these products are coded with MSxx or MFxx:

Some of the products (BN, BP, DT, SG) come as data cubes combining up to three individual files. The original files can be recovered using the DECUBI/FLAM command of the MIDAS FLAMES context:

midas> indisk/fits <file>.fits <file>.bdf
midas> decubi/flam <file>.bdf <plane> <outputname>.bdf no

with <plane> = 1, 2, or 3. Example:

midas> decubi/flam UV_MSDT_050309A_REDL580fi_SI0_PL1.bdf 2 master2L.bdf no .

For master files produced in Period 73 or earlier, the type was either MSFT of MFFT and an additional three letter code was added after the instrumental parameters. Data cubes were not used.

Naming scheme

The naming scheme has the product type, the ID of the observation block, a time stamp, and pipeline-relevant parameter values all recognisable from its name. The general scheme is:

UV_<TYPE>_<OB_ID>_<TIMESTAMP>_<PARAMS>.<SUFFIX> .

Type of product

The product type is given by the fits key HIERARCH.ESO.PRO.CATG. A short form of this is coded in the name using a four character scheme:

1st letter S science product file 2nd to 4th letter ... type of product

The following types of calibration products presently exist:

OB ID

The ID of the observation block that has been used to measure the raw science frame.

Time stamp

The time stamp has the form <YEAR>-<MONTH>-<DAY>T<HOUR>:<MINUTE>:<SECOND>.<MILLISEC>. It has the same value that is used in the archive filename of the raw file, e.g. 2005-01-18T04:45:19.435.

Instrumental parameters

The instrumental parameters for the science frames are the same as for the calibrations in order to identify matching files.