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
use deterministic seed for time smearing producers #21354
Conversation
The code-checks are being triggered in jenkins. |
sigh, a conflict arose in the past ~hour. Rebasing... |
Actually, will wait for the next IB to rebase. |
assign upgrade |
+code-checks |
New categories assigned: upgrade @kpedro88 you have been requested to review this Pull request/Issue and eventually sign? Thanks |
A new Pull Request was created by @kpedro88 (Kevin Pedro) for master. It involves the following packages: IOMC/RandomEngine @smuzaffar, @civanch, @Dr15Jones, @mdhildreth, @cmsbuild, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Your PR is unmergeable. Please have a look and possibly rebase it. |
d68a901
to
b2640fe
Compare
The code-checks are being triggered in jenkins. |
+code-checks |
Pull request #21354 was updated. @smuzaffar, @civanch, @Dr15Jones, @mdhildreth, @cmsbuild, @kpedro88 can you please check and sign again. |
please test |
The tests are being triggered in jenkins. |
The tests are being triggered in jenkins. |
+1 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 There are some workflows for which there are errors in the baseline: Comparison Summary:
|
+1 |
+1 |
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 (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
1 similar comment
+1 |
Resolves #20621
The TrackTimeValueMapProducer now uses STL
<random>
with the PRNG reseeded for every event. The seed is based on the event run/lumi/event numbers and the chi2 value of the first track. (The last quantity is added to ensure different seeding when the producer is called with different collections. Currently two versions of it exist in the Phase2 reco sequences, one for general tracks and another for GSF electron tracks.)I checked the
t()
value of the 4D vertices after running 20034.2 with step3 on 1 thread vs 4 threads. In the default release, I see a change; with this PR, there is no change.Should this be backported to 93X? It runs in RECO, while with 93X we only plan to do re-miniAOD.
attn: @lgray, @bendavid