[ ESO ]
FLAMES/GIRAFFE:
Pipeline product naming scheme

CAL | HC | refs | QC
QUALITY CONTROL
    HOME
GIRAFFE QC
Trending & QC1
Pipeline
product names
Data Management
GIRAFFE ...
QC links:
general GIRAFFE

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

top GIRAFFE INSTRUMENT CODE

All GIRAFFE pipeline product names start with "GI_".

top SCIENCE PIPELINE PRODUCTS

Science products have the following scheme:

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

e.g.

GI_SRBS_186898_2011-03-29T02:17:38_Medusa2_L479.7_o4_n.fits
(data taken before 2010-10-20 have a slightly different name structure, GI_SRBS_186898_2005-03-29T06:48:12_Argus_L479.7nm_o4.fits)

where:

  • S<PPP> is the four letter code uniquely describing the type of SCIENCE product (the first letter is always S for SCIENCE)
  • 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. slit, central wavelength; calibration products use the same string)
  • ext is fits

The following types of science products exist:
CODE TYPE OF FILE PRO_CATG
SRBS wavelength calibrated spectra SCIENCE_RBNSPECTRA
SRBE associated errors SCIENCE_RBNERRORS
SEXS extracted, but not wavelength calibrated spectra SCIENCE_EXTSPECTRA
SEXE associated errors SCIENCE_EXTERRORS
SIMG reconstructed image (Argus and IFU only) SCIENCE_RCSPECTRA
SIME associated errors (Argus and IFU only) SCIENCE_RCERRORS
SCUB reconstructed image as data cube (Argus only) SCIENCE_CUBE_SPECTRA*
SCUE associated errors (Argus only) SCIENCE_CUBE_ERRORS*

* since 2007-06-18

For the instrument parameter string see below.

top CALIBRATION PIPELINE PRODUCTS

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:
CODE TYPE OF FILE PRO_CATG VERSIONING?
MBIA master bias MASTER_BIAS no
MDRK master dark MASTER_DARK no
 
PLOW localization width FF_LOCWIDTH yes
PLOC localization centroid FF_LOCCENTROID yes
PFEX extracted spectra FF_EXTSPECTRA yes
PFEE extraction errors FF_EXTERROS yes
 
PNLW localization width (nasmyth flats) NF_LOCWIDTH yes
PNLC localization centroid (nasmyth flats) NF_LOCCENTROID yes
PNEX extracted spectra (nasmyth flats) NF_EXTSPECTRA yes
PNEE extraction errors (nasmyth flats) NF_EXTERROS yes
 
PDIS dispersion solution DISPERSION_SOLUTION yes
PAES extracted spectra ARC_EXTSPECTRA yes
PAEE extraction errors ARC_EXTERRORS yes
PRBS rebinned spectra ARC_RBNSPECTRA yes
PRBE rebinned extraction errors ARC_RBNERRORS yes
 
PSRS* rebinned spectra (STD) STD_RBNSPECTRA yes
PSRE* rebinned extraction errors (STD) STD_RBNERRORS yes
PIMG* reconstructed image (STD) STD_RCSPECTRA yes
PIME* corresponding errors (STD) STD_RCERRORS yes
PCUB** reconstructed image, data cube(STD) STD_CUBE_SPECTRA yes
PCUE** corresponding errors, data cube (STD) STD_CUBE_ERRORS yes
PEFF*** efficiency curve (STD) EFFICIENCY_CURVE yes
PRSP*** instrument response (STD) INSTRUMENT_RESPONSE yes

* 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:

CODE TYPE OF FILE PRO_CATG VERSIONING?
GCAT line catalog LINE_CATALOG no
GRAT grating data GRATING_DATA
GMSK line mask LINE_MASK
GDIS reference dispersion solution REFERENCE_DISP_SOLUTION
GSGS slit geometry setup SLIT_GEOMETRY_SETUP
GFLX flux standard list FLUX_STANDARDS*
GATM extinction table ATMOSPHERIC_EXTINCTION*
* for IFU and Argus only

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:

<SLIT>_<GRATING><WLEN>nm_o<ORDER>
(since 2010-10-20: <SLIT>_<GRATING><WLEN>_o<ORDER>_<READ> )

where

  • SLIT is either Medusa1, Medusa2, IFU1, IFU2, or Argus,
  • GRATING is either H (high resolution) or L (Iow resolution)
  • WLEN is the central wavelength in nm of the mode,
  • ORDER is the spectral order (to distinguish 'old' and 'new' setups),
  • READ is either n (Normal) or f (Fast) and indicates the read speed.

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).

STD data have in addition the target name coded,
<SLIT>_<GRATING><WLEN>nm_o<ORDER>_<TARG_NAME>.

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.

Suffix

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

top Examples

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).


 
[ESO][Index][Search][Help][News]