Data product names
The names of all calibration 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 setup values recognizable in the product name.
The general format of user-oriented product file names is the same for all
VLT/VLTI instruments.
On the archive interface, the master calibrations can be associated to science files and downloaded. Then they carry
technical filenames (the archive filename ARCFILE). In order to rename them to the
original filenames, search for the fits header key ORIGFILE. The naming scheme
of ORIGFILE is described here.
Instrument code
All product names start with two letters which are specific for the
instrument. For instance: UVES product names start with 'UV', VISIR names with
'VR'.
Product category
The full value of the product category is coded in the FITS header
key HIERARCH.ESO.PRO.CATG. A short form of this tag is encoded in four
characters being unique per instrument:
1st letter | M or P | calibration product |
| G | general (static) calibration product |
2nd to 4th letter | ... | type of product |
Calibration products come in two flavours: dynamic ones (being updated
regularly, short validity), and static ones (never or rarely updated). The
static ones are also called 'general' because they often are not derived from
raw data (like e.g. a line catalogue).
Both
product types are stored in the archive and are available for download through
the calSelector service.
Naming convention
Convention for calibration products
All PIONIER pipeline product names start with "PI_".
Dynamic calibrations.
The following types of dynamic calibration products of PIONIER exist:
MODE | TYPE OF FILE | PRO_CATG |
MGAI | gain | PIONI_DETMON_GAIN |
MBPM | bad pixel Map (full detector) | PIONI_MASTER_BPM |
MMBP | bad pixel Map (science pixels) | PIONI_MASTER_BPM_MASKED |
MDRK | dark | DARK_CALIBRATION |
MSPE | spectral calibration (Lamp) | SPECTRAL_CALIBRATION |
MKAP | Interferometric transmission (kappa on liamp or object) | KAPPA_MATRIX |
MIFR | Visibility and CP (lamp) | LAMP_OIDATA_RAW |
MSPO | spectral calibration (object) | OBJECT_SPECTRAL_CALIBRATION |
MCFR | Visibility and CP (lapm) | CALIB_OIDATA_RAW |
MCTF | TF (calibrator) | OIDATA_TF |
Date of origin, version
The date of origin is identical to the date of the raw data measurement. It is coded as, e.g., 011015 for Oct 15, 2001. The version of a file is indicated by capital letters always starting with A. Versioning is supported.
The calibrator catalog starts with PI_GCAL_
Instrumental parameters
Those parameters which are relevant for the specific type of calibration product are included in its name.
For the astronomical calibrators the following keywords are used to identify relevant parameters in the product name:
KEYWORD | Description |
INS.OPTI2.NAME | Dispersive element |
DET.POLAR | Gain |
DET.SUBWINS | number of subwindows |
OBS.TARG.NAME | target name |
ISS.CONF.STATION1 | station1 |
ISS.CONF.STATION2 | station2 |
ISS.CONF.STATION3 | station3 |
ISS.CONF.STATION4 | station4 |
For most of the other calibration products only INS.OPTI2.NAME, DET.POLAR, DET.SUBWINS are used
|