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
Patatrack: introduce pt-clamping in vertex sorting, add #tracks in track SOA #37281
Conversation
@cmsbuild, please test |
enable gpu |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-37281/28908
|
A new Pull Request was created by @VinInn (Vincenzo Innocente) for master. It involves the following packages:
@jpata, @makortel, @fwyzard, @clacaputo, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
what is waiting for? |
@smuzaffar tests seem stuck here. Can you verify? Thank you. |
@mmusich , jenkins was very bus today that is why there was not enough resources to run tests, I see that https://cmssdt.cern.ch/jenkins/job/compare-root-files-short-matrix/49033/console is still running for last 2 hours. Hopefully it will finish soon. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d7e9ee/23240/summary.html GPU Comparison SummarySummary:
Comparison Summary@slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
|
assign tracking |
assign tracking-pog assuming that was the intention of #37281 (comment) |
+1
|
Thanks Marco, I wanted to ask tracking to take a look (and make sure it was discussed in the POG) as I didn't really have any comments. I will sign now. |
+reconstruction |
auto ntracks = apc->get().m; | ||
if (0 == first) | ||
tracks.setNTracks(ntracks); | ||
for (int idx = first, nt = ntracks; idx < nt; idx += gridDim.x * blockDim.x) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just checking -- why is nt
needed ? wouldn't idx < ntracks
equivalent ?
+heterogeneous |
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. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
@VinInn @fwyzard @silviodonato , should this PR be backported to |
I definitely support the request of a backport, if it is possible. It would be very good if we can start the data taking including this PR. |
+1 |
Okay, @silviodonato. Unless anyone objects to this (or goes ahead with the backport), I will open the backport PR to 12_3_X in the next days as per TSG's request. (cc: @Martin-Grunewald) |
This PR introduces some long standing improvements in Patatrack that can be useful to POG and PAG using directly SOA products.
This is supposed to mitigate the effect of spurious tracks with large pt due to miss-measurement, resolution or inaccurate calibration/alignment.
The effect has been tested in Z->tau-tau events that are supposed to be among those who most suffer from signal-vertex miss-identification.
The effect is small if not negligible. see: http://innocent.home.cern.ch/innocent/RelVal/ztt_clamp/plots_selectedPixelVertices/pvtagging.pdf
where we compare clamping at 20, 75 (the default) and 1000 GeV.
This is not unexpected given the resolution of HP quadruplets, those used to build vertices, that reaches ~30% at ~70 GeV.
It may be different with initial calibrations or large inefficiency.
Results for ttbar can be found in
http://innocent.home.cern.ch/innocent/RelVal/gpuMTVclamp/plots_selectedPixelVertices/pvtagging.pdf
This should make the use of the SOA more user-friendly.
Default has changed, so expect small regressions.