Analysis support requires ability to store objects in file in branch other than Run, SubRun, or Event
I am currently working on performing an analysis on NOvA and would like to use art's provenance tracking feature when producing and storing the final output of the analysis.
The problem is that to do a neutrino oscillation analysis, we do a fit over the energy spectra of all selected events from all runs taken. That is, we cannot store the analysis result in any of the event, sub run, or run areas of the output art file because the analysis must be done at the endJob portion of the state. To store the result, we would need to do it at a level that is outside of the run process.
I think it would be good to organize a meeting with the art stakeholders to discuss the use case of art for performing an analysis and come up with requirements. Doing so would also allow users to move away from making TTrees/ntuples outside of art for doing analysis and make use of art's provenance tracking.
I have a path forward for now, so this is not a critical issue, but it should be given attention soon.
#1 Updated by Christopher Backhouse over 5 years ago
We also wanted this for the attenuation calibration. In that respect it was filed as Issue 4324. The solution there with the database I guess is working for the drift, but it's inapplicable for the attenuation, where we're still hacking around the absence of this.
#2 Updated by Christopher Green over 5 years ago
- Category set to I/O
- Status changed from New to Feedback
- Assignee set to Christopher Green
- SSI Package art added
- SSI Package deleted (
We believe it is a reasonable way forward to send a message to the stakeholders list requesting that experiments put together their thoughts on this subject, for a meeting to discuss them at next week's stakeholders meeting (18th December). Does this work for you?