Help for Health Check monitor

last update: December 21, 2012 | contact

topics: Update information and process monitor | navigation | news | result table | plot symbols | statistical functions | scores & quick-look | shiftleader's page

The Health Check monitor is developed and maintained by QC Garching. It provides information about the health of the instrument and about calibration quality.

Update information and process monitor

Last update: 2012-11-11T09:35:18 (UT) (0d 02h:05m ago)
| now: 2012-11-11T11:37:22 (UT)
| QC pipeline: giraf-2.9.1 (installed 2012-04-27)

Last update: timestamp of creation of this page and plot (UT)

Now: current timestamp (UT) (press Ctrl+Shift+R to enforce reloading of the page, it may be cached)

(0d 20h:05m ago): difference of both timestamps (requires javascript enabled)

QC pipeline: this is the name, version and installation date of the pipeline being currently in use for processing at QC (for comparison to the version installed on Paranal)

ftp monitor. For HC plots with OPSLOG data, there is a monitor for the ftp process (OPSLOG files from Paranal to Garching) and the parsing process (executed on the QC machines). A javascript calculates the difference between NOW and the respective timestamps of these two processes. If these differences are less than 2 hours, the corresponding boxes are coded green, otherwise red. If after 12 UT no OPSLOG file has arrived, the code is grey, since then it is unknown if there is a problem or if no OPSLOG data are available (because e.g. all daytime calibrations have already been processed before 12 UT).

Possible values:
ftp
parser
ftp and parser results not older than 2 hours
ftp
parser
ftp result older than 2 hours, may indicate a problem; parser is up and running
ftp
parser
ftp and parser results older than 2 hours; the parser process is stopped; the ftp process cannot be monitored (so it could be ok)
... ftp
parser
no ftp result since 12 UT, parser up and running, cannot decide if ftp is broken or no OPSLOG file availabe yet

What to do if HealthCheck monitor page is outdated? (intended for our Paranal partners)

The Health Check monitor pages are refreshed upon discovery of new data, but at least once in 24 hours. If a page is found to be older than 24 hours (as indicated by the "... ago" field) this might indicate a problem (this field is calculated by your browser).

The first thing to check is: does this problem show up only for the current report, or for all reports of a given instruments, or for all instruments? In the latter case, there is most likely a network or a database problem. It may be known already, check first with DHA. If the problem is specific to one instrument, send a mail ("contact") if you expect the QC scientist to be able to read it; to the general list qc@eso.org, if not. On a weekend generic problems will most likely be picked by the Garching maintenance teams, they provide service 7 days a week during daytime. Again ask DHA for support, they know whom to contact.

If there is a problem with one report only, this is most likely due to the process on the QC machine. Pls contact the QC scientist in charge.

What to do if the "ftp" or the "parser" watch flags are red? (intended for our Paranal partners)

Both flags watch the health of the opslog data transfer and the parsing process on the QC side (see above). If the ftp flag is red, pls. ask DHA to check. It may help to click on "MORE" first, there you see all watch flags. This will tell you about a general problem. A gray ftp flag does not indicate a problem.

If the parser flag is red, send a mail ("contact") if you expect the QC scientist to be able to read it; to the general list qc@eso.org, if not.

Any problem related to these two flags is not considered very urgent since the opslog data are a fallback solution in case of trouble with the data transfer process.


[ top ]Navigation

HELP USERS-GUIDE MORE

This navigation links to:

  • this file;
  • the process description (users guide);
  • a file with additional information (time zone information, link to ASM, technical monitor of ftp and parser process).

Group navigation. Plots are often grouped together. For instance, plots with detector properties could be grouped like:

same group: bias   dark linearity&gain fp-noise contamination

  daily/often; important to check This marks the most important plots. These are the ones which are fed daily by dedicated health check calibrations. These are also the ones which should be checked daily. The other ones are also of interest but are not filled so frequently (nevertheless all are updated at least once a day or when new data are detected).

The second line displays the report scores (see here).


