Project

General

Profile

Feature #9794

FileDumper to print the chronologically ordered list of process names

Added by Christopher Green over 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
I/O
Target version:
Start date:
08/05/2015
Due date:
% Done:

100%

Estimated time:
2.00 h
Spent time:
Scope:
Internal
Experiment:
NOvA
SSI Package:
art
Duration:

History

#1 Updated by Kyle Knoepfel over 4 years ago

  • Status changed from New to Assigned
  • Assignee set to Kyle Knoepfel

#2 Updated by Kyle Knoepfel over 4 years ago

  • Status changed from Assigned to Feedback

After some investigation, it is not immediately apparent to me how this can be done.

The process information can be obtained via the ProcessHistoryRegistry, or through objects associated with a given process BranchDescription, Group, etc. The ProcessHistoryRegistry is not a candidate since its keys are hashes; the ordering, therefore, does not correspond to the chronology.

The only solution I can think of at the moment is to retrieve the BranchIDLists object from the root file, and obtain the process name through one item on each BranchIDList (singular), which are ordered chronologically within the BranchIDLists meta-container. Unfortunately, the BranchIDLists meta-container corresponds to products that were produced only in the Event. So that doesn't solve the problem either.

Any thoughts?

#3 Updated by Kyle Knoepfel over 4 years ago

Actually not even the BranchIDLists container will work -- it consists of lists of BranchIDs, and you cannot retrieve a BranchDescription (from which you can get the process name) from a BranchID, thanks to the checksum algorithm.

#4 Updated by Kyle Knoepfel about 4 years ago

  • Status changed from Feedback to Assigned

#5 Updated by Kyle Knoepfel over 3 years ago

Upon investigation, implementing this feature is not as difficult as it first seemed. The order of process names corresponds to the ordering of the longest item in the ProcessHistoryRegistry.

#6 Updated by Kyle Knoepfel over 3 years ago

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

Implemented with art:ba1cda3. My interpretation of this issue is that all products printed should be printed in chronological order according to process name.

A --process-history program option was also added to file_info_dumper to provide the list of process names corresponding to processes that produced the file in question.

#7 Updated by Kyle Knoepfel over 3 years ago

  • Status changed from Resolved to Closed
  • Target version set to 2.03.00


Also available in: Atom PDF