Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.eso.org/~qc/docu/detmon/index.html
Дата изменения: Mon Nov 7 11:30:03 2011 Дата индексирования: Mon Feb 4 22:56:20 2013 Кодировка: Поисковые слова: europa |
![]() |
|||||||
---|---|---|---|---|---|---|---|
Include detmon as a generic pipeline |
|||||||
|
For reasons of better and more efficient maintenance of the pipeline recipes, the SDD pipeline group introduces
generic pipeline recipes. Generic pipelines collect data processing tasks
like detector monitoring which are not specific to an instrument. SDD offers now both lingain recipes, the optical CCD and the NIR array detector
version in one generic pipeline. In the future, SDD plans to remove the detmon recipes from the instrument pipelines
and will only maintain the generic pipeline version.
This page describes the procedure how to migrate
the operational
detmon pipeline recipe as part of the instrument pipeline (IP) to
the generic detmon pipeline recipe (GP). This page does not describe,
how to put the detmon recipe into operations for the first time.
The detmon recipe is currently implemented in several instrument
pipelines. Either the version for optical CCDs or the version for
NIR arrays is included. Both recipes are also available in the new
generic detmon pipeline. In the long term it is planned to use the
recipe from the generic pipeline instead of the recipe implemented
in the instrument specific pipeline. The migration procedure
is explained in the detmon pipeline user manual vers 1.0.1, 2010-11-02 (see bottom
of that page: detmon pipeline manual ) and is
repeated on this page. Additional information is given on the esorex
web page. The migration has to be done only once. The procedure does not has to be repeated
for generic pipeline upgrades.
esorex --recipe-config=${HOME}/.esorex/detmon_{opt|ir}_lg_{instument}.rc detmon_opt_lg SOF
where SOF can be the set of files
extracted from an operational linearity AB.
Note that the DO_CLASS values (the raw type tags, which appear after the raw file name in the SOF,
which are specified in {instrument}_classification.h are ON_RAW and OFF_RAW and might
differ from tags used by the IP version.
Note also that the PRO.CATG values of the GP products might differ from the IP version.
The
--recipe-config=${HOME}/.esorex/detmon_{opt|ir}_lg_{instument}.rc tells esorex to
read the instrument specific parameters for recipe detmon_opt_lg (or detmon_ir_lg, whatever version is applicable) from the specified file
under ${HOME}/.esorex.
|
Generic pipeline detmon recipe |
If the raw frames have no detector extensions, the default detmon recipe configuration --exts=0 allows to process them.
If the raw frames are multi-extension fits files the user can either
1) (monolithic processing mode) use --exts=-1 to process all extensions and generate products with same
number of extensions as the raw frames.
2) (detector splitting processing mode) use --exts=n to get a product file with one extension corresponding to
extension n.
esorex --recipe-config=${HOME}/.esorex/detmon_ir_lg_vircam_4.rc detmon_ir_lg --ext=4 SOF
esorex --recipe-config=${HOME}/.esorex/detmon_ir_lg_vircam_9.rc detmon_ir_lg --ext=9 SOF
esorex --recipe-config=${HOME}/.esorex/detmon_ir_lg_vircam_16.rc detmon_ir_lg --ext=16 SOF
meaning for each detector a separate detector specific configuration file has to be maintained.
The DFOS tool processAB version 1.10 supports recipe specific configuration and
detector specific configuration. See extraction of config.processAB :
# ======================================================================
# 2. esorex configuration file names for generic pipelines
# List here the name(s) of esorex configuration file(s) of general pipeline(s) (e.g. detmon)
# RAW_TYPE: usually just one, but could be more
# DET_ID: required only if you need to specify config files per detector (avoid if possible)
# if not needed, just enter ANY, will be ignored
# CONFIG: name of config file for generic pipeline, under $HOME/.esorex
# ============================================================================================
#GENERAL RAW_TYPE DET_ID CONFIG
#Example for arm-specific configuration:
GENERAL DETMON_IR_ARM ANY detmon_ir_lg_xshooter.rc
GENERAL DETMON_UV_ARM ANY detmon_opt_lg_xshooter.rc
#Example for detector-specific configuration, with a default config file and
# several detector specific configuration files:
# GENERAL DETMON 1 detmon_ir_lg_vircam_DET01.rc
# GENERAL DETMON 2 detmon_ir_lg_vircam.rc
# GENERAL DETMON 3 detmon_ir_lg_vircam_DET03.rc
# GENERAL DETMON 4 detmon_ir_lg_vircam_DET04.rc
# GENERAL DETMON 5 detmon_ir_lg_vircam_DET05.rc
# GENERAL DETMON 6 detmon_ir_lg_vircam.rc
# GENERAL DETMON 7 detmon_ir_lg_vircam_DET07.rc
# GENERAL DETMON 8 detmon_ir_lg_vircam.rc
# GENERAL DETMON 9 detmon_ir_lg_vircam.rc
# GENERAL DETMON 10 detmon_ir_lg_vircam_DET10.rc
# GENERAL DETMON 11 detmon_ir_lg_vircam_DET11.rc
# GENERAL DETMON 12 detmon_ir_lg_vircam_DET12.rc
# GENERAL DETMON 13 detmon_ir_lg_vircam_DET13.rc
# GENERAL DETMON 14 detmon_ir_lg_vircam_DET14.rc
# GENERAL DETMON 15 detmon_ir_lg_vircam_DET15.rc
# GENERAL DETMON 16 detmon_ir_lg_vircam_DET16.rc
# ======================================================================