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

Fixing initialization of event setup point of PR 6030 #6085

Merged

Conversation

mmusich
Copy link
Contributor

@mmusich mmusich commented Oct 29, 2014

Small fix to save memory. Initializing event setup pointer once for all

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_7_3_X.

Fixing initialization of event setup point of PR 6030

It involves the following packages:

Alignment/OfflineValidation

@diguida, @cerminar, @cmsbuild, @nclopezo, @rcastello, @mmusich can you please review it and eventually sign? Thanks.
@ghellwig, @frmeier 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.
@nclopezo, @ktf you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@@ -382,7 +382,9 @@ TrackerOfflineValidation::~TrackerOfflineValidation()
void
TrackerOfflineValidation::checkBookHists(const edm::EventSetup& es)
{
lastSetup_ = &es;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The framework does not guarantee that we will always keep the same EventSetup object throughout the job. Please close this commit.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure to understand the comment. We just need the EventSetup pointer once in the endjob to invoke the TrackerTopology. Before this commit tlampen@078138b, lastSetup_ was simply a nullptr, which was causing seg faults.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can't use the EventSetup in the endJob, nor can you use any data held by the EventSetup. That is why it is not passed as a value to the various module's endJob. Please find another way to accomplish what you are trying to do.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the clarification. Does this imply we should revert also commit 078138b from @tlampen in PR #6030 (which, by the way has already been merged) and in all the backport PR #6070 #6072 and #6073?

@Dr15Jones
Copy link
Contributor

hold

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Reverting commits regarding unsafe treatment of EventSetup
@mmusich
Copy link
Contributor Author

mmusich commented Nov 4, 2014

As agreed with @diguida and @rcastello, while I'll try to figure out a better implementation. I reverted the unsafe commits. Please notice that these also reverts 078138b from @tlampen.

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 5, 2014

@diguida
Copy link
Contributor

diguida commented Nov 5, 2014

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 5, 2014

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_3_X IBs unless changes (tests are also fine). This pull request will be automatically merged.

cmsbuild added a commit that referenced this pull request Nov 5, 2014
Fixing initialization of event setup point of PR 6030
@cmsbuild cmsbuild merged commit 5159e3e into cms-sw:CMSSW_7_3_X Nov 5, 2014
@hroskes hroskes mentioned this pull request Sep 6, 2015
@mmusich mmusich deleted the fixTrackerOfflineValidationMemory branch April 20, 2018 14:27
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.

4 participants