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
Remove CurrentProcessingContext from HLTrigger #576
Remove CurrentProcessingContext from HLTrigger #576
Conversation
Remove all uses of CurrentProcessingContext from HLTrigger packages. This is replaced by using the new ModuleCallingContext. There should be no change in behavior. The only interface change in the HLTrigger code is that the Event is an added argument to some functions. These functions are only used in a few places and all uses are fixed. Also in the Framework, the PlaceInPathContext class is added and used. Removed the unused filling of TriggerResults for end paths. Some other minor Framework cleanup and unit tests.
@Dr15Jones @Martin-Grunewald @perrotta can you please sign? |
I wanted to wait for the results of the run the tests before signing. |
The following categories have been signed by gruenew (a.k.a. @Martin-Grunewald on GitHub): HLT @cms-git-hlt, @cms-git-fastsim |
The following categories have been signed by chrjones (a.k.a. @Dr15Jones on GitHub): Core @cms-git-visualization, @cms-git-core, @cms-git-geometry |
Hi, I took these changes on top of CMSSW_7_0_X_2013-08-21-0200, I ran the unit tests and RelVals, all tests passed. You can see the logs here: |
…mHLT Remove CurrentProcessingContext from HLTrigger
…7_4_12_samples3 fix QCD Mu5 samples in mAOD v2
…py80X_MDG add Triggers for entire 2016
Update GPU code following cms-sw#32146.
Remove all uses of CurrentProcessingContext from HLTrigger
packages. This is replaced by using the new ModuleCallingContext.
There should be no change in behavior. The only interface change
in the HLTrigger code is that the Event is an added argument
to some functions. These functions are only used in a few
places and all uses are fixed. Also in the Framework, the
PlaceInPathContext class is added and used. Removed the unused
filling of TriggerResults for end paths. Some other minor
Framework cleanup and unit tests.