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

Moved fastSim reconstruction to use era #20884

Merged
merged 3 commits into from Nov 9, 2017

Conversation

Dr15Jones
Copy link
Contributor

When trying to convert the reconstruction configurations from Sequences to Tasks, we found that the fastsim was greatly complicating the transition. One reason was the fastsim was directly rewriting Configuration.StandardSequences.Reconstruction_cff from within FastSimulation.Configuration.Reconstruction_AftMix_cff which was leading to very 'brittle' configuration code. For example, if someone accidently loaded Reconstruction_cff into the Process before Reconstruction_AftMix_cff the configuration would no longer work. Switching to fully using the fastSim era avoids many problems and makes fastsim behave like the other configuration modification workflows.

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@Dr15Jones
Copy link
Contributor Author

I used release validation workflow 25402.0 as the test bed. I used the following simple configuration for testing

from TTbar_13TeV_TuneCUETP8M1_cfi_GEN_SIM_RECOBEFMIX_DIGI_L1_DIGI2RAW_L1Reco_RECO_EI_VALIDATION_DQM_PU import process
process.prune()
print process.dumpPython()

With that configuration, I found the my change returns a configuration with exactly the same module configuration as before. In addition, I checked that the Paths reconstruction_step and reconstruction_befmix_step contain the exact same list of modules.

@Dr15Jones
Copy link
Contributor Author

@gartung here is the fastsim change

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-20884/1361

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @Dr15Jones (Chris Jones) for master.

It involves the following packages:

Configuration/StandardSequences
FastSimulation/Configuration
FastSimulation/Tracking
RecoEcal/EgammaClusterProducers
RecoEgamma/Configuration
RecoEgamma/EgammaPhotonProducers
RecoLocalCalo/Configuration
RecoLocalCalo/EcalRecProducers
RecoMET/Configuration
RecoMuon/Configuration
RecoMuon/GlobalMuonProducer
RecoMuon/GlobalTrackingTools
RecoMuon/MuonIdentification
RecoMuon/TrackingTools
RecoParticleFlow/PFTracking
RecoTracker/Configuration
RecoTracker/FinalTrackSelectors
RecoTracker/IterativeTracking
RecoTracker/MeasurementDet
TrackingTools/GsfTracking
TrackingTools/TrackRefitter

@perrotta, @civanch, @lveldere, @ssekmen, @mdhildreth, @cmsbuild, @franzoni, @slava77, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @TaiSakuma, @gouskos, @felicepantaleo, @jainshilpi, @abbiendi, @argiro, @Martin-Grunewald, @ahinzmann, @lgray, @varuns23, @seemasharmafnal, @mmarionncern, @battibass, @makortel, @jhgoh, @dgulhan, @jdolen, @HuguesBrun, @trocino, @rociovilar, @Sam-Harper, @GiacomoSguazzoni, @rovere, @VinInn, @jdamgov, @bellan, @nhanvtran, @gkasieczka, @schoef, @mschrode, @ebrondol, @amagitte, @echapon, @calderona, @cbernet, @gpetruc, @matt-komm, @mariadalfonso, @bachtis this is something you requested to watch as well.
@davidlange6, @slava77 you are the release manager for this.

cms-bot commands are listed here

@Dr15Jones
Copy link
Contributor Author

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 10, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/23655/console Started: 2017/10/10 22:11

@cmsbuild
Copy link
Contributor

-1

Tested at: 50c957c

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
dd401df
a2aeaf0
d9807b8
da408a3
e802724
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20884/23655/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20884/23655/git-merge-result

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

I found follow errors while testing this PR

Failed tests: RelVals

  • RelVals:

When I ran the RelVals I found an error in the following worklfows:
1000.0 step3

runTheMatrix-results/1000.0_RunMinBias2011A+RunMinBias2011A+TIER0+SKIMD+HARVESTDfst2+ALCASPLIT/step3_RunMinBias2011A+RunMinBias2011A+TIER0+SKIMD+HARVESTDfst2+ALCASPLIT.log

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
dd401df
a2aeaf0
d9807b8
da408a3
e802724
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20884/23655/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20884/23655/git-merge-result

