Skip to content
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

Merged
merged 2 commits into from
Dec 9, 2024

Conversation

mmusich
Copy link
Contributor

@mmusich mmusich commented Dec 7, 2024

PR description:

This is a follow-up to #45555 (comment).

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:

%MSG-e UnusableBeamSpot:  PrimaryVertexProducer:hltVerticesPF  07-Dec-2024 11:13:50 CET Run: 386614 Event: 48610345
Beamspot with invalid errors [            0           0           0
             0           0           0
             0           0           0 ]
%MSG
----- Begin Fatal Exception 07-Dec-2024 11:13:50 CET-----------------------
An exception of category 'VertexException' occurred while
   [0] Processing  Event run: 386614 lumi: 55 event: 48610345 stream: 0
   [1] Running path 'MC_AK8PFJetPNet_v4'
   [2] Calling method for module PrimaryVertexProducer/'hltVerticesPF'
   [3] While processing SequentialPrimaryVertexFitterAdapter::fit() with BeamSpot parameters: 
-----------------------------------------------------
              Beam Spot Data

 Beam type    = -1
       X0     = 0 +/- 0 [cm]
       Y0     = 0 +/- 0 [cm]
       Z0     = 0 +/- 0 [cm]
 Sigma Z0     = 0 +/- 0 [cm]
 dxdz         = 0 +/- 0 [radians]
 dydz         = 0 +/- 0 [radians]
 Beam width X = 0 +/- 0 [cm]
 Beam width Y = 0 +/- 0 [cm]
 EmittanceX   = 0 [cm]
 EmittanceY   = 0 [cm]
 beta-star    = 0 [cm]
-----------------------------------------------------


Exception Message:
BasicSingleVertexState::could not invert error matrix 

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

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 7, 2024

cms-bot internal usage

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 7, 2024

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 7, 2024

A new Pull Request was created by @mmusich for master.

It involves the following packages:

  • RecoVertex/BeamSpotProducer (reconstruction, alca)
  • RecoVertex/PrimaryVertexProducer (reconstruction)

@atpathak, @cmsbuild, @consuegs, @jfernan2, @mandrenguyen, @perrotta can you please review it and eventually sign? Thanks.
@GiacomoSguazzoni, @VinInn, @VourMa, @dgulhan, @fabiocos, @francescobrivio, @martinamalberti, @missirol, @mmusich, @mtosi, @rovere, @rsreds, @tocheng, @yuanchao this is something you requested to watch as well.
@antoniovilela, @mandrenguyen, @rappoccio, @sextonkennedy you are the release manager for this.

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());
Copy link
Contributor

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?

Copy link
Contributor Author

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:

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)

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).

Copy link
Contributor

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,

@perrotta
Copy link
Contributor

perrotta commented Dec 8, 2024

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 8, 2024

+1

Size: This PR adds an extra 12KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c3bfb0/43315/summary.html
COMMIT: a390d6b
CMSSW: CMSSW_15_0_X_2024-12-08-0000/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/46893/43315/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • You potentially added 1 lines to the logs
  • Reco comparison results: 284 differences found in the comparisons
  • DQMHistoTests: Total files compared: 47
  • DQMHistoTests: Total histograms compared: 3623082
  • DQMHistoTests: Total failures: 2443
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3620619
  • DQMHistoTests: Total skipped: 20
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 46 files compared)
  • Checked 206 log files, 177 edm output root files, 47 DQM output files
  • TriggerResults: found differences in 1 / 45 workflows

@jfernan2
Copy link
Contributor

jfernan2 commented Dec 9, 2024

+1

@perrotta
Copy link
Contributor

perrotta commented Dec 9, 2024

+alca

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 9, 2024

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)

@mandrenguyen
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit b1d0e43 into cms-sw:master Dec 9, 2024
11 checks passed
@mmusich mmusich deleted the mm_improve_HLT_beamspot_45555 branch December 9, 2024 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants