[ ESO ]
UVES/FLAMES-UVES:
Pipeline product naming scheme

CAL | HC | refs | QC
QUALITY CONTROL
    HOME
UVES QC
Trending & QC1
Pipeline
product names
Data Packages
Data Management
Solar&sky spectra
QC links:
general UVES

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:

CODE TYPE OF FILE PRO_CATG* UVES MODE** VERSIONING?
MBIA master bias MASTER_BIAS_<CCD> ECH, MOS no
MDRK master dark MASTER_DARK_<CCD> ECH, MOS yes
         
MFLT master flat (ordinary FF lamp) MASTER_FLAT_<CCD> ECH yes
MDFT master deuterium flat (deuterium lamp, 346nm settings only) MASTER_DFLAT_<CCD> ECH yes
MIFT master I2 flat (FF3 lamp plus iodine absorption cell, 600nm settings only) MASTER_IFLAT_<CCD> ECH yes
         
PDRS setup table for data reduction system DRS_SETUP_<CCD> ECH no
PORD order table ORDER_TABLE_<CCD> ECH no
PBKG background table BACKGR_TABLE_<CCD> ECH no
PGUE line guess table LINE_TABLE_<CCD> ECH no
PLI1,
PLI2,
PLI3
line tables (1 and 3: sky window, 2: object window) LINE_TABLE_<CCD>1,
LINE_TABLE_<CCD>2,
LINE_TABLE_<CCD>3
ECH yes
         
PRSP response curve from a single standard star measurement INSTR_RESPONSE_<CCD> ECH yes
PEFC efficiency curve from a single standard star measurement EFFICIENCY_TABLE_<CCD> ECH yes
MRSP master response curve (created from several individual response curves) MASTER_RESPONSE_<CCD> ECH N/A
         
MSFT master slit flat MASTER_SFLAT_<CCD> MOS yes
MSxx other slit flat products SLIT_FF_xxx_<CCD> (see below) MOS yes
MFxx master fibre flat products FIB_FF_xxx_<CCD> (see below) MOS yes
         
PDRS setup table for data reduction system FIB_DRS_<CCD> MOS no
PODF order definition frame FIB_ORDEF_<CCD> MOS no
POGU guess order definiton table FIB_ORD_GUE_<CCD> MOS no
PORD order definition table FIB_ORDEF_TABLE_<CCD> MOS yes
PGUE guess line table FIN_LIN_GUESS_<CCD> MOS no
PLIN line table FIB_LINE_TABLE_<CCD> MOS yes

*For the complete value of PRO.CATG, the designation of the chip has to be added: <CCD>=BLUE, REDL, or REDU
**ECH: UVES-Echelle (i.e. usage as single-object spectrograph); MOS: UVES-Fibre aka FLAMES-UVES (i.e. usage as multi-object spectrograph)

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:

CODE TYPE OF FILE PRO_CATG* DATA CUBE?
MFCO common data of fibre flat field set FIB_FF_COM_<CCD> no
MFNO normalisation data of fibre flat fields FIB_FF_NOR_<CCD> no
MFNS variance for FIB_FF_NOR FIB_FF_NSG_<CCD> no
MFDT normalised, cleaned fibre flat fields FIB_FF_DTC_<CCD> yes
MFSG variance for FIB_FF_DTC FIB_FF_SGC_<CCD> yes
MFBP bad-pixel mask for FIB_FF_DTC FIB_FF_BPC_<CCD> yes
MSCO common data of slit flat field set SLIT_FF_COM_<CCD> no
MSNO normalisation data of slit flat field set SLIT_FF_NOR_<CCD> no
MSDT data cube of nomalised slit flat field frames SLIT_FF_DTC_<CCD> yes
MSSG variances for SLIT_FF_DTC SLIT_FF_SGC_<CCD> yes
MSBP bad-pixel mask for SLIT_FF_DTC SLIT_FF_BPC_<CCD> yes
MSBN boundaries for SLIT_FF_DTC SLIT_FF_BNC_<CCD> yes

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.

SCIENCE PRODUCT CODES

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:

CODE TYPE OF FILE PRO_CATG* UVES MODE**
SRED reduced spectrum RED_SCI_POINT_<CCD>, RED_SCI_EXTND_<CCD>, RED_SCI_SLICER_<CCD> ECH
SERR errorbars for reduced spectrum ERRORBAR_SCI_POINT_<CCD>, ERRORBAR_SCI_EXTND_<CCD>, ERRORBAR_SCI_SLICER_<CCD> ECH
SORD position and FWHM information per order ORDER_TRACE_<CCD> ECH
SCRM cosmic ray mask table CRMASK_<CCD> ECH
SFLX flux-calibrated science spectrum FLUXCAL_SCIENCE_<CCD> ECH
SFXE errorbars for flux-calibrated spectrum FLUXCAL_ERRORBAR_<CCD> ECH
       
SE2D extracted 2D spectrum EXT_2D_SCI_EXTND_<CCD> ECH
SF2D flat-fielded extracted 2D spectrum FF2D_SCI_EXTND_<CCD> ECH
SW2D wavelength-calibrated, flat-fielded 2D spectrum WCAL2D_SCI_EXTND_<CCD> ECH
SX2D final flux-calibrated 2D spectrum FLUXCAL_2D_SCI_EXTND_<CCD> ECH
       
SINF fibre information table FIB_SCI_INFO_TAB MOS
SRED reduced spectra MWXB_SCI_<CCD> MOS
SERR errorbars for reduced spectra ERR_MWXB_SCI_<CCD> MOS
SEXT extracted spectra for each order XB_SCI_<CCD> MOS
SRRD reduced spectra with fibre throughput correction MWXB_SCI_RAW_<CCD> MOS
SRER errorbars for reduced spectra (not corrected) ERR_MWXB_SCI_RAW_<CCD> MOS
SREX extracted spectra for each order (not corrected) XB_SCI_RAW_<CCD> MOS
SCOR cross-correlation results (SimCal only) CORVEL_TAB MOS

*For the complete value of PRO.CATG, the designation of the chip has to be added: <CCD>=BLUE, REDL, or REDU
**ECH: UVES-Echelle (i.e. usage as single-object spectrograph); MOS: UVES-Fibre, FLAMES-UVES (i.e. usage as multi-object spectrograph)

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.


[ QC Home page ]
 
[ESO][Index][Search][Help][News]