UVES calChecker: calibration completeness monitor (CAL4CAL)
[ ] ?
Paranal date*: 2015-09-02 [ muc02 ] ?
Last header: UVES.
Date on this monitor changes at 21:00 UT.
Refresh frequency: 1/2hr day and night
1. 'how to execute' now maintained by SciOps; 2. raw CALIB file screenshots for quality review, last 7 days, behind the 'raw' links (also linked to HC monitor).
We currently experience technical problems with databases; the incoming data may be not properly accounted for
Long-term calibrations and maintenance
complete overview | how to execute [ ?]
type of calibration
PARASITIC_DARK_BLUE 30 22.4 soft REMINDER: next 16 day(s)
PARASITIC_DARK_RED 30 23.7 soft REMINDER: next 15 day(s)
DEROTATOR 14 18.7 REMINDER: take as soon as possible!
MONITORING_DIC1_346 7 14.1 REMINDER: take as soon as possible!
MONITORING_DIC1_580 7 10.6 REMINDER: take as soon as possible!
MONITORING_DIC2_437 7 14.1 REMINDER: take as soon as possible!
MONITORING_DIC2_860 7 14.1 REMINDER: take as soon as possible!
EFFICIENCY_DIC1_346 30 65.6 REMINDER: take as soon as possible!
EFFICIENCY_DIC1_580 30 65.6 REMINDER: take as soon as possible!
EFFICIENCY_DIC2_437 30 65.5 REMINDER: take as soon as possible!
EFFICIENCY_DIC2_860 30 65.5 REMINDER: take as soon as possible!
Product availability depends on the data transfer to Garching and the archive access there (check the "transfer" and "ngas" flags above).
INFORMATION SPECIFIC TO UVES
The CAL4CAL completeness checks are done for STD_ECH data only. We assume that all other calibrations are triggered by the calibration plan and hence any failures would flag on the
main page ("science").
Number of days scanned:
Range of days for the issue memory : (configured)
Range of days for the calibration memory : (issue memory plus longest validity)
Days in the calibration&issue memory:
*Date on this monitor changes at:
powered by QC [calChecker v4.5]