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

remove unused DigiSimLinkProducer and related configuration #23644

Merged
merged 1 commit into from Jun 25, 2018

Conversation

mmusich
Copy link
Contributor

@mmusich mmusich commented Jun 22, 2018

Greetings,
this is a follow-up of issue #23634.
As suggested by @makortel, apparently DigiSimLinkProducer is not used anymore anywhere in the Strip digitization package. To avoid supporting unused code and duplicated configuration, we just propose to remove it.
Passes local testing via runTheMatrix.py -s.
cc: @boudoul @echabert @mjansova

@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 @mmusich (Marco Musich) for master.

It involves the following packages:

SimTracker/SiStripDigitizer

@cmsbuild, @civanch, @mdhildreth can you please review it and eventually sign? Thanks.
@echabert, @makortel, @GiacomoSguazzoni, @rovere, @VinInn, @prolay, @ebrondol, @threus, @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

@makortel
Copy link
Contributor

@cmsbuild, please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Jun 22, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/28824/console Started: 2018/06/22 16:25

@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-23644/28824/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 5373 differences found in the comparisons
  • DQMHistoTests: Total files compared: 31
  • DQMHistoTests: Total histograms compared: 2899538
  • DQMHistoTests: Total failures: 19262
  • DQMHistoTests: Total nulls: 8
  • DQMHistoTests: Total successes: 2880078
  • DQMHistoTests: Total skipped: 190
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: -13102.107 KiB( 30 files compared)
  • DQMHistoSizes: changed ( 1330.0,... ): -397.031 KiB HLT/SiStrip
  • DQMHistoSizes: changed ( 1330.0,... ): -397.031 KiB SiStrip/MechanicalView
  • DQMHistoSizes: changed ( 250202.181 ): -397.114 KiB SiStrip/MechanicalView
  • Checked 128 log files, 14 edm output root files, 31 DQM output files

@civanch
Copy link
Contributor

civanch commented Jun 23, 2018

please test

number of DQM failures (HI, 2018..) cannot be explained by this PR, for any case, re-trigger tests

@cmsbuild
Copy link
Contributor

cmsbuild commented Jun 23, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/28848/console Started: 2018/06/23 16:45

@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-23644/28848/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 31
  • DQMHistoTests: Total histograms compared: 2899480
  • DQMHistoTests: Total failures: 2
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2899288
  • DQMHistoTests: Total skipped: 190
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 30 files compared)
  • Checked 128 log files, 14 edm output root files, 31 DQM output files

@civanch
Copy link
Contributor

civanch commented Jun 24, 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

@cmsbuild cmsbuild merged commit 5528b18 into cms-sw:master Jun 25, 2018
@VinInn
Copy link
Contributor

VinInn commented Aug 1, 2018

@cmsbuild cmsbuild modified the milestones: CMSSW_10_2_X, CMSSW_10_3_X Aug 1, 2018
@mmusich
Copy link
Contributor Author

mmusich commented Aug 1, 2018

Hi @VinInn,
about your specific question I am not sure, but regarding your query at https://hypernews.cern.ch/HyperNews/CMS/get/swDevelopment/3479.html it doens't depend on this PR.
I've run wf 110808.0 in the last 10.1.X IB (which doens't contain this PR) and there are no

edm::DetSetVector<StripDigiSimLink>    "simSiStripDigis"           ""                "HLT"

in step3:

[10808.0_SingleMuPt100+SingleMuPt100_pythia8_2018_GenSimFull+DigiFull_2018+RecoFull_2018+ALCAFull_2018+HARVESTFull_2018]$ edmDumpEventContent step3.root | grep DigiSim
MuonDigiCollection<DTLayerId,DTDigiSimLink> "simMuonDTDigis"            ""                "HLT"
edm::DetSetVector<RPCDigiSimLink> "simMuonRPCDigis"           "RPCDigiSimLink"   "HLT"
edm::DetSetVector<StripDigiSimLink> "simMuonGEMDigis"           "GEM"             "HLT"
edm::DetSetVector<StripDigiSimLink> "simMuonCSCDigis"           "MuonCSCStripDigiSimLinks"   "HLT"
edm::DetSetVector<StripDigiSimLink> "simMuonCSCDigis"           "MuonCSCWireDigiSimLinks"   "HLT" 

@VinInn
Copy link
Contributor

VinInn commented Aug 1, 2018 via email

@mmusich
Copy link
Contributor Author

mmusich commented Aug 1, 2018

Since they are there in step2 I suppose they are just removed from the list of keep of the PoolOutputModule for the RECO step?

@VinInn
Copy link
Contributor

VinInn commented Aug 1, 2018

apparently....

@VinInn
Copy link
Contributor

VinInn commented Aug 1, 2018

no simDigis in step3
edmDumpEventContent step3.root | grep simSiPixelDigis
most probably never been there (I was looking to a step2 file from relval, not reco)
sorry for the noise...
one needs to start from step2 or produce a special step3.

@slava77
Copy link
Contributor

slava77 commented Aug 1, 2018 via email

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

8 participants