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

set serial option for TH1::Fit in BeamSpotProducer #22227

Merged
merged 1 commit into from
Feb 19, 2018

Conversation

dan131riley
Copy link

Interactions between TMinuit thread local variables and implicit multi-threading in the evaluation of the fit are suspected to be a cause of crashes in AlcaBeamMonitor, details are in #21769 (long). This PR sets the SERIAL option to the calls to TH1::Fit, which turns off the use of IMT in the fit evaluation.

…uit thread local variables and IMT parallelization
@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @dan131riley (Dan Riley) for master.

It involves the following packages:

RecoVertex/BeamSpotProducer

@perrotta, @ghellwig, @arunhep, @cerminar, @cmsbuild, @franzoni, @slava77, @lpernie can you please review it and eventually sign? Thanks.
@ghellwig, @makortel, @felicepantaleo, @GiacomoSguazzoni, @tocheng, @VinInn, @ebrondol, @rovere, @mmusich, @dgulhan this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

@fabiocos
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 15, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/26083/console Started: 2018/02/15 09:12

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-22227/26083/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 27
  • DQMHistoTests: Total histograms compared: 2465360
  • DQMHistoTests: Total failures: 3
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2465188
  • DQMHistoTests: Total skipped: 169
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 1.1499999999 KiB( 22 files compared)
  • Checked 111 log files, 9 edm output root files, 27 DQM output files

@perrotta
Copy link
Contributor

Just for the record, this is what the jenkins tests report as difference in DQM in wf 136.788 (RunSinglePh2017B), sub-directory AlcaBeamMonitor:

image

I can't appreciate any difference in the figure, but since this is exactly the place which this PR wants to fix, this maybe can provide some kind of info

@dan131riley
Copy link
Author

The code paths for the chi2 and likelihood evaluations are slightly different for the kSerial vs. kMultithread execution policies even single-threaded, but it's just sums and integrals, dunno to what extent there are random numbers involved. BinToBin is .996, with a fail threshold of 0.999999999999.

I'm not really sure what to make of it, but I'd like to see this go in anyway to see if it fixes the crashes.

@perrotta
Copy link
Contributor

+1

  • "SERIAL" option added to the calls to TH1::Fit in RecoVertex/BeamSpotProducer BSFitter and PVFitter
  • No effect on reco quantities, as expected
  • Let see if it fixes the crashes observed in AlcaBeamMonitor...

@fabiocos
Copy link
Contributor

@lpernie @arunhep @ghellwig could you please check? This is another fix to try to solve the long standing issue with the AlcaBeamMonitor...

@lpernie
Copy link
Contributor

lpernie commented Feb 19, 2018

+1

@cmsbuild
Copy link
Contributor

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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

@fabiocos
Copy link
Contributor

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

5 participants