Project

General

Profile

Feature #13273

Support #13174: Some issues have been found with the RootOutput automatic file closing changes

Allow maxSubRuns and maxRuns for output-file handling

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

Status:
Closed
Priority:
Normal
Assignee:
Category:
I/O
Target version:
Start date:
07/18/2016
Due date:
% Done:

100%

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

Description

In addition to the maxEvents parameter, maxSubRuns and maxRuns parameters should also be added for the RootOutput module.

History

#1 Updated by Kyle Knoepfel over 3 years ago

  • Description updated (diff)

#2 Updated by Kyle Knoepfel over 3 years ago

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

The implementation of this feature was more difficult than originally envisaged. In addition to supporting maxEvents, maxSubRuns, and maxRuns per file, I also implemented a maxInputFiles parameter to keep the configuration uniform. Doing so required some subtle adjustments of the state-machine transition actions. Fortunately, the end result of the implementation is more intuitive than the previous one.

When typing art --print-description RootOutput, the following is now printed:

<config>: {

  module_type: RootOutput

  fileName: <string>
  .
  .
  .
  fileProperties: {

    maxEvents: 4294967295  # default

    maxSubRuns: 4294967295  # default

    maxRuns: 4294967295  # default

    maxInputFiles: 4294967295  # default

    # Maximum size of file (in KiB)

    maxSize: 2130706432  # default

    # Maximum age of output file (in seconds)

    maxAge: 4294967295  # default

    # The 'granularity' parameter specifies the level at which
    # an output file may be closed, and thereby the granularity
    # of the file.  The following values are possible:
    #
    #     Value        Meaning
    #    =======================================================
    #    "Event"       Allow file switch at next Event
    #    "SubRun"      Allow file switch at next SubRun
    #    "Run"         Allow file switch at next Run
    #    "InputFile"   Allow file switch at next InputFile
    #
    # For example, if a granularity of "SubRun" is specified, but the
    # output-module has reached the maximum events written to disk (as
    # specified by the 'maxEvents' parameter), the output module will NOT
    # switch to a new file until a new SubRun has been reached (or
    # there are no more Events/SubRuns/Runs to process).

    granularity: "Event"  # default
  }
}

Implemented with commit art:630a1913.

#3 Updated by Kyle Knoepfel over 3 years ago

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

#4 Updated by Kyle Knoepfel over 3 years ago

  • Tracker changed from Support to Feature


Also available in: Atom PDF