Checks and messages of the monitor

Summarized are the checks performed by the monitor in different modes, and also the error, warning and info messages printed usually.

Checks in Offline mode

First, the TestECProgress function is invoked in Offline mode. This test is passed, if:

  • There are at least 10 events in the datafile
  • There is at least 1 VFAT in those first 10 events that
    • is present in each of the first 10 events
    • has always valid CRC and Footprint
    • its event counter progresses one by one as the events progress
The first of the VFATs that meet this above criteria, is called the watcherVFAT. It will be used to do further tests during reading of the data.

If TestECProgress is successful, the monitor goes on to data reading. Checks on each event are done. A message (ERROR or WARN) is printed in the following cases (and maybe some action is also taken):

  • watcherVFAT is missing from an event (ERROR, skip this event)
  • event counter in the watcherVFAT frame and the event counter in the datafile (btag) are different (ERROR, no action)
  • watcherVFAT has wrong event counter progress (WARN, no action)

Then VFATs are processed in each event.

Checks in Offline (minimum checks) mode

No event checks are done at all, only the working VFATs are processed.

Checks in Scan or trimDAC mode

The same TestECProgress is done as above, with the same conditions and messages.

Then events per cycle are checked to be in the meaningful range (0...256).

If TestECProgress is successful and the events per cycle number is meaningful, the monitor goes on to data reading. Checks on each event are done. A message (ERROR or WARN) is printed in the following cases (and maybe some action is also taken):

  • watcherVFAT is missing from an event (ERROR, skip this event)
  • event counter in the watcherVFAT frame and the event counter in the datafile (btag) are different (ERROR, no action)
  • event counter is bigger than the given number of events per cycle (WARN, skip this event)
  • watcherVFAT has wrong event counter progress (WARN, no action)
Then, when the reading is at the maximal number of cycles per configuration, next config is loaded. One receives a warning if:
  • a next configuration cannot be loaded (ERROR, exit data reading)
  • config number from the datafile (btag) and from the configurations input are not the same (ERROR, no action)

-- MateCsanad - 04-Feb-2010

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2010-02-05 - MateCsanad
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    TOTEM All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback