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

Add possibility to cut on timing to IVF #20640

Merged
merged 6 commits into from Nov 16, 2017

Conversation

lgray
Copy link
Contributor

@lgray lgray commented Sep 24, 2017

This PR adds the possibility to cut on the time significance between a vertex with timing and a time stamped track.

Timing is checked for dynamically in both the vertex and the transient track. If not present in both the timing cut is skipped.

This will only affect timing workflows where the 1D vertex reconstruction is overridden (Phase2_timing_layer / D19).

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@lgray
Copy link
Contributor Author

lgray commented Sep 24, 2017

@cmsbuild please test

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-20640/936

@cmsbuild
Copy link
Contributor

The tests are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

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

It involves the following packages:

RecoVertex/AdaptiveVertexFinder
TrackingTools/TransientTrack

@perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks.
@gpetruc, @pvmulder, @HuguesBrun, @bellan, @makortel, @felicepantaleo, @acaudron, @abbiendi, @GiacomoSguazzoni, @mverzett, @rovere, @VinInn, @calderona, @imarches, @JyothsnaKomaragiri, @jhgoh, @ferencek, @battibass, @ebrondol, @trocino, @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

@lgray
Copy link
Contributor Author

lgray commented Sep 24, 2017

@cmsbuild please abort

(realized I forgot a few things)

@cmsbuild
Copy link
Contributor

Jenkins tests are aborted.

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-20640/940

@cmsbuild
Copy link
Contributor

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

@lgray
Copy link
Contributor Author

lgray commented Sep 24, 2017

@cmsbuild please test

@cmsbuild
Copy link
Contributor

The tests are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

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

@cmsbuild
Copy link
Contributor

-1

Tested at: 7a501f1

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
c738e9e
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20640/24406/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20640/24406/git-merge-result

You can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20640/24406/summary.html

I found follow errors while testing this PR

Failed tests: UnitTests

  • Unit Tests:

I found errors in the following unit tests:

---> test runtestTqafTopEventProducers had ERRORS
---> test runtestTqafTopEventSelection had ERRORS
---> test runtestTqafExamples had ERRORS

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
c738e9e
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20640/24406/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20640/24406/git-merge-result

@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-20640/24406/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 27
  • DQMHistoTests: Total histograms compared: 2832699
  • DQMHistoTests: Total failures: 99
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2832422
  • DQMHistoTests: Total skipped: 178
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.94000000009 KiB( 23 files compared)
  • Checked 111 log files, 8 edm output root files, 27 DQM output files

@slava77
Copy link
Contributor

slava77 commented Nov 15, 2017

+1

for #20640 7a501f1

@kpedro88
Copy link
Contributor

+1

@slava77
Copy link
Contributor

slava77 commented Nov 15, 2017

@davidlange6

[in absence of analysis signature] this PR is now fully signed. Please check it.
Thank you.

@davidlange6
Copy link
Contributor

davidlange6 commented Nov 15, 2017 via email

@davidlange6
Copy link
Contributor

merge

@cmsbuild cmsbuild merged commit 2c37c6b into cms-sw:master Nov 16, 2017
@slava77
Copy link
Contributor

slava77 commented Nov 16, 2017

A notable feature of this PR is that b-tagging is now not reproducible due to unreproducible randomness in the phase-2 workflows with timing.
#20621 is still open.

@kpedro88
Copy link
Contributor

but only in the timing workflow, right?

@slava77
Copy link
Contributor

slava77 commented Nov 16, 2017

but only in the timing workflow, right?

yes, only in the timing workflows and only in multi-threaded ones.

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