[ ESO ] MIDI Data Management:
general information

CAL | HC | refs | QC
Trending & QC1
Data packages
Data Management
general info
QC links:
general MIDI


Users can access their raw data through the ESO User Portal. The 'calSelector' service provides associated calibration data.

ESO provides for some instruments fully reduced science-grade spectral data products for the entire history of the respective instrument.

Find the current list of these data products here.

Historical note: until the end of P87 (September 2011), ESO used to deliver PI data packages. With the begin of October 2011, this service was terminated.

 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.



Usually data packages should contain raw and processed science and calibration data (if the mode is supported by the pipeline). Sometimes, however, the automatic pipeline fails. In this case information should be available in the GEN_INFO directory.

top File Ownership

All MIDI raw files carry the FITS keyword 'HIERARCH ESO OBS PROG ID'. Depending on its content, two cases are distinguished concerning the distribution of files in the Data package:

  • Files with DPR CATG=SCIENCE: here a strict check on the PROG_ID is made. You will receive all files which carry your PROG_ID, and only those.
  • Files with the DPR CATG=CALIB. In this case, there are two different types of CALIB files :
    • the technical calibration files (part of the calibration plan, these are not driven by a PROG_ID), you will receive the raw files for the technical calibrations relevant to your observations,
    • the files measuring fringes on a astronomical calibrator which contains a PROG_ID. You will receive the raw files taken on the astronomical calibrator with your PROG_ID. You can also access the astronomical CALIB files which carry another PROG_ID as soon as they are in the archive in Garching (here).

[FORS1 QC][Observing Facilities and Operations][ESO][Index][Search][Help][News]