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

Require vertex to have time to use timing cuts in displaced track seeding #21659

Merged
merged 2 commits into from Apr 14, 2018

Conversation

lgray
Copy link
Contributor

@lgray lgray commented Dec 7, 2017

Since #20640 was merged, this is needed to bring master in line with #21193.

Add the requirement that the primary vertex has timing information to use the track time cuts.

@lgray
Copy link
Contributor Author

lgray commented Dec 7, 2017

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 7, 2017

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 7, 2017

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-21659/2498

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 7, 2017

The tests are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 7, 2017

A new Pull Request was created by @lgray (Lindsey Gray) for master.

It involves the following packages:

RecoVertex/AdaptiveVertexFinder

@perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks.
@imarches, @makortel, @felicepantaleo, @acaudron, @GiacomoSguazzoni, @rovere, @VinInn, @JyothsnaKomaragiri, @mverzett, @ferencek, @ebrondol, @pvmulder, @dgulhan this is something you requested to watch as well.
@davidlange6, @slava77 you are the release manager for this.

cms-bot commands are listed here

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 7, 2017

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 8, 2017

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

The workflows 1003.0, 1001.0, 1000.0, 140.53, 136.7611, 136.731, 4.22 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons

@slava77 comparisons for the following workflows were not done due to missing matrix map:

  • /build/cmsbld/jenkins-workarea/workspace/compare-root-files-short-matrix/results/JR-comparison/PR-21659/1325.7_TTbar_13_94XNanoAODINPUT+TTbar_13_94XNanoAODINPUT+NANOEDMMC2017

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 6588 differences found in the comparisons
  • DQMHistoTests: Total files compared: 27
  • DQMHistoTests: Total histograms compared: 2835085
  • DQMHistoTests: Total failures: 3710
  • DQMHistoTests: Total nulls: 2
  • DQMHistoTests: Total successes: 2831195
  • DQMHistoTests: Total skipped: 178
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 15.67 KiB( 23 files compared)
  • Checked 113 log files, 9 edm output root files, 27 DQM output files

@kpedro88
Copy link
Contributor

assign upgrade

@cmsbuild
Copy link
Contributor

New categories assigned: upgrade

@kpedro88 you have been requested to review this Pull request/Issue and eventually sign? Thanks

@slava77
Copy link
Contributor

slava77 commented Dec 12, 2017

@cmsbuild please test

running tests for PRs made against the HEAD is not very practical.
rerunning now to get comparisons cleaner.

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 9, 2018

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 9, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/27399/console Started: 2018/04/09 20:21

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 9, 2018

Pull request #21659 was updated. @perrotta, @cmsbuild, @kpedro88, @slava77 can you please check and sign again.

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 9, 2018

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 9, 2018

Comparison job queued.

@slava77
Copy link
Contributor

slava77 commented Apr 9, 2018

@lgray
please push the same updates to #21193
it is much easier to test in 93X

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 9, 2018

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

Comparison Summary:

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

@slava77
Copy link
Contributor

slava77 commented Apr 12, 2018

@lgray
please push the same updates to #21193
it is much easier to test in 93X

Please let me know if you can follow up on this.
Thank you.

@lgray
Copy link
Contributor Author

lgray commented Apr 12, 2018 via email

@slava77
Copy link
Contributor

slava77 commented Apr 13, 2018

+1

for #21659 bc93565

  • updates to get rid of the residual dependence of the secondary vertexing on track times in the (now default) setup with the reference PV having no time measurement.
  • jenkins tests pass and comparisons with the baseline show expected behavior.

The changes are only in 20434.0 as expected.
this plot is probably the most telling
all_oldvsnew_ttbar14tev2023d19wf20434p0c_recovertexcompositeptrcandidates_inclusivecandidatesecondaryvertices__reco_obj_t
given absence of time measurement in the default PV, the goal of this fix/PR was to make the secondary vertexing to ignore time measurement.

Additionally, the tests in #21193 now show no difference in the b-tagging variables (DQM plots)

@kpedro88
Copy link
Contributor

+1

@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

+1

@cmsbuild cmsbuild merged commit a330b37 into cms-sw:master Apr 14, 2018
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