-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement filter module based on run/subrun/event #264
Comments
I realize that the 'simple format' here may not be what one would want, but presumable this art filter could already fit the bill, if you print out the matching run:subrun:event number list in a fcl format? Can you comment if that would fit the need? And if so, then do we need something to auto-make an event list? |
Hmm, it's fcl-based rather than taking a text file, but we can presumably produce the right format easily enough. NOvA CAFAna has the FileList tools to produce these lists (you give it a Cut, and a list of Vars, and it makes a text file or TTree with the run/subrun/event and Var values for events that passed the cut). They didn't get ported to SBN yet. I think for the raw question of spitting out events that pass event-level cuts that would be straightforward. I was holding off because people may well want lists of slices based on slice cuts, or even tracks based on track cuts and that would be much cleaner in the RecordSource world that is currently on a branch. |
(see SBNSoftware/sbnana#85 for that RecordSource branch) |
Closing until we specify a more specific and active need. |
We should implement something very like NOvA's RunEventFilter module. This takes a text file (in the simple format output by CAFAna's EventList code) and only passes art events that are in this list. That enables you to make a skim file for further study, e.g. hand scanning
/cvmfs/nova-development.opensciencegrid.org/novasoft/releases/development/Filter/RunEventFilter_module.cc
The text was updated successfully, but these errors were encountered: