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 GIRAFFE pipeline product names start with "GI_".
Science products have the following scheme:
The following types of science products exist:
* since 2007-06-18
For the instrument parameter string see below.
GIRAFFE 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 GIRAFFE presently exist:
* for IFU and Argus only; ** since 2007-06-18; *** for Argus only, since 2008-07-16
top Static calibrations. With P81 (April 2008), the static calibration products are also named according to the standard GIRAFFE 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. Most products have the following scheme:
Master biases have only <BIN> =1x1 as mode designator (since P86: <READ> = n or f).
With P86 (2010-10-01), a new readmode was introduced (Fast). Now it became important to indicate the read mode which is either n (Normal) or f (Fast).
have in addition the target name coded,
Static calibration products either have some setup part, or contain some self-explanatory string like e.g. GI_GATM_021213A_atm_extinction.fits for the extinction table.
All product files have extension .fits. They have either image format or binary table format.
NOTE: most GIRAFFE pipeline products have in addition to the image part an extension with the 'fibre-setup table'. That table lists the fibre parameters (from the ozpoz and fibre tables attached to the raw files) for the fibres actually found. More ...
GI_PDIS_040516A_Argus_L773.4nm_o2.fits: dispersion solution for Argus, setup L773.4 (order 2); taken on date 2004-05-16 (first one on that date).
GI_PFEX_040606B_Medusa2_L427.2nm_o4.fits: extracted flat for Medusa2, setup L427.2 (order 4); taken on date 2004-06-06 (second one).
GI_PFEX_101106B_Medusa2_L427.2nm_o4_n.fits: same product type, taken on date 2010-11-06.
GI_MBIA_040101A_1x1.fits: master bias for 2004-01-01 (first and only one).