search

elaird / supy

analyze events stored in TTrees in parallel
8 stars 7 forks source link

optional predicate step in reweights #176

Closed betchart closed 11 years ago

betchart commented 11 years ago

Due to a new requirement of my analysis, I need to plot my signals after two incompatible cuts, so I have added a predicate in this step for convenience. The theme of predicates could be expanded, for example, I can imagine a more general "steps.other.predicate" step, taking a step to execute along with a "temporary cut" step as a predicate. We originally designed supy purposefully with linear cut-flow, due to conceptual and coding simplicity, and those reasons may still apply. Feel free to merge this branch or expand on the theme.

gerbaudo commented 11 years ago

Hi Burt,

merging is fine with me. As a side note, I have tried to put in place a minimal example for 'reweights' here https://github.com/davidegerbaudo/supy-minimal-example/pull/4 However I couldn't get it to work (if you see anything that is obviously wrong please let me know). If you guys think think it would be useful to have this example within the supy tests we can move it here. Thanks,

Davide