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.

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

Better consumes interface for TrackerHitAssociator #8999

Conversation

wmtan
Copy link
Contributor

@wmtan wmtan commented May 7, 2015

This PR replaces the previous consumes interface for TrackerHitAssociator (implemented in #8647) with a much better interface. Prior to #8647, each TrackerHitAssociator instance was created and destroyed on a per event per module basis, which guaranteed that each auxiliary structure (e.g. map of PSimHits) were deleted as soon as it was no longer needed. PR #8647 unfortunately extended the lifetime of each TrackerHitAssociator instance to be the entire job, so that each map needed to be manually deleted. This is an error prone interface.
This new interface restores the lifetime of each TrackerHitAssociator instance to be per module per event, which automatically guarantees that the memory problems will not occur. The consumes interface is implemented by using a helper class TrackerHitAssociator::Config. Instances of this helper class do last the entire job, but this helper class does not contain any per event data, so there are no memory issues.
Although this PR needs to be tested, it should be expedited, as use of the consumes interface for other TrackerHitAssociator users (there are many) depends on this PR, and development will be hindered if this is not merged in a timely manner. I would strongly suggest that L2 signatures be bypassed if not signed in a timely manner, unless, of course, an L2 has issues with this PR.

@cmsbuild
Copy link
Contributor

cmsbuild commented May 7, 2015

A new Pull Request was created by @wmtan for CMSSW_7_5_X.

Better consumes interface for TrackerHitAssociator

It involves the following packages:

SimTracker/TrackerHitAssociation
Validation/GlobalRecHits
Validation/RecoTrack
Validation/TrackerRecHits

@civanch, @nclopezo, @danduggan, @mdhildreth, @cmsbuild, @deguio can you please review it and eventually sign? Thanks.
@makortel, @GiacomoSguazzoni, @rovere, @VinInn, @appeltel, @wmtford, @cerati, @threus, @dgulhan, @venturia this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.
@nclopezo you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@Dr15Jones
Copy link
Contributor

Please test

@cmsbuild
Copy link
Contributor

cmsbuild commented May 8, 2015

The tests are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented May 8, 2015

@civanch
Copy link
Contributor

civanch commented May 11, 2015

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_5_X IBs unless changes (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @nclopezo, @smuzaffar

@davidlange6
Copy link
Contributor

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants