Pipeline product naming scheme
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.
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:
All VISIR pipeline product names start with "VR_".
Science products have the following scheme:
The following types of science products presently exist:
For the instrument parameter string see below.
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:
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:
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:
Spectroscopy products follow different scheme:
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.
All product files have extension .fits. They have either image format or binary table format.
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).