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

BugFix for L3MuonCandidateProducerFromMuons #22774

Conversation

folguera
Copy link
Contributor

Matching efficiency was degrading for very high-pt muons, this brings back the possibility of using the innerTrack when available and using the outerTrack otherwise. This recovers the missing efficiency.

…degrading for very high-pt muons, this brings back the possibility of using the innerTrack when available and using the outerTrack otherwise
@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @folguera (Santiago Folgueras) for master.

It involves the following packages:

RecoMuon/L3MuonProducer

@perrotta, @cmsbuild, @silviodonato, @slava77, @Martin-Grunewald, @fwyzard can you please review it and eventually sign? Thanks.
@bellan, @abbiendi, @jhgoh, @echapon, @calderona, @HuguesBrun, @drkovalskyi, @battibass, @trocino, @bachtis, @rociovilar this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

@Martin-Grunewald
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 28, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/27162/console Started: 2018/03/28 14:43

@silviodonato
Copy link
Contributor

Even if we will definitely move to 10_1_X, I think it is good if you propagate this fix to 10_0_X too.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@perrotta
Copy link
Contributor

This implies that for high pT muons the parameters of the muonBestTrack() are "worst" than the ones obtained from the innerTrack(), at least for this purpose. Out of curiosity: do you understand why?

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-22774/27162/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 29
  • DQMHistoTests: Total histograms compared: 2501822
  • DQMHistoTests: Total failures: 1
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2501645
  • DQMHistoTests: Total skipped: 176
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 1.17000000008 KiB( 22 files compared)
  • Checked 119 log files, 9 edm output root files, 29 DQM output files

@Martin-Grunewald
Copy link
Contributor

+1

@perrotta
Copy link
Contributor

perrotta commented Apr 1, 2018

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 1, 2018

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

@fabiocos
Copy link
Contributor

fabiocos commented Apr 1, 2018

+1

@cmsbuild cmsbuild merged commit 0dbf8d0 into cms-sw:master Apr 1, 2018
@Martin-Grunewald
Copy link
Contributor

@folguera
This PR is integrated in 102X so we need another PR backporting to 101X.

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

7 participants