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
migrate ootPhoton to use GEDPhotonProducer #19264
migrate ootPhoton to use GEDPhotonProducer #19264
Conversation
@cmsbuild please test |
The tests are being triggered in jenkins. |
A new Pull Request was created by @slava77 (Slava Krutelyov) for master. It involves the following packages: RecoEgamma/EgammaPhotonProducers @perrotta, @cmsbuild, @slava77, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
-1 Tested at: 2ae60bf You can see the results of the tests here: I found follow errors while testing this PR Failed tests: RelVals AddOn
When I ran the RelVals I found an error in the following worklfows: runTheMatrix-results/140.53_RunHI2011+RunHI2011+RECOHID11+HARVESTDHI/step2_RunHI2011+RunHI2011+RECOHID11+HARVESTDHI.log136.731 step1 DAS Error
I found errors in the following addon tests: cmsDriver.py RelVal -s HLT:HIon,RAW2DIGI,L1Reco,RECO --data --scenario=HeavyIons -n 10 --conditions auto:run2_data_HIon --relval 9000,50 --datatier "RAW-HLT-RECO" --eventcontent FEVTDEBUGHLT --customise=HLTrigger/Configuration/CustomConfigs.L1THLT --era Run2_2016,Run2_HI --magField 38T_PostLS1 --processName=HLTRECO --filein file:RelVal_Raw_HIon_DATA.root --fileout file:RelVal_Raw_HIon_DATA_HLT_RECO.root : FAILED - time: date Fri Jun 16 00:58:46 2017-date Fri Jun 16 00:47:14 2017 s - exit: 16640 |
Comparison not run due to runTheMatrix errors (RelVals and Igprof tests were also skipped) |
Checking the runTheMatrix 140.53 logs: ----- Begin Fatal Exception 16-Jun-2017 00:00:35 CEST----------------------- and then the AddOn test for the first one that failed: It seems that the HeavyIon 2011 config needs work to pick up the primary vertices... |
Pull request #19264 was updated. @perrotta, @cmsbuild, @slava77, @davidlange6 can you please check and sign again. |
@cmsbuild please test 140.53 runs OK locally with the last update. |
The tests are being triggered in jenkins. |
its "fixed" in the 1100 IB
… On Jun 16, 2017, at 2:22 PM, Slava Krutelyov ***@***.***> wrote:
@cmsbuild please test
@smuzaffar @davidlange6
was the issue with 136.731 step1 DAS Error resolved already?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
On 6/16/17 5:24 AM, David Lange wrote:
its "fixed" in the 1100 IB
OK.
So, this test attempt will still fail, since jenkins is still on -2300
…
> On Jun 16, 2017, at 2:22 PM, Slava Krutelyov ***@***.***> wrote:
>
> @cmsbuild please test
>
> @smuzaffar @davidlange6
> was the issue with 136.731 step1 DAS Error resolved already?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#19264 (comment)>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/AEdcbta4GP_aruvB5DyIPtXHFdYzQ0tPks5sEnP-gaJpZM4N7yVd>.
|
@cmsbuild please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@kmcdermo @Sam-Harper The comparisons show that there is a difference in caloPosition of the photon produced by GEDPhotonProducer compared to the PhotonProducer. Here is a sample of differences in workflow 136.761 after running on 400 events
I can guess that for a uniform treatment, you'd rather have the position the same as in gedPhotons, which use the same PF clustering as OOT photons. Please confirm. For the possible future migration of the legacy PhotonProducer to use the GEDPhotonProducer, this position recalculation will need to be added to GEDPhotonProducer. |
@slava77 , you are correct in asserting a more uniform treatment is preferred. Given that we use the same steps in forming superclusters for the ootPhotons as the gedPhotons, it would be better to have the same caloPosition assignment as the gedPhotons. |
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 requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar |
+1 |
Legacy PhotonProducer was not good enough for ootPhotons: important functionality (some of showerShapeVariables) was missing.
There was an attempt to update the legacy photon producer in #19060, but it effectively lead to a copy of GEDPhotonProducer.
This PR makes needed changes to make GEDPhotonProducer work for non-GED setup (no PFEGammaCandidates on inputs)
I checked on wf 136.761 and see that only showerShapeVariables_ show up which were zero in the baseline. Kinematics of the ootPhotons and other variables did not change. The chosen workflow is not the best though (only 4 OOT photons in 200 events).
From visual inspection (confirmed by @kmcdermo ) this PR should produce correct outputs.