modules: The module-by-module timing data written into the...
In marcpaterno/artsupport: Analysis of art Program Performance Data
Description
The module-by-module timing data written into the 'TimeModule' table, which contains one record
per module for each event. The recorded art process used 3 modules on just 1 path. There is also
a record for the TriggerResults 'module'.
Usage
1
Format
A tibble with 960 observatios of 8 variables:
- Run
the run number
- SubRun
the subrun number
- Event
the event number
- Path
the path on which the module ran; note that one module can appear on multiple paths
- ModuleLabel
the label of the module
- ModuleType
the C++ class of the module
- Time
module executon time in seconds
- sample
sample id, and integer unique for each event
marcpaterno/artsupport documentation built on May 6, 2020, 1:46 a.m.
R Package Documentation
Browse R Packages
We want your feedback!
Note that we can't provide technical support on individual packages. You should contact the package authors for that.
Description
The module-by-module timing data written into the 'TimeModule' table, which contains one record per module for each event. The recorded art process used 3 modules on just 1 path. There is also a record for the TriggerResults 'module'.
Usage
1 |
Format
A tibble with 960 observatios of 8 variables:
- Run
the run number
- SubRun
the subrun number
- Event
the event number
- Path
the path on which the module ran; note that one module can appear on multiple paths
- ModuleLabel
the label of the module
- ModuleType
the C++ class of the module
- Time
module executon time in seconds
- sample
sample id, and integer unique for each event
R Package Documentation
Browse R Packages
We want your feedback!
Note that we can't provide technical support on individual packages. You should contact the package authors for that.
Embedding an R snippet on your website
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.