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
Conversation
The code-checks are being triggered in jenkins. |
@cmsbuild please test |
+code-checks |
The tests are being triggered in jenkins. |
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. cms-bot commands are listed here |
@cmsbuild please abort (realized I forgot a few things) |
Jenkins tests are aborted. |
083f9d6
to
4d4aff5
Compare
The code-checks are being triggered in jenkins. |
+code-checks |
@cmsbuild please test |
The tests are being triggered in jenkins. |
-1 Tested at: 7a501f1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see the results of the tests here: I found follow errors while testing this PR Failed tests: UnitTests
I found errors in the following unit tests: ---> test runtestTqafTopEventProducers had ERRORS The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1
|
+1 |
[in absence of analysis signature] this PR is now fully signed. Please check it. |
yes, its on the list..
… On Nov 15, 2017, at 4:16 PM, Slava Krutelyov ***@***.***> wrote:
@davidlange6
[in absence of analysis signature] this PR is now fully signed. Please check it.
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
merge |
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. |
but only in the timing workflow, right? |
yes, only in the timing workflows and only in multi-threaded ones. |
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).