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

Health Check monitor

 

CAL | HC | refs | QC
HealthCheck Monitor
   HOME | UsersGuide
  sl icon ALL INSTRUMENTS
 
all KPI reports
ESPRESSO:
bias: level
Other HC:
QC links:
        [page auto-refreshes after 300 sec]   [stop | on]            [press Ctrl+Shift+R to enforce refresh of scores, dates and news]
ESPRESSO trending system: SCORES (quick-look)
HELP USERS-GUIDE MORE
Last update: 2024-07-14T18:40:10 (UT)
  | now: 2024-07-14T20:07:46 (UT) muc11 QC pipeline: espdr-2.5.0 (installed 2022-06-28)
same group: (U)HR_1x1 HR_2x1 HR_4x2 MR_4x2 MR_8x4   (U)HR_1x1_all HR_2x1_all HR_4x2_all MR_4x2_all MR_8x4_all
General news: NOTE: The Health Check and calChecker services are moved to qcFlow on an instrument by instrument basis. The current pages will not be updated any longer once the move has been finished.
The links to KMOS, UVES, and ESPRESSO have been moved to a new section (qcFlow operational) at the lower part of the navigation bar.
ESPRESSO news:  
Report news:
DATE*: [?] 2024-07-07
report | NLT
2024-07-08
report | NLT
2024-07-09
report | NLT
2024-07-10
report | NLT
2024-07-11
report | NLT
2024-07-12
report | NLT
2024-07-13
report | NLT
r...
Raw CAL displays:
raw raw raw raw raw raw raw
P...
CAL product quality:
products products products products products products products
 
transfer   ngas [?]

HC plot | history ... | plot tutorial ... | contact | HC_docu... | quality events...                 daily/often; important to check     [?]
*Date on this monitor changes at 21:00 UT
BIAS mean, 2x1, slow read-out, HR (scores)
1: RED_0_1
not implemented
2: RED_1_1
not implemented
3: RED_2_1
not implemented
4: RED_3_1
not implemented
5: RED_4_1
not implemented
6: RED_5_1
not implemented
7: RED_6_1
not implemented
8: RED_7_1
not implemented
9: RED_0_0
not implemented
10: RED_1_0
not implemented
11: RED_2_0
not implemented
12: RED_3_0
not implemented
13: RED_4_0
not implemented
14: RED_5_0
not implemented
15: RED_6_0
not implemented
16: RED_7_0
not implemented
17: BLUE_0_1
not implemented
18: BLUE_1_1
not implemented
19: BLUE_2_1
not implemented
20: BLUE_3_1
not implemented
21: BLUE_4_1
not implemented
22: BLUE_5_1
not implemented
23: BLUE_6_1
not implemented
24: BLUE_7_1
not implemented
25: BLUE_0_0
not implemented
26: BLUE_1_0
not implemented
27: BLUE_2_0
not implemented
28: BLUE_3_0
not implemented
29: BLUE_4_0
not implemented
30: BLUE_5_0
not implemented
31: BLUE_6_0
not implemented
32: BLUE_7_0
not implemented


Scores

This is the quick-look version of the HealthCheck (HC) Monitor. It displays scores for each HC report. Scores are flags assessing the compliance of data points with configured thresholds. A green score indicates that the corresponding instrument component is performing as expected (OK) in the monitored time range. A red score is the result of a parameter exceeding these thresholds, and may indicate a problem.

Scoring has both an automatic and an interactive component. The automatic part consists of monitoring, pipeline-processing, and flagging new data once per hour, 24/7. The interactive component is the certification step which is performed by the QC scientist. It involves the analysis of red scores: A confirmation of their validity, an assessment of the severity of the red score and its cause, and often an analysis comment in the AB monitor. In cases of serious instrument issues, feedback to Paranal operations and/or USD is given. However, this analysis step cannot be guaranteed to be available at the same time as the automatic scoring. Do not expect new analysis results during weekends, holidays or other off-duty times.

The last score, per plot, will determine the current plot score, which is displayed as a larger symbol. The other, older plot scores display only the recent history of instrument scores. As part of the automatic scoring, a red score will be automatically overwritten by any new data that produce a green score. The date of any score can be seen by mousing over its score symbol. As part of the interactive analysis, there is also the possibility for the QC scientist to manually adjust thresholds and turn a red score into a green one, or to delete a false red score. Often this occurs after interaction with Paranal staff, after discussing the significance of the alert score. Use the 'contact' link to get in touch.

If available, a table with quality comments is displayed on the scores&comments page, usually offering additional information about data with red scores. A comment may refer to the quality of the pipeline products and not necessarily to the exact parameter scored in this report. Quality comments are entered by the QC scientist as part of the analysis workflow.

Scores are based on the QC data for the last 7 days before the indicated date. This date is always the last date with data for this report.

The 'Quality comments' are collected from the QC scientist certification review and are available for certified nights.

Information on demand:
- scroll over the small symbols and see the individual dates of the underlying data.
- click on them and see the detailed score report for that particular data set.

More ...