@cmsbuild
Copy link
Contributor

Comparison not run due to runTheMatrix errors (RelVals and Igprof tests were also skipped)

@Dr15Jones
Copy link
Contributor Author

The workflow 1000.0 is failing in the IBs with the exact same configuration error.

@slava77
Copy link
Contributor

slava77 commented Oct 11, 2017

Changes in this PR should be discussed in some joint meeting with fastsim category managers.
This PR is effectively fusing two categories at the package assignment level and may have to require a joint signature or some other non-obvious solution.

@ssekmen
Copy link
Contributor

ssekmen commented Oct 11, 2017

We have indeed planned to discuss the PR in the next simulation meeting when all simulation conveners are available.

@slava77
Copy link
Contributor

slava77 commented Oct 25, 2017 via email

@makortel
Copy link
Contributor

Perhaps it's time to think of refactoring the Iter_cff files?

Do you mean something like for each iterations splitting the seeding, pattern recognition+final fit, and selection to their own cff files imported in the main iteration cff file that also defines the iteration Task(/Sequence)?

@slava77
Copy link
Contributor

slava77 commented Oct 25, 2017 via email

@Dr15Jones
Copy link
Contributor Author

I agree with Slava

Design of eras works best if the modifiers are applied in the same file where the original modules are defined.

and I will go further. Not putting the modifier in the original module can lead to unforseen side-effects. E.g. clones that do not match or sequences that break.

@smuzaffar smuzaffar modified the milestones: CMSSW_9_4_X, CMSSW_10_0_X Oct 26, 2017
@cmsbuild cmsbuild modified the milestones: CMSSW_10_0_X, CMSSW_9_4_X Oct 26, 2017
@perrotta
Copy link
Contributor

I have just verified that this PR interferes with #20666: @ssekmen please let us know which are the plans for the integration of the two PRs, priorities, etc.

@ssekmen
Copy link
Contributor

ssekmen commented Oct 30, 2017

@Perrota, discussing with the FastSim tracking experts. We will come with a more concrete plan at our presentation at the tracking meeting on Nov 6.

@perrotta
Copy link
Contributor

perrotta commented Oct 30, 2017 via email

@perrotta
Copy link
Contributor

+1

  • Reco part of this PR was reviewed and approved
  • Effect of this PR will likely be that the maintenance of the fastsim modules goes towards DPG/POGs instead of being kept separated in the fastsim package
  • Several modules/sequences are marked with comments like "not commissioned and not relevant in FastSim": during the fastsim review it can be worth going through all those components and simply remove whatever not needed, thus simplifying and improving the future maintenance

@davidlange6
Copy link
Contributor

hi @civanch - this is the PR discussed in the ORP yesterday

@ssekmen
Copy link
Contributor

ssekmen commented Nov 8, 2017

+1

@davidlange6
Copy link
Contributor

merge

@cmsbuild cmsbuild merged commit 7a54396 into cms-sw:master Nov 9, 2017
@Dr15Jones Dr15Jones deleted the moveFastSimRecoToEras branch November 10, 2017 15:31
@kpedro88
Copy link
Contributor

@Dr15Jones I noticed some failures in fastsim premixing workflows in the IB tests (https://cms-sw.github.io/relvalLogDetail.html#slc7_aarch64_gcc700;CMSSW_10_0_X_2017-11-10-1100):

----- Begin Fatal Exception 10-Nov-2017 14:52:24 CET-----------------------
An exception of category 'Configuration' occurred while
   [0] Constructing the EventProcessor
Exception Message:
EDAlias does not match data
There are no products of type 'recoTracks'
with module label 'mix' and instance name 'generalTracks'.
----- End Fatal Exception -------------------------------------------------

Might be caused by this PR, can you take a look?

@kpedro88
Copy link
Contributor

ah, I see you were faster than me with #21263.

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

9 participants