![]() |
|||||
|---|---|---|---|---|---|
| CRIRES pipeline: general information |
|||||
|
|
This page is the CRIRES pipeline page with information about CRIRES data and pipeline processing. Raw data are selected, associated, and inserted into a reduction mechanism which produces calibration products, science products, and Quality Control information. This mechanism is the CRIRES data processing pipeline. It is operational since the start of Service Mode observations.
The main functionalities of the CRIRES pipeline are:
DFO Garching creates:
Find the description of CRIRES data processing and pipeline recipes here:
There are two instances of the CRIRES data reduction pipeline:
The automatic mode is used for quick look purposes and for on-site quality control. It processes all raw data sequentially, as they arrive from the instrument. It reduces science data, using pre-manufactured standard sets of calibration products. It is not tuned to obtain the best possible results. The optimized mode is the mode, which uses all data of a night, including the daytime calibrations. The calibration data are sorted and grouped according to their dependencies. Master calibration data are created. Their quality is checked. The certified, closest-in-time products are finally associated to the science data of a night. This is the way all calibration data in supported modes are processed by DFO Garching, as are all science data from Service Mode programmes.
All settings offered for Service Mode are pipeline supported. QC Garching processes the following CRIRES data:
Raw data. The CRIRES detector is a 4x1 mosaic of 4 Aladdin III arrays, each with 1024x1024 pixels. Only the lower 512 pixels of each array are read out so that the total mosaic consists of 4x1024x512 pixels. The pixel size is 27 microns. A fifth Aladdin III detector is used in the slit viewer. The arrays are read out using standard ESO IRACE controllers with 64 channels (4x16) for the science arrays and 32 channels for the slit viewer, respectively.
Extensions. Raw calibration and science data come as FITS files with one primary header unit (HDU) and four extensions. The primary HDU has all keywords necessary to identify the observation and the state of the telescope and the instrument; the data part is empty. Pixel data are stored in the extensions, one extension for each array. Acquisition frames have only a primary HDU containing keywords and the slit viewer image. Products. Pipeline products have varying formats. Wherever appropriate, also product files have four extensions with the relevant product data for each array (either pixel data or fits tables). Runs performed in Service Mode receive a set of DVDs containing
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||