Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.eso.org/~qc/dfos/writeBreakpoint.html
Дата изменения: Mon Mar 21 13:34:37 2016 Дата индексирования: Sun Apr 10 01:11:29 2016 Кодировка: Поисковые слова: п п п п п п п п п п п п п п п п п п п п п п п п п п п п п |
Common DFOS tools:
|
dfos = Data Flow Operations System, the common tool set for DFO |
![]() |
New: |
The tool is distributed through the utilities package (utilPack). tools related to calSelector: general overview of calSelector here
|
This tool manages new entries in the QC1 database table calsel_breakpoints, for a given instrument. Breakpoints are instrumental events (defined by mjd_obs and per instrument and raw_type) that are "fundamental" in the sense that no association between a science file and a calibration file is allowed that would cross the breakpoint. The OCA rules either have no time preference (then the closest-in-time match is chosen), or relative time preferences (PREVIOUS or NEXT), but they cannot cope with singular events. This is the purpose of the breakpoints.
Breakpoints are stored in the QC1 database table calsel_breakpoints. The tool writeBreakpoint guides the user in a dialogue through the ingestion process.
You need to specify in a dialogue:
After confirmation, the tool determines from the specified RAW_TYPEs the affected PRO.CATGs by usage of the latest calSelector OCA rule set. It is possible to specify a different set in the tool dialogue in case historic breakpoints are inserted. Then, the tool uses 'qc1Ingest' and writes all fields into calsel_breakpoints.
Type writeBreakpoint -h for on-line help, writeBreakpoint -v for the version number. Type
writeBreakpoint
to open the dialog.
The tool comes as part of utilPack.
None.