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 HAWK-I pipeline product names start with "HI_".
Science products have the following scheme:
The following types of science products presently exist:
HAWK-I 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.
The remaining part of the names follow the same convention as for the dynamic products (see below).
Date of origin, version
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).
All product files have extension .fits. They have either image format or binary table format.
NOTE: HAWK-I pipeline products are either a traditional FITS file (i.e. single Header-Data Units (HDUs), e.g. the Stitched product of the hawki_img_jitter recipe) or Multi-Extensin FITS files (MEFs) with a primary HDU containing a header only and then four extension HDUs (one for each chip of the mosaic). The order is normally, but not necessarily chips 1,2,4,3.