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

Light by light modifier 1100 pre1 #27633

Merged
merged 9 commits into from
Aug 22, 2019

Conversation

rchudasa
Copy link
Contributor

PR description:

This PR is submitted to reconstruct low pT photons down to 2 GeV for light by light scattering. It is just about relaxing few thresholds in python config with no changes in c++ source code. A modifier has been added to access the low pt photon reconstruction. Photon and electron efficiency plots and timing with default and modified reconstruction can be found in slides [1] presented in Reconstruction and Analysis Tools meeting. The modified reconstruction has been reviewed by Egamma POG convener @Sam-Harper .
[1]https://indico.cern.ch/event/836517/contributions/3513898/attachments/1887027/3111085/cms_reco_meeting_26thJuly_2019.pdf

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27633/11126

Code check has found code style and quality issues which could be resolved by applying following patch(s)

@@ -0,0 +1,4 @@
import FWCore.ParameterSet.Config as cms
Copy link
Contributor

Choose a reason for hiding this comment

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

Configuration/ProcessModifiers/python might be a better place

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I tried to keep this modifier in ProcessModifiers repo as suggested by you and tried to run cmsDriver command with --era Run2_2018 --procModifiers lightByLightLowPt but it tries to find this Modifier in Eras repo, could you please suggest what else should I modify, so that cmsDriver command recognizes it from ProcessModifiers repo?

@slava77
Copy link
Contributor

slava77 commented Jul 30, 2019

Photon and electron efficiency plots and timing with default and modified reconstruction can be found in slides [1] presented in Reconstruction and Analysis Tools meeting. The modified reconstruction has been reviewed by Egamma POG convener @Sam-Harper .
[1]https://indico.cern.ch/event/836517/contributions/3513898/attachments/1887027/3111085/cms_reco_meeting_26thJuly_2019.pdf

I missed this part of the meeting.
What do you imply by the "default reco"?
Naively, given the 10_3_X context and HI PDs, I can guess that this is about pp_on_AA,
but I'm not sure.

Is this expected to be a once-in-CMS-lifetime for 10_3_X use case or should this be a supported workflow?

@rchudasa
Copy link
Contributor Author

Photon and electron efficiency plots and timing with default and modified reconstruction can be found in slides [1] presented in Reconstruction and Analysis Tools meeting. The modified reconstruction has been reviewed by Egamma POG convener @Sam-Harper .
[1]https://indico.cern.ch/event/836517/contributions/3513898/attachments/1887027/3111085/cms_reco_meeting_26thJuly_2019.pdf

I missed this part of the meeting.
What do you imply by the "default reco"?
Naively, given the 10_3_X context and HI PDs, I can guess that this is about pp_on_AA,
but I'm not sure.

Is this expected to be a once-in-CMS-lifetime for 10_3_X use case or should this be a supported workflow?

The default reco is pp reconstruction with era "Run2_2018" and on top of that light by light modifier has been added. We don't use or modify pp_on_AA era as it modifies many Egamma thresholds to higher values which we don't want.
This is a supported workflow for higher CMSSW release and even for pp analyses, if required. :)

@slava77
Copy link
Contributor

slava77 commented Jul 30, 2019

The default reco is pp reconstruction with era "Run2_2018"

uhm, so this make a stronger case for backporting this at best to 10_6_X to be based on the UL release.

@slava77
Copy link
Contributor

slava77 commented Aug 1, 2019

@rchudasa
there is a merge conflict in this PR now
Please update.

@cmsbuild
Copy link
Contributor

cmsbuild commented Aug 1, 2019

The code-checks are being triggered in jenkins.

Copy link
Contributor Author

@rchudasa rchudasa left a comment

Choose a reason for hiding this comment

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

@rchudasa
there is a merge conflict in this PR now
Please update.

@slava77 , I just committed a change now. Please note that I have not changed the location of lightbylight modifier to ProcessModifier repo yet, as cmsDriver command could not identify that.

@@ -0,0 +1,4 @@
import FWCore.ParameterSet.Config as cms
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I tried to keep this modifier in ProcessModifiers repo as suggested by you and tried to run cmsDriver command with --era Run2_2018 --procModifiers lightByLightLowPt but it tries to find this Modifier in Eras repo, could you please suggest what else should I modify, so that cmsDriver command recognizes it from ProcessModifiers repo?

@cmsbuild
Copy link
Contributor

cmsbuild commented Aug 1, 2019

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27633/11237

@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-bda038/1975/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 34
  • DQMHistoTests: Total histograms compared: 2939508
  • DQMHistoTests: Total failures: 1
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2939166
  • DQMHistoTests: Total skipped: 341
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 33 files compared)
  • Checked 142 log files, 14 edm output root files, 34 DQM output files

@slava77
Copy link
Contributor

