Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Have a check to avoid not calling clearEvent #2

Closed
rsmith54 opened this issue Dec 21, 2015 · 1 comment · Fixed by #13
Closed

Have a check to avoid not calling clearEvent #2

rsmith54 opened this issue Dec 21, 2015 · 1 comment · Fixed by #13
Assignees
@rsmith54

Comments

@rsmith54
Copy link
Owner

We should have some way that we check that clearEvent has been called for each calculator. This is mostly a reminder to myself, but I'm also not sure the best way to do this.
@rsmith54 rsmith54 self-assigned this Dec 21, 2015
@rsmith54
Copy link
Owner Author

This probably requires doing some check on the n objects in the frames, but maybe there is a better way to do this. It would be best if this can be automatically called for any type of RJigsawCalculator (to avoid reimplementation).

@rsmith54 rsmith54 mentioned this issue Dec 22, 2015
Merged
lawrenceleejr pushed a commit to lawrenceleejr/FactoryTools that referenced this issue Sep 28, 2016
Merge branch 'dev-Larry' into 'master'
e44ef73 
Dev larry

- 2015 vs 2015 lepton triggers rsmith54#2 
- e/mu/btag SFs rsmith54#1 
- trigger matching rsmith54#3

See merge request !4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rsmith54 rsmith54

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Dev russell rsmith54/FactoryTools
1 participant
@rsmith54