Names of 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.

With the begin of period 76 (October 2005), both science and calibration product files are renamed.

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

Instrument code

All AMBER pipeline product names start with AM.

Type of product

The type of product is coded in 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 calibration product, master file or product file   S science product 2nd to 4th letter ... type of product

Science products have the following scheme:

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

e.g.

AM_SSFR_200147608_2005-02-26T03:47:46.826_GMR_24403509_U2U3.fits

where:

• S<PPP> is the four letter code uniquely describing the type of SCIENCE product (the first letter is always S for SCIENCE). Each OB consists of several files containing fringes (5 of them in general), the merged file is a concatenation of all the frames of these individual files
• 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. grism mode (high-medium or low resolution), P2VM ID, telescope stations)
• ext is either fits or tfits (for fits tables)

The following types of science products presently exist:

 

CODE TYPE OF FILE PRO_CATG SSFR reduced fringe file SCIENCE_REDUCED SMFR merged reduced fringe file SCIENCE_REDUCED_MERGED SFFR filtered reduced fringe file SCIENCE_REDUCED_FILTERED SFMR merged filtered reduced fringe file SCIENCE_FILTERED_MERGED SSCJ/H/K merged filtered calibrated fringe file SCIENCE_CALIBRATED_J/H/K

For the instrument parameter string see below.

Calibration products are named for example: AM_MCFR_051024A_3Tstd_Medium_K_1_2.1_GMR_HR201.fits. As with the science, each OB consists of several files containing fringes (5 of them in general), the merged file is a concatenation of all the frames of these individual files.

The following types of calibration products presently exist:

CODE TYPE OF FILE PRO_CATG VERSIONING? GBPM master bad pixel map AMBER_BADPIX no GFFM master flat field map AMBER_FLATFIELD no MPOS position of the beams BPOS_REDUCED yes   MPVM master P2VM (Pixel To Visibility Map) REDUCED_P2VM yes MCFR master Fringe file (calibrator) CALIB_REDUCED yes MMFR merged master Fringe file (calibrator) CALIB_REDUCED_MERGED yes MFFR filtered master Fringe file (calibrator) CALIB_REDUCED_FILTERED yes MFMR merged filtered master Fringe file (calibrator) CALIB_FILTERED_MERGED yes MTFx Instrumental Transfer Function in the band x (only for CalVin calibrators) AMBER_TRF_x (x: J, H or K) yes MTMx merged Instrumental Transfer Function in the band x (only for CalVin calibrators) MERGED_AMBER_TRF_x (x: J, H or K) yes

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 above table. In all other cases, only one version per day is created (always A).

Instrumental parameters

The resolution of the dispersive element is included in the product name.

• GMR (Medium resolution), GLR (Low resolution), GHR (High resolution)

Suffix

Most product files are fits table (amdLib compatible) and suffix .fits. In either case they are FITS files, of course.