[ top ] News. There are three kinds of 'news' (messages on the HC monitor): general news (applicable to the HC monitor in general), instrument news (applicable to all HC reports of a particular instrument), and report news (messages about current issues). The report news can be managed interactively, in the same way as the calChecker analysis cases:

Report news: 2012-11-26 The low flat lamp issue is followed up in PPRS-47984 [whummel@eso.org]
  • click 'edit'
  • provide your credentials (if unknown or forgotten, contact qc@eso.org)
  • provide a new comment, edit or delete an existing comment
  • for new or updated entries, provide a date and your email in addition to your comment.

The HC comment editor is available to both parties of the closed QC loop: QC and SciOps. In particular, daytime or nighttime astronomers on Paranal are encouraged to use the editor to exchange information with their colleagues.

Note that the report news have a validity period of 14 days. It is assumed that any quality issue related to a HC report is either solved, or becomes obsolete after that time. The report news are not designed to store permanent information.

You can also use the link edit COMMENTS ... on the 'score overview' page and select any HC report of a given instrument for comment editing. This is particularly useful if e.g. a new quality issue has occurred and a related comment should be entered for several affected HC reports.

An updated report comment will be visible immediately on the corresponding HC report. You may need to enforce page refresh with CTRL+R.

Note that report news will not immediately be visible on the Paranal ('PL') mirror site, but have to wait for replication (after max. 15 minutes).


DATE*:
2012-12-09
report | NLT
2012-12-10
report | NLT
2012-12-11
report | NLT 
2012-12-12
report | NLT
2012-12-13
report | NLT 
2012-12-14
report | NLT
Product quality:
products products products products products products

Data Quality links. With the same look and feel as on the calChecker, this panel displays links to the pages with complete information about the data quality (links products). Find more information about the data quality links in the calChecker help.

There are also links to the raw data reports and the nightlogs for the last 7 days. The nightlog links are labelled NR for the old nightlog database, and NLT for the new nightlog tool. The nightlog section requires a password for login. The new nightlogs are linked to the User Portal and the NLT database.


OPSLOG information. OPSLOG data are created by the Paranal on-line pipelines. They are less accurate than the QC-generated QC parameters but are included (if available) in the HC monitor as a fall-back solution. If OPSLOG data are included, their last date is listed here. There is the option to inspect or download these data in the result table below the graphical report.

last OPSLOG data:
2010-11-06*
monitor
ftp
parser
last files...


Quick-look navigation, history, tutorial, contact. The HC plots have a link labelled scores&comments... . It has as counterpart on the QUICK-LOOK version: HC plot. By using these links, you switch forth and back between the full version with graphics, and the score version for quick-look.

scores&comments... |FULL | history ... | plot tutorial ... | contact                 daily/often; important to check     [?]
*Date on this monitor changes at 21:00 UT

Full report. Some HC plots have an additional FULL version covering the whole data history. They are linked as orange square FULL.

History. This link opens the set of HISTORY plots (if available) in a separate window.

The HISTORY plots come in the same form at as the HC plot and present the historical evolution. Click on the red arrows to move forth and back in time, or on the symbols for direct navigation:
close window history: 2003 2004 2005 2006   2007   2008   HEALTH FULL
  ... ... ...

"HEALTH" is the HC plot, the only one to contain OPSLOG data (if configured and if available).
"FULL" is an optional link to the FULL report combining all historical data points in one plot (if available).

Tutorial. This link provides additional information about the QC items, the data, the algorithms etc. These pages are in the instrument QC section.

Contact. Send an email to the QC scientist responsible for this particular HC page.


Date change. Date on this monitor changes at 21:00 UT. This is 9 hours later than the Paranal convention changing date at 12:00 UT. This is done (1) to align with calChecker, (2) to have nighttime observations and the daytime calibrations under the same date. Effectively a new date starts shortly before the new night.


[ top ]Result table

It has two parts:

  • information and research
  • statistical results and downloads

