search

cmsdaq / DAQExpert

New expert system processing data model produced by DAQAggregator
1 stars 2 forks source link

Miscellaneous checks from the DAQ doctor #29

Open gladky opened 7 years ago

gladky commented 7 years ago

There are following checks I discovered in DAQDottoressa code that are not in DAQExpert:

To do/verify

To do later:

To be skipped:

andreh12 commented 7 years ago

AlignmentChecker

quoting from page 26 of the DAQ Doctor documentation (https://edms.cern.ch/document/1333881/1):

Checks if all FEDs got the same number of events, if the last seen BX number is the same across all FEDs, if all EVMs are flushed correctly

'all EVMs' refers to the fact that we had eight (independent) slices in Run I and each of them had its own EVM.

Looking at the code, it looks like this was originally run when TRG was in 'pausing' or 'stopping' state, it's essentially a check 'at the end of the run' (or when paused).

andreh12 commented 7 years ago

SplashAnalyzer

As far as I can tell was its main use to detect LHC splash events during a few days of commissioning where a single beam was sent onto a (closed) collimator (a few hundred meters away from CMS) which then produces a shower of horizontally going particles crossing the CMS detector.

It looks like the main purpose of this class was to produce a sound (to alert the shift crew) when a splash event was detected. I'm not sure it was permanently activated or just during periods of splash events.

andreh12 commented 7 years ago

CrashDetector

From the documentation of the DAQ Doctor:

The CrashDetector helps to find crashed applications or crashed computers. In addition it watches out for disk Controller (called “SAS controller”) faults which turned out to be a frequent problem on the computers deployed in the cluster.

I think we definitively want similar functionality also in the DAQExpert (it was useful to automatically generate a new configuration when e.g. a crashed RU was detected). I have opened a dedicated issue here: #33