-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Improve messages due VertexException
in SequentialPrimaryVertexFitterAdapter
and clean-up of BeamSpotOnlineProducer
#46893
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46893/42938 |
A new Pull Request was created by @mmusich for master. It involves the following packages:
@atpathak, @cmsbuild, @consuegs, @jfernan2, @mandrenguyen, @perrotta can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
reco::BeamSpot::Point apoint(spotDB->x(), spotDB->y(), spotDB->z()); | ||
double sigmaZ = (theSetSigmaZ > 0) ? theSetSigmaZ : spotDB.sigmaZ(); | ||
result = reco::BeamSpot(apoint, sigmaZ, spotDB.dxdz(), spotDB.dydz(), spotDB.beamWidthX(), matrix); | ||
result.setBeamWidthY(spotDB.beamWidthY()); |
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.
Not related to this PR (if not because of the part of the original code which is touched by it), but why not also setBeamWidthX
?
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.
but why not also
setBeamWidthX
the x-width is already set in the constructor at L162:
result = reco::BeamSpot(apoint, sigmaZ, spotDB.dxdz(), spotDB.dydz(), spotDB.beamWidthX(), matrix);
as per method signature:
cmssw/DataFormats/BeamSpot/interface/BeamSpot.h
Lines 39 to 45 in e9b58be
BeamSpot(const Point& point, | |
double sigmaZ, | |
double dxdz, | |
double dydz, | |
double BeamWidthX, | |
const CovarianceMatrix& error, | |
BeamType type = Unknown) { |
as both widths are constructed with the same value (in the hypothesis of round-optics)
cmssw/DataFormats/BeamSpot/interface/BeamSpot.h
Lines 50 to 51 in e9b58be
BeamWidthX_ = BeamWidthX; | |
BeamWidthY_ = BeamWidthX; |
setting explicitly the y component is necessary if the two differ (and in principle they will differ in 2025, if the flat optics is used).
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.
setting explicitly the y component is necessary if the two differ (and in principle they will differ in 2025, if the flat optics is used).
Ah, ok: that was indeed my worry. Thank you for confirming that the two directions can be set independently,
please test |
+1 Size: This PR adds an extra 12KB to repository Comparison SummarySummary:
|
+1 |
+alca |
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. @sextonkennedy, @rappoccio, @antoniovilela, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This is a follow-up to #45555 (comment).
SequentialPrimaryVertexFitterAdapter::fit
exceptions of theVertexExcpetion
type according to the suggestions at HLT crash in run 383631 - 'VertexException' and HcalDigisProducerGPU:hltHcalDigisGPU error #45555 (comment)BeamSpotOnlineProducer
in order to be more modular (and hopefully more easily debuggable).PR validation:
cmssw
compiles. Run an HLT job in normal conditions and didn't observe anomalies.Inducing the type of
VertexException
that is being caught now, I get the following type of log messages: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:
N/A