The first part has a link to display (e.g. for printing) the HC plot ("Print") and links to the corresponding QC1 database table for browsing and plotting ("Information and research"), sometimes with other useful links.

Print: Information and research: 
- png file - advanced studies: QC1 browser | QC1 plotter
Plot
?
Symbol
?
Source* OPS?** Average ? Thresholds ? N_data QC1 parameter Data downloads Remarks
method value unit method value
1 QC1DB yes (6) MEAN 151.2 ADU 10% +/-15.1 51 flux this | last_yr | all median BIAS level
plot number
plot symbol
data source
OPSLOG entries (same as OPSLOG table)
applied methods, trending results, units, number of data
links to download the data (this time range; last 365 days; all data)
remarks

The second part has the result table. Find in this table more details about the applied statistics and the current trend. Here you can usually also download the plotted data sets. #66CCFF


[ top ]Plot symbols

The symbols used in the plots are displayed in the column "Symbols". An attempt has been made to display them in the HTML pages as they are shown on the MIDAS plots, but some symbols do not exist as HTML code and show up here as bracketted number, like [20]. The table below lists all possible plot codes and reveals that [20] stands for a filled triangle.

SYMBOL meaning   SYMBOL meaning
1 dot .   11 lozenge ◊
2 open circle O   12 horizontal bar –
3 square □   13 vertical bar |
4 triangle Δ   14 right arrow →
5 plus +   15 arrow up ↑
6 cross x   16 left arrow ←
7 asterisk ∗   17 arrow down ↓
8 star *   18 filled hexagon
9 plus square   19 filled square ■
10 cross square   20 filled triangle ▲
      21 filled lozenge

[ top ] Statistical functions

Average:
method implementation
MEAN average (with clipping if combined with certain threshold option, see below) MIDAS: stat/tab; outputr(3)
MEDIAN median (with clipping if combined with certain threshold option, see below)   MIDAS: stat/ima; outputr(8)
FIXED=val1 fixed value  
NONE nothing applied  

The average values are listed in the result table (together with their units and the number of data points evaluated). They are indicated in the plots by a solid line. For MEAN and MEDIAN, they are clipped (outliers beyond the thresholds are removed after first calculation, then the calculation is repeated with the cleaned data set) if combined with certain threshold options (see below).

Thresholds:
method implementation clipping
PER=val1 relative thresholds percentage of average; e.g., PER=10: thresholds are 10% of average value yes
OFF=val1 relative thresholds as PER, but fixed offset; e.g., OFF=0.05: thresholds are average ± OFF yes
VAL=val1,val2 fixed thresholds thresholds are independent of average; val1, val2 listed in the result table no
none nothing applied   no

The threshold values are listed in the result table. These values are indicated in the plots by broken lines, and are used to detect and mark statistical outliers. PER and OFF thresholding is relative to the average value. PER and OFF thresholding is fixed relative to the average value. VAL thresholding is completely static and might represent e.g. a specification or an alarm level based on experience or specifications.

Outliers. Statistical outliers are marked if thresholds are defined and plotted. Marking is done by a red asterisk (to become blue if the symbol color is red).

Data points outside the Y range. These data points are marked by a red arrow.

OPSLOG data points. The data points from OPSLOG files (produced by the on-line Paranal pipelines) are always marked by a filled blue circle .

LAST data point. If configured, all data points from the last date are highlighted by a large magenta circle .

Data source:
method
QC1DB QC1 database (final, certified QC1 parameters from pipeline processing by QC)
OPSLOG QC1 ops logs (preliminary QC1 parameters from automatic pipeline processing on Paranal)
LOCAL Local data source (QC1 parameters not yet ingested into QC1 database, e.g. since they are under development; not considered a permanent option!)


[ top ] Scores and quick-look

Quick-look version. Clicking on scores&comments brings you to the score overview (QUICK-LOOK page). It displays the score result table:

