FAQ:What is the difference between a run number and an execution cycle?
| Offline Documentation: [Offline Category] [FAQ] [Howto] [Reference] [Manual] |
| Offline Documentation |
| This article is part of the Offline Documentation |
| Other pages... |
|
Offline Category |
| See also... |
Execution Number
A HeaderObject has an execution number that is incremented by 1 each time a new instance is made. Specifically it counts the time that the algorithm that produces the HeaderObject has its execute() method called.
Note, it should not be thought of as an "event" number. This is an ill-defined concept and one whose common interpretations do not always match with the definition of execution number.
Run Number
A run number identifies a particular setup of the simulation or DAQ.
DAQ Runs
A DAQ run will produce multiple sub run files, split up for file-size convenience.
DAQ run numbers are monotonically increasing and unique to a site (is this right?)
Simulation Runs
A simulation run number also indicates a particular configuration. It is also used to generate random number seeds.
There are Runs and then there are Runs
The word "run" is also overloaded to describe a period of data taking where there is some overall shared purpose or organization. Examples:
- Mini dry-run
- AD1 dry-run
- MDC09b simulation run
See also
| Offline Software Documentation: [Offline Categories] [FAQ] [Offline Faq Category] |