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

PFEGammaProducer to global producer #29375

Merged
merged 1 commit into from Apr 6, 2020
Merged

PFEGammaProducer to global producer #29375

merged 1 commit into from Apr 6, 2020

Conversation

guitargeek
Copy link
Contributor

PR description:

The PF egamma code is still a big chunk of hard-to-understand code; this PR does not really do much about that but it goes in the direction by making the PFEGammaProducer a global module and removing an unused configuration parameter that would not have an effect even if enabled (useVerticesForNeutral, the dummy vertex was overwritten by the real reconstructed vertex anyways). Furthermore, the producer got modernized with put tokens and the includes in the PFProducer packages were cleaned by not including forward header files in .cc sources anymore (which required a few little changes in the DataFormats, as there were some header files which didn't include their own forward header which should optimally be the case).

PR validation:

CMSSW compiles and matrix tests pass.

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

No backport intended.

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 1, 2020

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 1, 2020

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29375/14480

  • This PR adds an extra 104KB to repository

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 1, 2020

A new Pull Request was created by @guitargeek (Jonas Rembser) for master.

It involves the following packages:

DataFormats/EgammaReco
DataFormats/ParticleFlowReco
DataFormats/VertexReco
RecoParticleFlow/PFProducer

@perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks.
@mmarionncern, @Sam-Harper, @makortel, @jainshilpi, @afiqaize, @rovere, @lgray, @sobhatta, @hatakeyamak, @VinInn, @varuns23, @seemasharmafnal, @cbernet this is something you requested to watch as well.
@silviodonato, @dpiparo you are the release manager for this.

cms-bot commands are listed here

@slava77
Copy link
Contributor

slava77 commented Apr 1, 2020

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 1, 2020

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/5494/console Started: 2020/04/01 23:44

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 2, 2020

-1

Tested at: 7216d10

CMSSW: CMSSW_11_1_X_2020-04-01-1100
SCRAM_ARCH: slc7_amd64_gcc820

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:

You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9fe532/5494/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9fe532/5494/git-merge-result

You can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9fe532/5494/summary.html

I found follow errors while testing this PR

Failed tests: UnitTests

  • Unit Tests:

I found errors in the following unit tests:

---> test testTauEmbeddingProducers had ERRORS

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:

You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9fe532/5494/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9fe532/5494/git-merge-result

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 2, 2020

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 2, 2020

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

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 20 differences found in the comparisons
  • DQMHistoTests: Total files compared: 34
  • DQMHistoTests: Total histograms compared: 2692102
  • DQMHistoTests: Total failures: 53
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2691730
  • DQMHistoTests: Total skipped: 319
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 33 files compared)
  • Checked 147 log files, 16 edm output root files, 34 DQM output files

@perrotta
Copy link
Contributor

perrotta commented Apr 2, 2020

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 2, 2020

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/5502/console Started: 2020/04/02 16:17

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 3, 2020

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/5522/console Started: 2020/04/04 03:48

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 4, 2020

+1
Tested at: a8fe68a
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9fe532/5522/summary.html
CMSSW: CMSSW_11_1_X_2020-04-03-2300
SCRAM_ARCH: slc7_amd64_gcc820

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 4, 2020

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 4, 2020

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

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 49 differences found in the comparisons
  • DQMHistoTests: Total files compared: 34
  • DQMHistoTests: Total histograms compared: 2692110
  • DQMHistoTests: Total failures: 45
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2691746
  • DQMHistoTests: Total skipped: 319
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 33 files compared)
  • Checked 147 log files, 16 edm output root files, 34 DQM output files

@perrotta
Copy link
Contributor

perrotta commented Apr 5, 2020

@silviodonato since a few days it is hard to compare the reco outputs of the automatic tests because there are a lot of messages like

%MSG
[2020-04-04 02:11:46.060760 +0200][Error  ][PostMaster        ] [eoscms.cern.ch:1094 #0] Forcing error on disconnect: [ERROR] Operation interrupted.
%MSG-e ExcessiveTime:  SiPixelClusterProducer:siPixelClustersPreSplitting  04-Apr-2020 02:29:51 CEST Run: 326479 Event: 1394020
ExcessiveTime: Module used 1837.07 seconds of time which exceeds the error threshold configured in the Timing Service of 600 seconds.
%MSG

in the logs. And, according to some random inspection I made, all those ExcessiveTime error's are in the baseline logs, and not in the PR's logs.

Is there an explanation for this? Can we expect a fix is coming, so that we can more easily compare the outputs?

@perrotta
Copy link
Contributor

perrotta commented Apr 6, 2020

Please @guitargeek clean up the PR description in the part dealing with the forward header files, as these changes were reverted in this PR

@guitargeek guitargeek changed the title PFEGammaProducer to global producer and other changes PFEGammaProducer to global producer Apr 6, 2020
@perrotta
Copy link
Contributor

perrotta commented Apr 6, 2020

+1

  • Technical changes, leading to make the PFEGammaProducer a global producer, some cleaning, and removal of the useVerticesForNeutral parameter and its usage in the code (as it was actually a deadly and useless assignment, as pointed out in the PR description)
  • Jenkins tests pass and show no differences, as it should, besides the spurious ones described
    above

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 6, 2020

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

@silviodonato
Copy link
Contributor

+1

@makortel
Copy link
Contributor

makortel commented Apr 6, 2020

@silviodonato since a few days it is hard to compare the reco outputs of the automatic tests because there are a lot of messages like

%MSG
[2020-04-04 02:11:46.060760 +0200][Error  ][PostMaster        ] [eoscms.cern.ch:1094 #0] Forcing error on disconnect: [ERROR] Operation interrupted.
%MSG-e ExcessiveTime:  SiPixelClusterProducer:siPixelClustersPreSplitting  04-Apr-2020 02:29:51 CEST Run: 326479 Event: 1394020
ExcessiveTime: Module used 1837.07 seconds of time which exceeds the error threshold configured in the Timing Service of 600 seconds.
%MSG

in the logs. And, according to some random inspection I made, all those ExcessiveTime error's are in the baseline logs, and not in the PR's logs.

Is there an explanation for this? Can we expect a fix is coming, so that we can more easily compare the outputs?

@perrotta If this is a persistent problem, could you open an issue about it?

@slava77
Copy link
Contributor

slava77 commented Apr 6, 2020

@perrotta If this is a persistent problem, could you open an issue about it?

I've seen it in another case about a week ago (but I can't find that example to be more precise)

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.

None yet

7 participants