You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm about to start modifying the eventloop in my fork of NanoAODTools so that for a given input event, I will write out 100 (or any other arbitrary, fixed number) output events, where for each output event we smear the two leading jet Pt. The physics motivation is to over-sample and smear a statistically limited QCD control region.
I can see how to achieve this by modifying the eventloop function, but I'm curious if there's anything I need to be aware of in terms of additional book-keeping pieces, e.g. is there any place in the code that assumes each input event has a unique event number, etc.
Finally, does functionality like this seem more generally useful and worth a PR to contribute back once we're satisfied that it's working?
The text was updated successfully, but these errors were encountered:
I've implemented this functionality in this commit on our forked version of NanoAODTools: b9791fb.
I'd be happy to open a PR to push this back to the official master branch, but otherwise I will just leave this here as a reference for potential future users.
I'm about to start modifying the eventloop in my fork of NanoAODTools so that for a given input event, I will write out 100 (or any other arbitrary, fixed number) output events, where for each output event we smear the two leading jet Pt. The physics motivation is to over-sample and smear a statistically limited QCD control region.
I can see how to achieve this by modifying the
eventloop
function, but I'm curious if there's anything I need to be aware of in terms of additional book-keeping pieces, e.g. is there any place in the code that assumes each input event has a unique event number, etc.Finally, does functionality like this seem more generally useful and worth a PR to contribute back once we're satisfied that it's working?
The text was updated successfully, but these errors were encountered: