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

correct missing commas in dflt initializations for ghostTrack in IPProducer #27000

Merged
merged 1 commit into from May 31, 2019

Conversation

slava77
Copy link
Contributor

@slava77 slava77 commented May 29, 2019

This is a follow up to #26913 (comment)

@ferencek

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@slava77 slava77 changed the title correct missing comma in dflt initializations for ghostTrack in IPProducer correct missing commas in dflt initializations for ghostTrack in IPProducer May 29, 2019
@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27000/10056

  • This PR adds an extra 16KB to repository

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @slava77 (Slava Krutelyov) for master.

It involves the following packages:

RecoBTag/ImpactParameter

@perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks.
@smoortga, @acaudron, @HeinerTholen, @JyothsnaKomaragiri, @mverzett, @ferencek, @pvmulder 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

@slava77
Copy link
Contributor Author

slava77 commented May 29, 2019

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented May 29, 2019

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/591/console Started: 2019/05/29 19:49

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

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

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 7 differences found in the comparisons
  • DQMHistoTests: Total files compared: 33
  • DQMHistoTests: Total histograms compared: 3210728
  • DQMHistoTests: Total failures: 1
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3210393
  • DQMHistoTests: Total skipped: 334
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 32 files compared)
  • Checked 137 log files, 14 edm output root files, 33 DQM output files

@slava77
Copy link
Contributor Author

slava77 commented May 30, 2019

as expected, in a few cases the ghostTrack tag infos moved from -2 to 0.
E.g. in Run2018A EGamma wf 136.85

all_OldVSNew_RunEGamma2018Awf136p85c_recoCandidateedmPtrsrecoJetTagInforecoIPTagInfos_pfImpactParameterTagInfos__reRECO_obj_m_data_distanceToGhostTrack_value

@slava77
Copy link
Contributor Author

slava77 commented May 30, 2019

+1

for #27000 de52341

  • differences observed in the jenkins tests are as expected: in some rare cases where the defaults are not reset the values are now at 0 instead of -2

@cmsbuild
Copy link
Contributor

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

@slava77 this looks a genuine bug fix that I assume we would like to port to 10_6_X, am I correct?

@fabiocos
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit bd1e6f6 into cms-sw:master May 31, 2019
@slava77
Copy link
Contributor Author

slava77 commented May 31, 2019

@slava77 this looks a genuine bug fix that I assume we would like to port to 10_6_X, am I correct?

I do not really see a reason for a backport.
From #26913 (comment)

The ghost track feature is not really in active use which probably explains why this went unnoticed all this time.

@slava77 slava77 mentioned this pull request May 31, 2019
4 tasks
@fabiocos
Copy link
Contributor

@slava77 ok, in this case I agree, although strictly speaking it remains a bug

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

3 participants