Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/~qc/dfos/getObInfo.html
Дата изменения: Mon Aug 31 12:25:20 2015
Дата индексирования: Sun Apr 10 00:36:22 2016
Кодировка:

Поисковые слова: impact
getObInfo

Common DFOS tools:
Documentation

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

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

  v1.2:
- all instruments configured for NLT (nightlog tool)
v1.2.6:
- comments truncated after 300 chars.
[ used databases ] databases PANL2 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

getObInfo

Description

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: PANL2; after: NLT
flames, uves, xshooter 2012-04-01 before: PANL2; after: NLT
isaac, vimos, visir 2012-09-30 before: PANL2; after: NLT
hawki, naco, sinfoni 2012-10-02 before: PANL2; after: NLT
amber, midi 2012-10-02 before: PANL2; after: NLT
omegacam begin of ops NLT
vircam begin of ops NLT
kmos and all later instruments begin of ops NLT

"Switch" means that before that date, OB information is stored in PANL2 database, while after it is stored in the new nightlog tool (NLT). Technically, it is important to know that the PANL2 database is hosted on Paranal, with less connectivity and stability than the NLT database which is hosted in Garching. Also, the queries to these two different database have a different structure.

This complexity is hidden from the user. The instrument names and the corresponding switch dates are hard-coded in the tool. omegacam and vircam were never suported by PANL2. kmos and all later instruments came into operations after the switch date.

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 $PANL_INSTRUMENT and the specified date, or

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

Use option -V [verbose] to get more information. Use -i <$PANL_INSTRUMENT> to see results from other instruments.

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

How to install

The tool comes as part of utilPack.

Configuration file

None.

Notes

The comments are truncated after 300 characters.