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

Fix BeamSpotAnalyzer::fillDescriptions #37085

Merged
merged 3 commits into from
Mar 1, 2022

Conversation

mmusich
Copy link
Contributor

@mmusich mmusich commented Feb 28, 2022

PR description:

As reported by @francescobrivio, PR #35236 introduced a wrong type for the parameter BSAnalyzerParameters (which should be a PSet and non a VPSet).
This is fixed in this PR, together with completing the rest of descriptions coming from the BeamFitter and PVFitter classes.
I profit of this PR to introduce a unit test to check the functionality of the analyzer.

PR validation:

Relies on the unit tests provided in this PR

if this PR is a backport please specify the original PR and why you need to backport that PR:

N/A

@mmusich
Copy link
Contributor Author

mmusich commented Feb 28, 2022

type bug-fix

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-37085/28570

  • This PR adds an extra 16KB to repository

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @mmusich (Marco Musich) for master.

It involves the following packages:

  • RecoVertex/BeamSpotProducer (reconstruction, alca)

@malbouis, @yuanchao, @clacaputo, @cmsbuild, @slava77, @jpata, @tvami, @francescobrivio can you please review it and eventually sign? Thanks.
@GiacomoSguazzoni, @JanFSchulte, @rovere, @VinInn, @tocheng, @mmusich, @mtosi, @dgulhan, @francescobrivio this is something you requested to watch as well.
@perrotta, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@francescobrivio
Copy link
Contributor

@cmsbuild please test

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2418d1/22710/summary.html
COMMIT: 83ae0ba
CMSSW: CMSSW_12_3_X_2022-02-27-2300/slc7_amd64_gcc10
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/37085/22710/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 6 differences found in the comparisons
  • DQMHistoTests: Total files compared: 49
  • DQMHistoTests: Total histograms compared: 4001207
  • DQMHistoTests: Total failures: 14
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 4001171
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 48 files compared)
  • Checked 204 log files, 45 edm output root files, 49 DQM output files
  • TriggerResults: no differences found

@tvami
Copy link
Contributor

tvami commented Feb 28, 2022

Sorry, I'm not sure what we expect to see in the unit test
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2418d1/22710/unitTests/src/RecoVertex/BeamSpotProducer/test/testBeamSpotAnalyzer/testing.log

 Total number of events processed: 0
-------------------------------------
%MSG-w BeamFitter: 
No event read! No Fitting!
%MSG
[BeamSpotAnalyzer] beamfit fails !!!

is this expected?

@mmusich
Copy link
Contributor Author

mmusich commented Feb 28, 2022

is this expected?

of course it is....

tester.testRunWithNoLuminosityBlocks();

@tvami
Copy link
Contributor

tvami commented Feb 28, 2022

+alca

  • unit test results as expected
  • Jenkins diffs show MsgLogger only
  • code change in line w description

@jpata
Copy link
Contributor

jpata commented Mar 1, 2022

+reconstruction

  • technical

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 1, 2022

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)

@perrotta
Copy link
Contributor

perrotta commented Mar 1, 2022

+1

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.

6 participants