-
Notifications
You must be signed in to change notification settings - Fork 140
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
Bugfix: set trigger value in jet constituent QA #1030
Bugfix: set trigger value in jet constituent QA #1030
Conversation
For repository maintainers, please start the CI check manually (feedback)This is an automatic message to assist manually starting CI check for this pull request, commit c1ba9a12d38db5a8a0083651cb2a14af7a9c30d6. sPHENIX software maintainers: please make your input here and start the Build: Note:
Automatically generated by sPHENIX Jenkins continuous integration |
Isn't TriggerRunInfoReco nodes already in the DSTs at this stage of the prod? it is in the calo fitting macro. If it is being striped out accidentally we should fix that. |
Whoops! Good catch! I forgot about that! I'll double check that it isn't being stripped out. We do need the bugfix in the constituents, though, so I'll reduce the scope of this PR to just that... |
For repository maintainers, please start the CI check manually (feedback)This is an automatic message to assist manually starting CI check for this pull request, commit c5bb2f2f3eafbf3c128cc109e8e2ba8b46d2a638. sPHENIX software maintainers: please make your input here and start the Build: Note:
Automatically generated by sPHENIX Jenkins continuous integration |
This is now descoped! |
This PR fixes a minor bug: the trigger flag value wasn't being provided in the call to
ConstituentsInJets::setTrgStoSelect()
, so this module was always selecting the MBDNS >= 1 trigger.