MUSE calibration data are mostly taken as daytime
calibrations. Twilight flat-field exposures, standard stars and
astrometry fields are taken as part of the calibration plan during the
night. Find information about the MUSE data format, spectral format and the detector here.
The following calibration data are taken as part of the MUSE
calibration plan. The data types are identified by the DPR.TYPE and
DPR.TECH keyword in the FITS headers. For details on the data, and in
particular, on each extension see the MUSE reference frames web page.
detector status, bias level
tracing of slices; flat flux level
15, the input frames come as multiple of 3 for Ne, Xe, and HgCd arc lamps each
absolute flux calibration, telluric correction
*N: typical number taken per night and setting
The ARC LAMP exposures are taken separately for each spectral lamp:
Ne, Xe and HgCd. Thus, the number of input frames is always multiple
of 3. The different lamp exposures can be distinguished by the shutter
status keyword having True (T) rather than False (F) value:
The GEOMETRY and ASTROMETRY observations are taken about monthly
to monitor status of the instrument. They have to be processed
together and the pipeline requires special hardware and software
setup. Thus, the products exist as "static calibrations" and are
renewed whenever it is necessary.
creates a master bias from a set of input raw frames
creates a master dark from a set of input raw frames
creates a master lamp flat and trace table from a set of input frames
obtains the wavelength calibration solution from an input arc-lamp frames
determines instrumental response
STD_RESPONSE, STD_TELLURIC, DATACUBE_STD
creates a master twilight flat from a set of input frames
STD_RESPONSE - change between pipeline v.1 and v.2
The shape of STD_RESPONSE changed with transition from pipeline v.1
to v.2 (2017-05-01 in QC system). The v.2 response contains the
correction for the flat field, while the v.1 one does not. The flat
field correction is indicated by the ESO_DRS_FFCORR keyword, which allows
the pipeline to distiguish between different formats and handle them
accordingly. Thus, the pipeline is backwards compatible.
After production and certification, the calibration products are archived.
They are named with
a scheme including type, creation date and relevant setting
parameters. For the detailed description of the product names go here. The master calibrations are available for archive users through
the calSelector service.
The processing of MUSE calibration frames requires a cascaded scheme where
the mutual dependencies of products and raw frames are respected. The proper
sequence of all these production steps is called the calibration cascade. It
is described here.
Within that cascade, all products are checked with respect to their quality
and their relationship in time. This means e.g. that a dispersion solution is
not only generated using an arbitrary quality-checked localization solution,
but that specific solution is chosen which is closest in time.
All products created by QC Garching follow the calibration cascade. On the
hand, Paranal-processed science data use
standard solutions created by QC Garching and possibly
several months old.
Static calibration tables (the ones not being regularly processed from
raw calibration data) come as FITS tables and are available through
the calSelector archive service. Some of them come with different
versions indicated by unique date, e.g.140101, of creation, as they
are being updated with time.
catalog of astrometric standards
catalog of the WCS positions of the astrometric standards
table of bad pixels
list of filters
response curve for the WFM-E mode
response curve for the WFM-N mode
response curve for the NFM mode
flux table for the standard stars
catalog of the sky lines
vignetting mask, OBSOLETE, NOT used for the data since 2018-01-01
LSF profile for the WFM-E mode
LSF profile for the WFM-N mode
LSF table, OBSOLETE, NOT used with current pipeline version
LSF cube for WFM-E mode, OBSOLETE, NOT used with current pipeline version
LSF cube for WFM-N mode, OBSOLETE, NOT used with current pipeline version