Project

General

Profile

Feature #11894

Feature #11415: Implement Run and SubRun fragments

Provide contributing events/subruns for SubRun and Run products

Added by Kyle Knoepfel almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Metadata
Target version:
Start date:
03/04/2016
Due date:
% Done:

100%

Estimated time:
80.00 h
Spent time:
Scope:
Internal
Experiment:
-
SSI Package:
art
Duration:

Description

A necessary feature for properly supporting SubRun and Run products is the ability to known which subruns and events contributed to the products that were created. More specifically, for a given module, the list of events and subruns processed need to be recorded for products produced in the endSubRun and endRun overrides. Doing so requires:

  1. Creating an in-memory representation of the subruns and events that contribute to a given (Sub)Run product,
  2. Inserting the data from the in-memory representation into a set of SQLite tables in the output file,
  3. Providing new data member in art::Wrapper, which stores the index to the appropriate database entry,
  4. Adjusting product aggregation to combine contributing subruns and events when appropriate, based on looking up the information from the SQLite database,
  5. Providing a mechanism for users to retrieve and use the information when querying a product.

History

#1 Updated by Kyle Knoepfel almost 4 years ago

  • Status changed from New to Assigned

#2 Updated by Kyle Knoepfel over 3 years ago

  • Description updated (diff)

#3 Updated by Kyle Knoepfel over 3 years ago

  • % Done changed from 0 to 80

#4 Updated by Kyle Knoepfel over 3 years ago

  • Estimated time set to 80.00 h

#5 Updated by Kyle Knoepfel over 3 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 80 to 100

Providing contributing events/subruns for SubRun and Run products has been implemented by adding the requisite tables to the RootFileDB of the art/ROOT file. The C++-represented object is the art::RangeSet, which has a run number data member, and vector of EventRange objects. The EventRange represents a dense half-open range of events, associated with a specific subrun.

Implemented across many commits. The commit for merging develop into the feature branch is art:97485ee.

#6 Updated by Kyle Knoepfel over 3 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF