mirror sites: PL (internal link) HQ     [?]

Calibration completeness monitor

 

[all links are internal]             [page auto-refreshes after 300 sec]   [stop | on]            [press Ctrl+Shift+R to enforce refresh of "ago" time information]
CAL | HC | refs | QC
CALCHECKER
  HOME | HELP
  sl icon ALL INSTRUMENTS
UVES&FLAMES/UVES
QC links:
CAL
UVES calChecker: calibration completeness monitor (CAL4CAL)
Last update: 2018-04-20T04:26:38 (UT)
[?]
  Paranal date*: 2018-04-19         muc02 [?]   server: www.eso.org HQ
HELP ASSOC-RULES DETAILS
Last header: UVES. 2018-04-20T00:17:21.742.hdr
transfer     ngas    [?]
  *Date on this monitor changes at 21:00 UT. Refresh frequency: 1/2hr day and night
General news:
Long-term calibrations and maintenance complete overview | how to execute     [?]
type of calibration validity (days) age (days) evaluation
DARK_BLUE_1x1,225kHz,lg90 76.4soft REMINDER: next 40 day(s)
DARK_BLUE_2x2,50kHz,hg90 75.5soft REMINDER: next 41 day(s)
DARK_RED_1x1,225Khz,lg90 76.4soft REMINDER: next 40 day(s)
DARK_RED_2x2,50Khz,hg90 75.5soft REMINDER: next 41 day(s)
EFFICIENCY_DIC1_34630 29.2soft REMINDER: next 9 day(s)
EFFICIENCY_DIC1_58030 29.2soft REMINDER: next 9 day(s)
EFFICIENCY_DIC2_43730 34.9REMINDER: take as soon as possible
EFFICIENCY_DIC2_86030 34.9REMINDER: take as soon as possible
UVES news: 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)

       

HELP | Q&A | ASSOC-RULES   history... | contact   monitors: DataTransferMonitor | BandWidth
  science  .   cal4cal  .    [?]     Product availability depends on the data transfer to Garching and the archive access there (check the "transfer" and "ngas" flags above).
  daytime calibs:   pending
DATE*:   [?]
[color if science data acquired]
2018-04-13
VM
33
report | NLT
2018-04-14
SM
62
report | NLT
2018-04-15

report | NLT
2018-04-16
SM
22
report | NLT
2018-04-17
SM
51
report | NLT
2018-04-18
SM
1
report | NLT
2018-04-19
SM
27
report | NLT
LOST?
[not applicable
for 'cal4cal']
Calibration action?     [?]
[take these data types ...
Setup:
... for these setups]
r...
Raw CAL displays:     [?]
raw raw raw raw raw raw raw      
P...
CAL product quality:     [?]
products products products products products products products      
Data types: Setup:        
STD_ECH_BLUE 1x1_low_225_DI1_CD#1_346  
 
 
 
ok
 
ok
  all ok  
1x1_low_225_DI1_CD#2_390  
 
 
 
ok
 
ok
  all ok  
1x1_low_225_DI2_CD#2_437  
 
 
 
ok
 
ok
  all ok  
STD_ECH_RED 1x1_low_225_DI1_564  
 
 
 
ok
 
ok
  all ok  
1x1_low_225_DI1_580  
 
 
 
ok
 
ok
  all ok  
1x1_low_225_DI2_860  
 
 
 
ok
 
ok
  all ok  
 
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").
CONFIGURATION           [?]
Number of days scanned: 7
Range of days for the issue memory (configured): 20
Range of days for the calibration memory (issue memory plus longest validity): 27
Days in the calibration&issue memory:
*Date on this monitor changes at: 21:00 UT
powered by QC [calChecker v4.6.5]   increm