[ ESO logo ]
The UVES reprocessed
data set

UVES REPROCESSING
QC HOME
Products
[best viewing with style sheets and javascript enabled]

Quick links: FITS files | raw & products | file names | ancillary files

UVES products

FITS files

The following FITS products exist in the data set (sorted along increasing reduction level):

name code product type (PRO.CATG) description type always available?
UV_SWCA WCALIB_FF_SCI_POINT_{ccd} extracted, sky-subtracted, flattened, wave-calibrated but not order-merged spectrum science, intermediate yes
 
UV_SRED RED_SCI_POINT_{ccd} extracted, sky-subtracted, flat-fielded, rebinned, order-merged but not fluxed science, final yes
UV_SERR ERRORBAR_SCI_POINT_{ccd} error information for RED_SCI_POINT error yes
UV_SSKY MERGED_SKY_{ccd} background for RED_SCI_POINT error yes
 
UV_SFLX FLUXCAL_SCIENCE_{ccd}

extracted, sky-subtracted, flat-fielded, rebinned, order-merged and fluxed

science, final no
UV_SFXE FLUXCAL_ERRORBAR_{ccd} error information for FLUXCAL_SCIENCE error no
ccd = BLUE | REDL | REDU

The error products contain information based on the extraction process. They record, in each wavelength bin, the chi^2 value of the profile used for optimum extraction. Like the signal files, the error files come in two varieties: before flux calibration, and after flux calibration, if a final flux-calibrated product exists.

There is also the extracted sky background recorded which might become useful to assess data quality in cases of faint sources and high sky level (moon contamination, sky emission lines).

More on UVES pipeline products ...

More on master response curves ...

More on UVES flux calibration ...

top Relation between raw file and product files

The UVES spectra in a data set are always derived from a single raw file. There is always a set of 4 or 6 FITS products per CCD. The UVES blue arm has one CCD, the red arm two CCDs. Therefore all spectra from the red arm come as set of 8 or 12 FITS files, the blue products as set of 4 or 6 files:

UVES FITS products
  blue arm red arm   dichroic
raw file 1 1   2
product files per CCD 4 (6*)
BLUE
4 (6*)
REDL
4 (6*)
REDU
   
per raw file same 8 (12*)    
per dichroic observation       12 (18*)
* if flux calibration available

Dichroic: Most often UVES data have been measured in dichroic mode, delivering one blue and one red file almost simultaneously and covering a large part of the optical spectrum at once. Products from this pair of raw files are formally distinct (belong to 2 different data sets) but can be easily recognized from the product names.

top Names of FITS products

UVES product fits files carry names which are intended to contain explicitly some useful information. This is why they are not optimized for brevity. A typical UVES product fits file has a name like:

UV_SRED_118913_2002-05-02T06:22:50.057_REDL564d1_2x2_10.fits

UV_SRED is the product code and identifies a reduced but not fluxed spectrum. The next group is the OB (observing block) which might be helpful for a user e.g. to identify other data from the same OB. The next group (2002-05-02T06:22:50.057)is inherited from the raw file and is useful to uniquely describe this file (since an OB can produce more than one file of the same type). It also marks the timestamp of acqusition (actually of archiving the raw file). This timestamp is identical to the one of the data set.

The last part of the name consists of a setup string, describing: the CCD (BLUE | REDL | REDU); the central wavelength in nm; a short tag for the instrument mode (d1/d2 for the dichroic modes #1 or #2; bl for BLUE arm only, re for RED arm only). 2x2 marks the binning, 10 codes the slit width (10 stands for 1.0 arcsec).

The naming scheme facilitates grouping of similar files (e.g. all files from OB 118913), or e.g. of all files from that night taken with a particular setup. As mentioned above, files taken in dichroic mode are almost simultaneously acquired. In this example, there are in total three SRED files:

Arm name of SRED fits product data set ID
blue UV_SRED_118913_2002-05-02T06:22:50.914_BLUE390d1_2x2_10.fits UVES.2002-05-02T06:22:50.914
red UV_SRED_118913_2002-05-02T06:22:50.057_REDU564d1_2x2_10.fits UVES.2002-05-02T06:22:50.057
red UV_SRED_118913_2002-05-02T06:22:50.057_REDL564d1_2x2_10.fits

more on UVES SCIENCE naming scheme ...

top Ancillary files

There is associated log and QC information available in the following text and graphical files in the data set:

information name description type
a) information about pipeline processing:
association_log UVES.2002-05-02T06:22:50.914.alog association log: list of master calibration files used for processing documentation
association_block UVES.2002-05-02T06:22:50.914.ab executive, more technical text file with all association information documentation (probably not directly useful for the archive user)
recipe_log UVES.2002-05-02T06:22:50.914.rblog pipeline execution log documentation
b) information about quality
grading_nightlog UVES.2002-05-02T06:22:50.914.qcm

comparison of user-defined constraints to actual values; extraction from the nightlog with OB grade, and comments from the observing staff
Note: the nightlog information is available only after 2001-05-07.
The grading applies to the raw files!

documentation
scoring_result UVES.2002-05-02T06:22:50.914.html QC/scoring information about product quality documentation
scoring_log UVES.2002-05-02T06:22:50.914.tlog technical text file with all scoring information documentation (probably not directly useful for the archive user)
comment_file UVES.2002-05-02T06:22:50.914.cmt optional comment file with remarks about product data quality documentation
c) graphical information (preview and quality information)
qc_report r.UVES.2002-05-02T06:22:50.914_0000.fits_1.png graphical QC report, with preview of spectrum and error file documentation

All log files carry the data set ID, with a typical extension. The qc_report names include the data set ID, plus some additional tags which are used for technical reasons.


[QC group logo]  
[ESO][Index][Search][Help][News]