-
Notifications
You must be signed in to change notification settings - Fork 4.6k
backport of bugfix in vertex selection for the L2TauTagNNProducer #37372
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
backport of bugfix in vertex selection for the L2TauTagNNProducer #37372
Conversation
|
A new Pull Request was created by @valeriadamante (Valeria D'Amante) for CMSSW_12_3_X. It involves the following packages:
@cmsbuild, @missirol, @Martin-Grunewald can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
|
please test |
|
backport of #37291 @valeriadamante , please add "L2TauTagNNProducer" to the title of this PR. |
|
type bugfix |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-384b30/23443/summary.html Comparison SummarySummary:
|
|
+hlt
@valeriadamante , please don't forget the following
|
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_3_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_4_X is complete. 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) |
|
+1 |
PR description:
Doing tests on GPU, some issues in L2NNTag produced outputs have been reported: running twice the L2NNTag producer, it gave different results on the same events/taus. The problem has been addressed to the filling of the CNN inputs : PatatrackPtSumWithVertex and PatatrackSizeWithVertex.
The reason is the following: to fill the aforementioned variables while looping on tracks, a match between the vertex associated to the track (*) is required by associating the observable idv (which is the vertex index related to the patatrack) to be the same of the sortInd (**) which is the vertex index sorted by the vertex observable ptv2 .
If you want to give a look to the vertex related observables, they are described here.
This match is not correct: indeed, the idv has to be compared with the vertex index.
(*) all tracks with vertex index -1 are not considered, since this means that they are not associated to any vertex
(**) the sortInd is of a subset of all vertices, since they are required to pass some quality cuts described in the function SelectGoodVertices. Also in this function there is a similar matching requirement and also in that case it has been changed.
In this PR, this bug is fixed.
PR validation:
This bug was spotted because while looping multiple times on GPU, results were not consistent among each other.
With the aforementioned change, some preliminar tests on GPU and CPU have been carried on, selecting specific bugged events and from those preliminar tests there are no more differences.
With CPUs there were no difference both before and after the bugfix. So integrating this PR CPU results should be kept unchanged (in terms of efficiencies and rates).
if this PR is a backport please specify the original PR and why you need to backport that PR:
This is the backport of the PR cmssw-37291