make printable		see also:
		documentation of monitor tools: dfosExplorer | calChecker | dfoMonitor | ABmonitor | mucMonitor | cascadeMonitor
		tune your browser
		public versions of monitors: http://www.eso.org/~qc/dfos/monitors.html

Monitors and GUIs

The DFOS system has several monitor tools designed as graphical interfaces to the workflow tools:

	Infrastructure	Memory/archive	Daily workflow
tool name	dfosExplorer	histoMonitor	calChecker	dfoMonitor	getStatusAB	mucMonitor	cascadeMonitor
GUI name (under $DFO_MON_DIR)	dfosExplorer.html	FINISHED/...	CALCHECK/calChecker.html	dfoMonitor.html	status_<date>.html	mucMonitor_Mucnn.html	cascadeMonitor
external version?	no	yes*	yes*	yes*	yes**	yes*	yes, linked to mucMonitor

* linked under www.eso.org/~qc/dfos/monitor.html
** linked under www.eso.org/CAL

dfosExplorer

That tool scans your dfos installation for completeness and for being up-to-date. It checks your installation against a reference installation.

It can be called from the command line anytime, or from the GUI itself (under $DFO_MON_DIR), or from a cronjob. The latter option is recommended. The tool dfosCron can launch the tool. It is recommended to be launched once a day.

histoMonitor (also called the nautilus)

This is actually a web site with all historical information about data processing for a given instrument. It provides, per QC date, pages with complete AB monitor information, links to QC plots, processing logs, scores, comments, data report, nightlog, etc. These pages are sorted by month and year. There is a second branch for the historical packages, which sorts by period.

calChecker

This tool monitors the execution of the Paranal calibration plan. It uses a stripped-off version of the OCA rules to check for completeness of the calibrations for all SCIENCE setups taken. It evaluates validity ranges.

dfoMonitor

This tool is the core of the DFOS system. Called from the command line, or from some of the DFOS tools, it scans the dates with unprocessed data in the system. It evaluates the status values in DFO_STATUS under $DFO_MON_DIR for each date to be scanned. Depending on the state returned, the tool uses color coding to illustrate e.g. the availability of the next step, with buttons for launching the next step.

The tool is organized such that the user can work along the offered options.

AB monitor (getStatusAB)

This GUI monitors the processing status of the set of ABs per date. For each AB, there is one line, with links to the AB and the execution log. During execution, the active ABs are highlighted. Colour coding marks ABs as being scheduled, active, or executed. In the batch queue mode, dependencies of ABs are indicated (blocked/scheduled).

mucMonitor

This tool visualizes the condor processing situation on a MUC blade. It is particularly useful on the multi-user blades. It gives an overview of the current condor activity (nodes executing condor jobs) and the pending queue.

cascadeMonitor

This tool visualizes the execution of the current condor processing cascade on a MUC blade. It helps understanding the dependencies in a cascade, analyze recipe performance and interplay with the condor processing nodes on a muc blade.