slava77 commented Aug 14, 2019

@rchudasa
compared to the test command in #27633 (comment)
I'm missing the event content modifications for the following in the latest version of the PR

"keep *_interestingGedEgammaIsoESDetId_*_*", "keep *_interestingGedEgammaIsoHCALDetId_*_*", 
"keep *_interestingGedEleIsoDetIdEB_*_*", "keep *_interestingGedEleIsoDetIdEE_*_*",
"keep *_interestingGedGamIsoDetIdEB_*_*","keep *_interestingGedGamIsoDetIdEE_*_*",
"keep EBDigiCollection_ecalDigis__*","keep EEDigiCollection_ecalDigis__*","keep ESDigiCollection_ecalPreshowerDigis__*",

Please check and confirm that these are not needed or update the PR to include the missing parts.

Also, compared to the test setup, the following were added

     'keep ZDCDataFramesSorted_hcalDigis_*_*',
    'keep ZDCDataFramesSorted_castorDigis_*_*',
    'keep QIE10DataFrameHcalDataFrameContainer_hcalDigis_ZDC_*'

ZDC data is small, so it seems OK to add if it's needed.

@rchudasa
Copy link
Contributor Author

@rchudasa
compared to the test command in #27633 (comment)
I'm missing the event content modifications for the following in the latest version of the PR

"keep *_interestingGedEgammaIsoESDetId_*_*", "keep *_interestingGedEgammaIsoHCALDetId_*_*", 
"keep *_interestingGedEleIsoDetIdEB_*_*", "keep *_interestingGedEleIsoDetIdEE_*_*",
"keep *_interestingGedGamIsoDetIdEB_*_*","keep *_interestingGedGamIsoDetIdEE_*_*",
"keep EBDigiCollection_ecalDigis__*","keep EEDigiCollection_ecalDigis__*","keep ESDigiCollection_ecalPreshowerDigis__*",

Please check and confirm that these are not needed or update the PR to include the missing parts.

Also, compared to the test setup, the following were added

     'keep ZDCDataFramesSorted_hcalDigis_*_*',
    'keep ZDCDataFramesSorted_castorDigis_*_*',
    'keep QIE10DataFrameHcalDataFrameContainer_hcalDigis_ZDC_*'

ZDC data is small, so it seems OK to add if it's needed.

I consulted @Sam-Harper and concluded that we dont need those event contents as they are already present in reducedEgamma rechit collection. We require ZDC event content for the analysis.

@slava77
Copy link
Contributor

slava77 commented Aug 15, 2019

I consulted @Sam-Harper and concluded that we dont need those event contents as they are already present in reducedEgamma rechit collection. We require ZDC event content for the analysis.

Do you really mean "reducedEgamma"? This is a module from miniAOD.
In the earlier discussion we concluded that you will not run/need miniAOD.

Perhaps you actually mean other reduced rechit collections available in AOD.
Please clarify/confirm.

@rchudasa
Copy link
Contributor Author

I consulted @Sam-Harper and concluded that we dont need those event contents as they are already present in reducedEgamma rechit collection. We require ZDC event content for the analysis.

Do you really mean "reducedEgamma"? This is a module from miniAOD.
In the earlier discussion we concluded that you will not run/need miniAOD.

Perhaps you actually mean other reduced rechit collections available in AOD.
Please clarify/confirm.

Sorry, for the confusion. We will use AOD content and to be precise, reducedEcalRecHitsEB, reducedEcalRecHitsEE, reducedEcalRecHitsES collections.

@slava77
Copy link
Contributor

slava77 commented Aug 15, 2019

+1

for #27633 fb097ff

  • code changes are in line with the PR description and the follow up review
  • jenkins tests pass and comparisons with the baseline show no differences (the new process modifier is not exercised)
  • the latest updates should not change conclusions made in test in Light by light modifier 1100 pre1 #27633 (comment) (or in the PR description). Some moderate cleanup of the keep statements should reduce the event size by ~1 kB/event to just under 30 kB/evt (compared to an increase from 19 to 31 kiB observed in the earlier tests)

@slava77
Copy link
Contributor

slava77 commented Aug 19, 2019

@fabiocos @kpedro88
please check this and comment or merge some time soon.
Thank you.

@cmsbuild cmsbuild mentioned this pull request Aug 19, 2019
@kpedro88
Copy link
Contributor

+1
At some point (once decisions on production are made), a workflow using this modifier should be put into the matrix.

@kpedro88
Copy link
Contributor

merge

@cmsbuild cmsbuild merged commit b5741be into cms-sw:master Aug 22, 2019
@fabiocos
Copy link
Contributor

fabiocos commented Sep 2, 2019

+operations

the addition of the modifier is correct, although it is not activated by default in a test workflow

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 2, 2019

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 be automatically merged.

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.

7 participants