FF level (scores, last 7 days up to 2010-01-31*)
1: Med1
3|
2: Med2
2|
4: IFU1
4|
5: IFU2
2|
6: Argus
3|
*Date on this monitor changes at 21:00 UT

It displays scores for each HC report. Scores are flags assessing the compliance of data points with configured thresholds. A green score symbol indicates that the corresponding instrument component performs OK in the monitored time range, a red one may indicate a problem.

Each plot in the report has one score table cell. Each cell displays a set of scores. Scores are displayed for the last 7 days only, up to the specified date. This time range is aligned with the calChecker page which also has a standard depth of 7 days. Note that the specified date corresponds to the last date with an available measurement (i.e. with a processed calibration file) which is not necessarily today. If you move your mouse over a score symbol, the corresponding date will display as tool tip. If you click on a score symbol, the full score report for this product will display.

Scores are based on QC1 parameters. They are checked against an upper and lower threshold. If compliant, the score is 0, otherwise 1. An outlier is scored as 1.

All scores are aggregated to plot scores and report scores. If no outlier is found, the corresponding plot is scored OK and marked green. Outliers get a NOK score and are marked red:

2: GLOW
2|
This plot has two QC data points in the monitored time range, both scored OK.   2: GLOW
2|
... a NOK score.

Comments.

The comment section has two parts:

  • the (general and report) NEWS section replicated from the main HC report page
  • quality comments as entered by the QC scientist upon certification
Quality comments:
Plot Date* AB name score product quality comment
Plot 4 2010-01-22 GIRAF.2010-01-23T06:50:12.384_tpl.ab
saturated
Plot 4 2010-01-23 GIRAF.2010-01-24T01:37:34.812_tpl.ab
saturated
Plot 4 2010-01-23 GIRAF.2010-01-24T06:02:36.832_tpl.ab
ok
Plot 5 2010-01-23 GIRAF.2010-01-24T07:45:59.520_tpl.ab
ok
"Date" links to complete AB product page; "AB" links to score report

Only those scores display here which got a comment (which usually but not exclusively refers to a red score). These comments are intended to better understand a red score.

Plot scores. If the last QC data point for a plot is found NOK, the total score for the plot is NOK and marked red (see below). If any other QC data point is found red but the last one is green, the total score for the plot is OK and marked green (since it is assumed that the problem is solved in the meanwhile).

2: GLOW
2|
Both data points are scored OK. The plot score is OK.   2: GLOW
2|
Same plot, with one data point scored NOK (but not the last one) . The plot score is OK. 2: GLOW
2|
Same plot, with the last data point scored NOK. The plot score is NOK. 3: ALL_GLOW
multiple dataset
Note: Plots with multiple data sets cannot be scored.

Report scores. Total scores per plot are accumulated to report scores and displayed at larger size (see example above). Report scores can be OK, NOK or grey ("not implemented"). If no report score is red (some may be grey), the plot score is OK and displays green. A single red plot score will turn the report score also red. Reports without scoring are marked grey and are not evaluated further.

Other possible tags:

multiple dataset more than one dataset in a single report; since scores are always for a report, this situation is usually avoided but may make sense exceptionally
computed values as displayed are computed after download from the database; for technical reasons, these values cannot be scored

Accumulated report scores are repeated in the group navigation bar, for quick reference:

same group: bias   dark linearity&gain fp-noise contamination

Group scores. Likewise, report scores are accumulated to group scores. They are displayed in the vertical navigation bar at left:

FLAMES/GIRAFFE:

If you want to monitor the current health of an instrument, you start with its navigation bar. Either all items are green, or you find at least a red one. In that case, follow any red score to the group level, find the corresponding report and plot scores. There you may want to check the detailed HC plot. All in all 2 levels to see the QC data point which causes the alert, and 3 to see all details.


[ top ] Shiftleader's page

sl icon ALL INSTRUMENTS

Designed as the highest-level overview, it offers a monitor of all instrument scores. It comes in three versions: a snapshot of the current situation, and history overviews of the last 7 and 30 days.