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

fixed digi search behavior to check for end of list #12037

Merged
merged 3 commits into from Oct 24, 2015

Conversation

hardenbr
Copy link
Contributor

No description provided.

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @hardenbr for CMSSW_7_4_X.

fixed digi search behavior to check for end of list

It involves the following packages:

HLTrigger/special

@Martin-Grunewald, @perrotta, @cmsbuild, @fwyzard can you please review it and eventually sign? Thanks.
@Martin-Grunewald 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.
@Degano you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@Martin-Grunewald
Copy link
Contributor

Just to make sure: this is a genuine correction - or does the occurence of "end" reveal a mistake elsewhere and this is just a fix?

@@ -140,14 +140,17 @@ HLTRechitsToDigis::produce(edm::Event& iEvent, edm::EventSetup const& setup) {
// loop over the collection of rechits and match to digis
EcalRecHitCollection::const_iterator ituneEB;
for (ituneEB = recHitsHandle->begin(); ituneEB != recHitsHandle->end(); ituneEB++) {
EcalRecHit hit = (*ituneEB);
outputEBDigiCollection->push_back( (*digisEB->find(hit.id())).id(), (*digisEB->find(hit.id())).begin() );
EcalRecHit hit = (*ituneEB);
Copy link
Contributor

Choose a reason for hiding this comment

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

could you change this to

EcalRecHit const & hit = * ituneEB;

to avoid the copy ?
(though hopefully the compiler optimises it out itself)

@cmsbuild
Copy link
Contributor

Pull request #12037 was updated. @Martin-Grunewald, @perrotta, @cmsbuild, @fwyzard can you please check and sign again.

@Martin-Grunewald
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/9121/console

@cmsbuild
Copy link
Contributor

Pull request #12037 was updated. @Martin-Grunewald, @perrotta, @fwyzard can you please check and sign again.

@cmsbuild
Copy link
Contributor

The jenkins tests job failed, please try again.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/9121/console

@hardenbr
Copy link
Contributor Author

@Martin-Grunewald This is being looked into. At some point a rechit that does not have a corresponding DIGI is being created and passed to the RechitsToDigi module. This happens in a very small fraction of events which is why it wasn't found until it was put online.

@Martin-Grunewald
Copy link
Contributor

+1

@Martin-Grunewald
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/9144/console

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs after it passes the integration tests and once validation in the development release cycle CMSSW_7_6_X is complete. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_7_6_X is complete. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_7_6_X is complete. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar

@hardenbr
Copy link
Contributor Author

@Martin-Grunewald Does a PR need to be done for 80X?

@Martin-Grunewald
Copy link
Contributor

Currently we have auto-port forward from 76 to 80...

@davidlt
Copy link
Contributor

davidlt commented Oct 24, 2015

Add ref to issue: #11982

davidlange6 added a commit that referenced this pull request Oct 24, 2015
fixed digi search behavior to check for end of list
@davidlange6 davidlange6 merged commit ee9f783 into cms-sw:CMSSW_7_4_X Oct 24, 2015
EcalRecHit const & hit = (*ituneEB);
EcalDigiCollection::const_iterator digiLookUp = digisEB->find(hit.id());
// protect against a digi not existing
if( digiLookUp == digisEB->end()) continue;
Copy link
Contributor

Choose a reason for hiding this comment

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

Reviewing this PR now.... this check makes no sense, there are no recHits without a digi associated. The recHit should not be skipped as it is now.

@shervin86
Copy link
Contributor

@argiro @ferriff @emanueledimarco @ghezzi please have a look

@emanueledimarco
Copy link
Contributor

I think that either the origin of the ghost hits is found (better) or the hits have to be skipped (patchy, but OK). Because this is what we will do anyway offline with them.

@ferriff
Copy link
Contributor

ferriff commented Nov 12, 2015

RecHits with no digis might be there for recovered dead channels. Can this be checked comparing a list of DetId for which there is a recHit but no digi to the channel status in the DB?
However, from my fainted memories recoveries are switched off at HLT, and, if confirmed for Run2, I guess it would be better to fix a likely bug someplace else than integrate this fix...

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

9 participants