Initiating a Calibration Config Set for an Instrument
A CalOb Configuration Set consists of the documents listed in (Configuration).
The template instrument now provides a Cookiecutter template of its calibration schedule. Here are the steps to use the IFW Calob Template configuration.
IFW Software Configuration
If not yet done, retrieve and install the complete ICS Framework from the ESO RPMs repository. For more details, please have a look to the installation procedure here.
Please create your software based on the provided template by following the procedure in the Getting Started guide here.
IFW Calob Template Configuration
Assuming that the instrument name used for the template was micado, the files pertaining to the CalOb Configuration are presented in the following table:
File |
Description |
---|---|
micado/mic-resource/config/calob/configuration.cfg.yaml |
Holds the general configuration and paths |
micado/mic-resource/obd/calob |
Holds two OBD files to be used for the template calibrations |
micado/mic-resource/obdx/calob |
Holds one OBDX file to be used for the template calibrations |
micado/mic-ics/calob/src/mic/calob/calob_schedule.py |
The template schedule which will produce the daily calibrations |
micado/mic-ics/calob/src/mic/calob/calob_tables.py |
The tables to be used inside the schedule or obdx files |
micado/mic-ics/calob/src/mic/calob/calob_ext_functions.py |
The tables to be used inside the schedule or obdx files |
These files should be modified according to the instrument needs following the instructions given in the previous chapters of this document.
IFW Calob Template Data
At the moment of writing this document, the best way of providing the CalOb Configuration template is to use simulated/pre-generated data for simplicity. Find these FITS files in:
micado/mic-ics/calob/resource/tmp_image/mic/calob
The configuration provided with the IFW Calob Template will use these files and produce a simulated Daily Calibration OB.
Executing the Generator
Ensure “DATAROOT”, “CFGPATH” and “INTROOT” are defined.
Example:
$ echo $DATAROOT /scratch/eltdev/DATAROOT $ ll /scratch/eltdev/DATAROOT drwxr-xr-x 2 eltdev vlt 80 May 11 14:48 image/ $ echo $CFGPATH /scratch/eltdev/INTROOT/resource:/elt/ifw/resource $ echo $INTROOT /scratch/eltdev/INTROOT
Ensure that the CII Services are up and running:
These will normally be started automatically on the ELT development machines.
Install the template instrument.
$ waf configure $ waf build install
Execute the example CalOb Generator executable “calobGenerator”:
$ calobGenerator -c config/ifw/calob/example/configuration.yaml $
To execute without the historic feature and showing output in the console:
$ calobGenerator -c config/ifw/calob/example/configuration.yaml -n -x $
The following output files have been generated:
After executation, the output Daily Calibration OB generated can be found in:
DATAROOT/calob/mic/daily_calibration/daily_calib.obd.json
with the template CalOb Configuration File provided.
The Calibration DB file can be found in:
$DATAROOT/calob/mic/db/calibration_history.db
Note, the user shall normally not tamper with this file.
Logs generated during execution are stored in the log file:
./ifw-calob.log
Normally the user shall not access this file directly, but shall use the CII Log Service GUI to browse the logs.