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
Fixes for vertex fits in the muon system #40479
Conversation
…ween two predicted states
…ween two predicted states
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40479/33653
|
A new Pull Request was created by @steggema (Jan Steggemann) for master. It involves the following packages:
@cmsbuild, @mandrenguyen, @clacaputo can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
type tracking |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2876aa/29911/summary.html Comparison SummaryThere are some workflows for which there are errors in the baseline: Summary:
|
assign tracking-pog |
@@ -226,6 +242,9 @@ class SequentialVertexFitter : public VertexFitter<N> { | |||
float theMaxShift; | |||
int theMaxStep; | |||
|
|||
float trackerBoundsRadius{112.}; |
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.
if you don't plan to make it configurable (as per PR description), at least preserve the original comment about having to take it from elsewhere.
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.
addressed at 170b193
+1
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40479/33805
|
Pull request #40479 was updated. @mandrenguyen, @clacaputo can you please check and sign again. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2876aa/30075/summary.html Comparison SummarySummary:
|
+reconstruction |
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, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Problem addressed: In EXO long-lived analyses, it was observed that using CMSSW vertex fitting code to reconstruct the decay vertex of resonances decaying beyond around 300 cm had much worse efficiency than for lower values, and the covariance matrix entries remained at their default values.
This was identified as coming from an issue in the fitting code when the sign of the magnetic field switches sign between two extrapolated track states. A report given in the context of the related Muon POG studies can be found here: https://indico.cern.ch/event/1220371/#6-dsa-vertex-inefficiency-stud
Another report will be given at a tracking POG meeting: https://indico.cern.ch/event/1232392/
The PR also includes a minimal change to the SequentialVertexFitter such that user code can update the boundaries in which the fit is considered valid. Up to now, users were updating these hard-coded values manually. We leave more involved updates (like taking the default values from a database or making it configurable at the EDProducer level) to future studies.
Changes to output: No changes to outputs are expected since this PR only affects the special use case of searches for long-lived particles using the CMSSW vertex fitting code to reconstruct secondary vertices outside of the inner tracker.
Other PRs: There is no interference with other PRs that we are aware of.
PR validation:
The proposed fixes lead to a large increase of efficiency for vertex fits beyond around 300 cm, and also to reasonable values of the covariance matrix entries, as reported in the slides above.
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
Not a backport.
@annamasce @jalimena @aescalante