[ ESO ]
FLAMES/GIRAFFE:
basics about data management

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

DATA MANAGEMENT AT ESO

Data packages have been delivered for period P87 (April-September 2011) and before. For new data, acquired after the begin of October 2011, data packages are no longer created. Users can access their raw data in electronic form through the ESO User Portal.

 Data access on the ESO USER PORTAL

Packages can be accessed by the PIs only.

Since October 2011, packages are replaced by associations of calibration data to science data. These packages contain raw data only. Processed data are currently not available through this service.

 File naming schemes

Throughout the data flow system, files are named following certain conventions. The following naming schemes are relevant for files in the data packages:
  • archive file name (FITS keyword: ARCFILE): this is the unique name of a raw file which consists of the parent instrument name and the timestamp of its generation. Raw FITS files produced at ESO always have extension '.fits'.
  • original file name (FITS keyword: ORIGFILE): this is the name of a raw file generated on the mountain on the instrument workstation. It consist of:
    - the name of the parent instrument,
    - the category (e.g. BIAS, FLAT, OBS, ... ),
    - the day sequence number within the year,
    - and a sequence number counted within the night.

    Original file names are not unique (they will usually repeat after a year, sometimes even after a day).
  • data product file name (FITS keyword: PIPEFILE): this is the name of any pipeline product. It is composed of:
    • the prefix 'r.',
    • the ARCFILE of the parent raw file stripped off by the extension,
    • and a sequence number '_0000' etc. (since there may be multiple pipeline products per raw file).

    Product files have the extension '.fits'. In some cases, ESO product files also may have the extension 'tfits' where 't' stands for 'table'. These are ordinary FITS files just like the ones with extension 'fits'.

    In case that more than one raw file has been used to generate the product, the ARCFILE of the first one is used.

  • calibration product name: this is a name of calibration data products which has been chosen to have explicit information about the type of file, the date of creation, its version and the instrument parameters in the file name. It is generated after the pipeline product has been created. The FITS keyword PIPEFILE is preserved and can be used to map the two naming conventions.
  • science product names: science products are renamed to a scheme which allows the user to recognize from the file name the parent OB, the product type and setting parameters.

 

GIRAFFE INFORMATION

GIRAFFE ARCFILE names always start with 'GIRAF'. They come as FITS files with a main plane with the CCD data, and with two extensions with binary tables containing OzPoz and fibre information.

GIRAFFE ORIGFILE names start with FLAMES.

Names of GIRAFFE product science and calibration files are explained here.

GIRAFFE FILE ASSOCIATION

The association of raw files of different types (CALIB and SCIENCE) is a non-trivial task given the many different possible modes of GIRAFFE data. To support in this task, we have created the list files which you find in each package data directory. Since Period 75 (April 2005) there is also an association report, as part of the night and OB logs.

The GIRAFFE association scheme is described here.

FLAMES COMBINED PACKAGES

FLAMES can feed two spectrographs simultaneously, GIRAFFE and UVES. If a FLAMES run has produced both UVES and GIRAFFE data, they will be packed into two separate packages, but shipped together.

GIRAFFE PIPELINE PROCESSING

Since July 2004, GIRAFFE data are pipeline-processed, and usually data packages receive both processed calibration data and reduced science data. If you do not receive pipeline-reduced data, this may be due to the following reasons:

  • Your package has been released prior to July 2004.
  • Some or all of the setups you have used are not yet pipeline-supported. Find more information about the support status here.
  • The pipeline may have failed for other reasons. These are reported to you in a separate file.

[ QC Home page ]  
[ESO][Index][Search][Help][News]