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:

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

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., 070402 for Apr 02, 2007. The version of a file is indicated by capital letters always starting with A. Versioning is supported for most types of files (see table above). In the remaining 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 DIT<DIT> PDRK <WLEN>nm PBPM, PFLT, PDIS, PWMA DIT<DIT>_<WLEN>nm PEFF, PEXT, PCOM, PPRF, PCON

where

PARAMETER EXPLANATION VALUES <DIT> detector DIT in sec e.g. 1, 15, 60 <WLEN> reference wavelength on chip 3 in nm e.g. 1090.4

Extension

All files have extension .fits .

Examples

CR_PDRK_070402A_DIT60.fits is a dark product (master) frame from 2007-04-02 with DIT=60 sec.

CR_PDIS_070411B_1648.9nm.fits is the second (from at least two) dispersion solution table from 2007-04-11 for 1648.9 nm reference wavelength.

CR_PEFF_070411A_DIT15_5050.4nm.fits is a standard star product for 5050.4 nm reference wavelength measured with DIT=15 sec on 2007-04-11.

Naming scheme

The naming scheme has the product type, a date, and short description. The general scheme is:

CR_<TYPE>_<DATE><VERSION>_<NAME>.<SUFFIX> .

Type of product

The following types of static calibrations presently exist:

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:

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

Type of product

The following types of calibration products presently exist:

The ID of the observation block that has been used to measure the raw science frame. It has usually six digits, e.g. 154718.

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. 2007-04-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:

PARAMETER CODE USED FOR FILE TYPES DIT<DIT>_<WLEN>nm SEXT, SCOM, SCON, SPRF, SBGD, SWMA, SWMP

where

PARAMETER EXPLANATION VALUES <DIT> detector DIT in sec e.g. 1, 15, 60 <WLEN> reference wavelength on chip 3 in nm e.g. 1090.4

Extension

All files have extension .fits .

Example

VI_SEXT_218201_2007-04-02T08:53:01.761_DIT30_1202.9nm.fits: table with extracted science spectra, statistical errors, etc.; the ID of the OB was 218201, the (first) raw file was measured on 2 April 2005 at 08:53:01.761 (UT) with reference wavelength 1202.9 nm and a DIT of 30 sec.