Goodruns

From Mu2eWiki
Revision as of 18:29, 16 March 2025 by Rlc (talk | contribs) (Created page with "==Introduction== As data is recorded all sorts of issue may appear which might make data more or less appropriate to use in specific purposes. For example, if a run has excessive noise in the tracker, it might not be good for physics analysis, but would be fine for calorimeter cosmics calibration. This system has two parts. The first part allows the experiment to set bits for each run, defining if the data passed or failed certain criteria. These bits need to be define...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Introduction

As data is recorded all sorts of issue may appear which might make data more or less appropriate to use in specific purposes. For example, if a run has excessive noise in the tracker, it might not be good for physics analysis, but would be fine for calorimeter cosmics calibration.

This system has two parts. The first part allows the experiment to set bits for each run, defining if the data passed or failed certain criteria. These bits need to be defined and labeled, but it is simple to create new ones as needed. This page does not address what bits will be used, since that is topic for operations. These daily records can be converted into a list of runs which pass certain criteria for a certain purpose (analysis, calibration, studies). These good run lists are the second function of the system. The resulting good run list can then be used to filter or select good data. Arbitrary good run lists can be created and used.

Recording status with bits

Interactions with the database are by an exe called grlTool, which is available with Offline

The bit record consist of words, and bits assigned inside each word. The name of each word is categories:

category/subcategory/name

for example

DAQ/DQM/tracker
Ops/shift/tracker
Pass1/DQM/calo
Analysis/eplus/efficiencies

A word can be defined

grlTool define-word DAQ/DQM/tracker "auto entry from DQM end run"

and then for each word, bits can be defined and labeled.

grlTool define-bit DAQ/DQM/tracker noise "more than 5% noise hits"
grlTool define-bit DAQ/DQM/tracker badnoise "more than 10% noise hits"
grlTool define-bit DAQ/DQM/tracker running "the tracker was active and triggered no readout errors or trips"

Word and bit definitions are permanent, obsolete bits can be ignored. The database is recording an actual bit field to attach to the bit name for this word. As shown later, bits can have a positive sense or a negative sense, i.e. you want to require the bit on to be a good run, or reject the run if the bit is set. Once bits have been defined, they can be set:

grlTool set-word  103001 DAQ/DQM/tracker running noise 

This example sets the content of the given word. If there was a previous entry for this word, the old entry will be retired and this value will replace it. Since words are replaced, and not additive. There would only be one entry for a given word. The run field can be a single run, a run range, and may include subruns as boundaries. The syntax is the same as for the [conditions IoVs]

t

t

t

Good run lists

t

t

t