The meeting was very useful with lively initial discussions.  Continued
efforts from all involved as well as prompt feedback from shifters are needed
to bring online monitoring to a high level of maturity in the near future.

Some Highlights:

* Meeting Schedule:

It was decided at the meeting today, that we shall meet once a week for the
next few weeks and then go to a bi-weekly meeting.  Weekly meeting could be
Monday, Tuesday, Wednesday, AM or PM.

* Graphical User Interface:

GUI was discussed quite a bit. We need to figure out what interactions are
needed with Examines (Consider the control/switches you have in RCP).

First define what we need, then find / adapt / write a package.

Interactions with examines are useful.
  Some items mentioned:
    (1) Resetting histograms
    (2) Looking at selected regions
    (3) Booking new histograms
    (4) Comparison of histograms
    (5) Spying on histograms/objects
    (6) Starting and stopping examine through GUI

We should compile complaints regarding histoscope so that we can discuss
them with Joy, the histoscope contact person in the CD.

Presentations at the next meetings:

The following detector experts were requested to make presentations on details
of their detector monitoring.

SMT		Lisa
CFT		Drew
Calorimeter	Florencia
Muon		Dave/Linda

Please include the following in your presentations:  (1) a list or an overview
of histograms that detector shifters look at, (2) a reduced set of summary
histograms that would be useful for global monitoring, (3) what tools are
available and are being used, and (4) what tools are needed.

* Run Certification:

There is no objective way of certifying a run as good / bad / maybe. 
--> Judgements vary with time and depend on the judge / analysis.  Start off by
    having detector shifters write down on a piece of paper at the end of each
    run or shift, for a week, to identify criteria.  A set of
    histograms / variables which summarize the detector status is needed.
    They must be accessible offline.
* Eventually, we may want to get a certain level of automation in defining
  detector performance or data quality.
* Primary goal of online monitoring:  Monitor things during data taking to
  fix problems.
* Detector examines are freezing if no data comes in(?) --> shifter doesn't
  know that there is no data flowing --> action needed.
  Solution:  Examines to keep track of time-flow?
             A warning from examine?
* Detector shifters don't know the run state --> action needed.
  Solution:  Some sort of announcement of begin and end run.