UVES calChecker: calibration completeness monitor (CAL4CAL)
[ ] ?
Paranal date*: 2018-04-19 [ muc02 ] ?
Last header: UVES.
Date on this monitor changes at 21:00 UT.
Refresh frequency: 1/2hr day and night
Long-term calibrations and maintenance
complete overview | how to execute [ ?]
type of calibration
DARK_BLUE_1x1,225kHz,lg 90 76.4 soft REMINDER: next 40 day(s)
DARK_BLUE_2x2,50kHz,hg 90 75.5 soft REMINDER: next 41 day(s)
DARK_RED_1x1,225Khz,lg 90 76.4 soft REMINDER: next 40 day(s)
DARK_RED_2x2,50Khz,hg 90 75.5 soft REMINDER: next 41 day(s)
EFFICIENCY_DIC1_346 30 29.2 soft REMINDER: next 9 day(s)
EFFICIENCY_DIC1_580 30 29.2 soft REMINDER: next 9 day(s)
EFFICIENCY_DIC2_437 30 34.9 REMINDER: take as soon as possible
EFFICIENCY_DIC2_860 30 34.9 REMINDER: take as soon as possible
A check on the slit width (blue and red) has been introduced. If science data are taken with a slit >=2.1 arcsec, a WAVE calib is needed with 1arcsec slit. The previous scheme was to take a WAVE calib with the same slit width which could cause issues with remnant on the detector (for ex. when taking WAVE with a 10arcsec slit)
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.6.5]