Feature #8593: Improve flexibility of output file handling
Design and specify maxEvents for output streams
The Schedule::limitOutput function is currently ifdef'd into a no-op. I have now removed the ifdef'd code. The attached file is the contents of this function, before removal of the ifdef'd code.
Confirmed, but must wait for the great I/O revolution.
- Due date set to 09/30/2013
- Target version set to 1.09.00
- Estimated time set to 160.00 h
- Scope set to Internal
- Experiment - added
This will need significant analysis due to various assumptions made in the framework about the "push" nature of output file closure.
Online applications might prefer a streaming file format, which would satisfy several of the customers for this feature (possibly Darkside online, NOvA DDT).
- Tracker changed from Feature to Milestone
- Due date changed from 09/30/2013 to 01/01/2014
- Target version changed from 1.09.00 to 2.01.00
- Target version changed from 2.01.00 to 1.18.00
- Blocks deleted (Milestone #3708: Implement condition-based output file rollover)
- Estimated time changed from 160.00 h to 0.00 h
This issue will require the, "push" nature of the state machine input / output system to be changed. An estimate for the implementation of this particular issue given that change is pending.
- Target version changed from 1.18.00 to 834
- Target version changed from 834 to 3.12.06
- Target version changed from 3.12.06 to 521
- Assignee set to Kyle Knoepfel
- Target version changed from 521 to 2.01.00
- % Done changed from 0 to 100
Implemented with commit art:09d893e as a specific instance of condition-based output-file rollover.
RootOutput now has a parameter called
- Status changed from Accepted to Resolved
- Status changed from Resolved to Closed
Also available in: Atom