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

era for HI pp reference run and relval wf #21122

Merged
merged 4 commits into from
Nov 7, 2017

Conversation

ttrk
Copy link
Contributor

@ttrk ttrk commented Nov 1, 2017

adds "Run2_2017_ppRef" era to run customized reco for HI pp reference run
adds a corresponding relval wf (149)
runs and stores photonIsolationHIProducer objects using the era

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 1, 2017

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 1, 2017

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-21122/1751

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 1, 2017

A new Pull Request was created by @ttrk (Kaya Tatar) for master.

It involves the following packages:

Configuration/DataProcessing
Configuration/Eras
Configuration/PyReleaseValidation
Configuration/StandardSequences
RecoEcal/Configuration
RecoEgamma/Configuration

@perrotta, @prebello, @kpedro88, @fabozzi, @cmsbuild, @franzoni, @slava77, @GurpreetSinghChahal, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @varuns23, @Sam-Harper, @argiro, @makortel, @felicepantaleo, @jainshilpi, @GiacomoSguazzoni, @rovere, @lgray, @Martin-Grunewald, @ebrondol, @VinInn, @dgulhan this is something you requested to watch as well.
@davidlange6, @slava77 you are the release manager for this.

cms-bot commands are listed here

self.eras=Run2_2017_ppRef
self.promptCustoms += [ 'Configuration/DataProcessing/RecoTLR.customisePostEra_Run2_2017_ppRef' ]
self.expressCustoms += [ 'Configuration/DataProcessing/RecoTLR.customisePostEra_Run2_2017_ppRef' ]
self.visCustoms += [ 'Configuration/DataProcessing/RecoTLR.customisePostEra_Run2_2017_ppRef' ]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's reuse the available customisePostEra_Run2_2017

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nm, I actually opted to make a new method for Run2_2017_pp_on_XeXe.
so, no change


_ecalClustersHI_ppRef = ecalClusters.copy()
_ecalClustersHI_ppRef += islandBasicClusters
ppRef_2017.toReplaceWith(ecalClusters, _ecalClustersHI_ppRef)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can this be simply the same as what's used above for pA_2016 etc?

Copy link
Contributor Author

@ttrk ttrk Nov 1, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This new era does not need the full islandClusteringSequence, but only islandBasicClusters.
Your suggestion would also work, in that case the other modules in islandClusteringSequence would not be run, since their output will not be used.
I chose to make the customization only for those modules that are going to be run. That is why I made it separate.
What do you suggest ? If you want, I can move the modification and make it part of what is done before.

from Configuration.Eras.Modifier_ppRef_2017_cff import ppRef_2017
for ec in [RecoEgammaAOD.outputCommands, RecoEgammaRECO.outputCommands, RecoEgammaFEVT.outputCommands]:
ppRef_2017.toModify( ec, func=lambda outputCommands: outputCommands.extend(['keep recoHIPhotonIsolationedmValueMap_photonIsolationHIProducerppGED_*_*',
'keep recoHIPhotonIsolationedmValueMap_photonIsolationHIProducerpp_*_*'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there an obvious need to be surgical here and not simply follow the same mods as for pA_2016 above?

Copy link
Contributor Author

@ttrk ttrk Nov 1, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as the previous comment. islandPhotons are not added by this. So I made a separate block. If you agree, then I can move it to the block of pA_2016.

@slava77
Copy link
Contributor

slava77 commented Nov 1, 2017

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 1, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/24109/console Started: 2017/11/01 21:30

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 1, 2017

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 1, 2017

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 1, 2017

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

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 1 differences found in the comparisons
  • DQMHistoTests: Total files compared: 26
  • DQMHistoTests: Total histograms compared: 2838442
  • DQMHistoTests: Total failures: 112
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2838159
  • DQMHistoTests: Total skipped: 171
  • DQMHistoTests: Total Missing objects: 0
  • Checked 107 log files, 10 edm output root files, 26 DQM output files

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 6, 2017

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 6, 2017

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-21122/1846

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 6, 2017

Pull request #21122 was updated. @perrotta, @prebello, @kpedro88, @fabozzi, @cmsbuild, @franzoni, @slava77, @GurpreetSinghChahal, @davidlange6 can you please check and sign again.

@slava77
Copy link
Contributor

slava77 commented Nov 6, 2017

@cmsbuild please test workflow 149.0

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 6, 2017

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

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 7, 2017

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 7, 2017

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 7, 2017

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

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 26
  • DQMHistoTests: Total histograms compared: 2900266
  • DQMHistoTests: Total failures: 1
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2900094
  • DQMHistoTests: Total skipped: 171
  • DQMHistoTests: Total Missing objects: 0
  • Checked 107 log files, 10 edm output root files, 26 DQM output files

@slava77
Copy link
Contributor

slava77 commented Nov 7, 2017

+1

for #21122 243c2e4

  • ppRef_2017 modifier, Run2_2017_ppRef era, and ppEra_Run2_2017_ppRef T0 processing scenarios are defined to keep additional producers for analysis.
    • apparently for T0 all other setups should use the regular 2017
  • jenkins tests pass, including wf 149.0
  • local test of 149.0 shows that the extra producers and their products show up and do not introduce a large increase in cost.

@davidlange6
Copy link
Contributor

merge

@cmsbuild cmsbuild merged commit 2a61fa0 into cms-sw:master Nov 7, 2017
@@ -1569,6 +1575,8 @@ def gen2018HiMix(fragment,howMuch):
steps['RECOHI2015']=merge([hiDefaults2015,{'-s':'RAW2DIGI,L1Reco,RECO,VALIDATION,DQM'},step3Up2015Defaults])
steps['RECOHI2011']=merge([hiDefaults2011,{'-s':'RAW2DIGI,L1Reco,RECO,VALIDATION,DQM'},step3Defaults])

steps['RECOPPREF2017']=merge([ppRefDefaults2017,step3Up2015Defaults])
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I notice that in the 94X backport PR (#21069) this line reads

steps['RECOPPREF2017']=merge([ppRefDefaults2017,{'-s':'RAW2DIGI,L1Reco,RECO,EI,PAT,VALIDATION:@standardValidation+@miniAODValidation,DQM:@standardDQM+@miniAODDQM'},step3Up2015Defaults])

i.e. the RECOSIM got removed: I think the same should be also done here

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@perrotta
I don't understand your comment.
Please elaborate.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I consider this PR the correct implementation #21122 (comment)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, thank you Slava. I supposed it was done on purpose, instead.
Then it has to be fixed in the backport: I will add a note o that PR

@fabozzi
Copy link
Contributor

fabozzi commented Nov 7, 2017

+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