Common DFOS tools:

dfos = Data Flow Operations System, the common tool set for DFO
*make printable New:

The tool is distributed through the utilities package (utilPack).

- old PANL2 database turned off, replaced by a local database
- tool self-configuration simplified, default for new instruments
- comments truncated after 400 chars.
[ used databases ] databases 'associations' for old format, NLT for new format
[ used dfos tools ] dfos tools none
[ output used by ] output tmp files being used by createReport, calChecker
[ upload/download ] upload/download none



This tool provides queries for OB related information. Since this information is used by various other tools (createReport, calChecker etc.), these queries have been centralized in this helper tool. The situation for the information sources is the following:
instruments switch information source
fors2, crires 2012-10-02 before: associations db; after: NLT
flames, uves, xshooter 2012-04-01 before: associations db; after: NLT
isaac, vimos, visir 2012-09-30 before: associations db; after: NLT
hawki, naco, sinfoni 2012-10-02 before: associations db; after: NLT
amber, midi 2012-10-02 before: associations db; after: NLT
omegacam begin of ops NLT
vircam begin of ops NLT
kmos and all later instruments begin of ops NLT

"Switch" means that OB information before that date is stored in 'associations' database, while after that date it is stored in the nightlog database (NLT). The instrument names with switch dates during their lifetime are hard-coded in the tool. omegacam and vircam were always supported by NLT, as all instruments coming to life later than 2012-10. These are not listed in the tool.

Output. Queries and OB information output files in $TMP_DIR. Call the tool from the command line with option -V and inspect the output. Otherwise the tool works silently as called from createReport or calChecker.

How to use

Type getObInfo -h for on-line help, getObInfo -v for the version number. On the command line, type

getObInfo -d <date> to call it for the local instrument and the specified date, using $DFO_FILE_NAME for queries before the switch, and $PANL_INSTRUMENT after;

getObInfo -C to call it for all dates currently in the calChecker date list ("CAL mode", used internallt by calChecker).

Use option -V [verbose] to get more information.

Use -i <$PANL_INSTRUMENT> to see results from other instruments (but only for dates after the switch!).

Usually the tool works silently if called from createReport or calChecker.

How to install

The tool comes as part of utilPack.

Configuration file



The comments are truncated after 400 characters. Calls for instruments with dates before the switch are only possible on the parent account (because there is automatic matching of $DFO_FILE_NAME and $PANL_INSTRUMENT).