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
Adding HGCal configuration in electron MC Validations #20934
Conversation
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-20934/1481 Code check has found code style and quality issues which could be resolved by applying a patch in https://cmssdt.cern.ch/SDT/code-checks/PR-20934/1481/git-diff.patch You can run |
The code-checks are being triggered in jenkins. |
+code-checks |
A new Pull Request was created by @archiron (Chiron) for master. It involves the following packages: Validation/RecoEgamma @kmaeshima, @cmsbuild, @vanbesien, @vazzolini, @dmitrijus can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Hi all, |
Hi Marco, |
|
||
from Configuration.Eras.Modifier_phase2_hgcal_cff import phase2_hgcal | ||
phase2_hgcal.toModify( | ||
electronMcFakeValidator, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@beaudett
here we switch from gedGsfElectrons
to ecalDrivenGsfElectronsFromMultiCl
et all for all related collection.
What I was proposing was to clone the original analyzer and run them both at the same time so that gedGsfElectrons
are left as they are (broken for the time being) and FromMultiCl
added. The moment we fix the gedGsfElectrons
there's nothing else/more to touch here. Would that make sense?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. It would be indeed convenient. But we will have duplicate set of histograms then, one broken (with empty histograms) and one filled. Aren't the broken ones take disk-space for nothing ? If you tell me that it is not an issue, then I buy your solution !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@beaudett they will take up both memory and disk space: the latter is very limited, the formes is somehow quite expensive these days. Just to have a rough understanding, of how much histograms are we talking about? I'd then put the histograms in 2 separate folders. That could also be useful to have a comparison later on between the 2 collections.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Marco,
we are speaking of > 1K histograms, with a good fraction of them being 2D.
ElectronMcFakeValidator : 360 histos
ElectronMcSignalValidator : 494 histos
ElectronMcSignalValidatorPt1000 : 494 histos
ElectronMcSignalValidatorMiniAOD : 41 histos
Arnaud reminded me that we had been asked in the past to reduce the number of histograms, and we had to struggle a bit when we introduced the Pt1000 duplicated directory (which is not empty) and for which the ranges of the histograms are adapted.
Therefore, and after some thinking, we are a bit reluctant to clone the sequence and to put a new directory in place. We are aware that it implies that we manually switch back to the regular collection once it is in place.
We hope it is agreeable to you.
Florian & Arnaud
In that case, I totally agree: I thought we were talking about much fewer
histograms.
Ciao,
-- Marco.
…___________
Marco Rovere
Marco.Rovere@cern.ch
CERN EP-CMG | room 40 3-A28 | tel +41227671209 (71209)
On Mon, Oct 23, 2017 at 4:40 AM, Florian Beaudette ***@***.*** > wrote:
***@***.**** commented on this pull request.
------------------------------
In Validation/RecoEgamma/python/ElectronMcFakeValidator_
gedGsfElectrons_cfi.py
<#20934 (comment)>:
> @@ -57,7 +57,18 @@
histosCfg = cms.PSet(electronMcFakeHistosCfg)
)
-
-
-
-
+from Configuration.Eras.Modifier_phase2_hgcal_cff import phase2_hgcal
+phase2_hgcal.toModify(
+ electronMcFakeValidator,
Hi Marco,
we are speaking of > 1K histograms, with a good fraction of them being 2D.
ElectronMcFakeValidator : 360 histos
ElectronMcSignalValidator : 494 histos
ElectronMcSignalValidatorPt1000 : 494 histos
ElectronMcSignalValidatorMiniAOD : 41 histos
Arnaud reminded me that we had been asked in the past to reduce the number
of histograms, and we had to struggle a bit when we introduced the Pt1000
duplicated directory (which is not empty) and for which the ranges of the
histograms are adapted.
Therefore, and after some thinking, we are a bit reluctant to clone the
sequence and to put a new directory in place. We are aware that it implies
that we manually switch back to the regular collection once it is in place.
We hope it is agreeable to you.
Florian & Arnaud
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#20934 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABHaR7cbs4RWR6QCRPpJ0wDdRL4Y-oVCks5svHs8gaJpZM4P7xe6>
.
|
Hello |
I'm begging for this but, apparently, I have no luck. |
I now understand why CMS is so well ranked by github on the amount of discussions :-) |
@cmsbuild please test |
The tests are being triggered in jenkins. |
New categories assigned: upgrade @kpedro88 you have been requested to review this Pull request/Issue and eventually sign? Thanks |
On 10/25/17 10:09 PM, Kevin Pedro wrote:
@slava77 <https://github.com/slava77> I also find this quite puzzling.
Modifications of the Validation subsystem should not be able to affect
reco. In the 2023D19 workflow, the timing-related changes are enabled -
maybe this problem is related to #20621
<#20621>? @lgray
<https://github.com/lgray> @bendavid <https://github.com/bendavid>
It looks like the same is showing up in other PRs
e.g. #20682 (comment)
Is this workflow hitting some uninitialized values
or did it get some extra randomization?
…
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#20934 (comment)>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/AEdcbq1NHSVL_LqZApSIwb7TduZWEnO3ks5sv5WPgaJpZM4P7xe6>.
|
@slava77 I'll run valgrind... |
see first the GitHub thread
https://hypernews.cern.ch/HyperNews/CMS/get/pixelOfflineSW/1335.html
#20397
on these histograms
… On Oct 26, 2017, at 4:26 PM, Kevin Pedro ***@***.***> wrote:
@slava77 I'll run valgrind...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@davidlange6 I had noticed the irreproducibility in Phase1 pixel validation, but I'm not sure if it is related to what was observed here (changes in handful of reco validation plots only in 20434.0, 2023D19 workflow). |
On 10/26/17 4:36 PM, Kevin Pedro wrote:
@davidlange6 <https://github.com/davidlange6> I had noticed the
irreproducibility in Phase1 pixel validation, but I'm not sure if it is
related to what was observed here (changes in handful of reco validation
plots only in 20434.0, 2023D19 workflow).
I don't see how phase-1 pixel validation can change RPC rechit content
in reco.
|
indeed - sorry for the noise.. this one is different.
… On Oct 26, 2017, at 4:36 PM, Kevin Pedro ***@***.***> wrote:
@davidlange6 I had noticed the irreproducibility in Phase1 pixel validation, but I'm not sure if it is related to what was observed here (changes in handful of reco validation plots only in 20434.0, 2023D19 workflow).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
+1 |
+1 |
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 (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
A few modifications have been made for HGCal Phase2 integration into electron MC Validations.
2 small modifcations into Validation/RecoEgamma/plugins/ ('ElectronMcFakeValidator.cc & ElectronMcSignalValidator.cc) related to the scale limits of one histo.
there is modifications into the _cfi files to take HGcal Pahse2 modifications into account (ElectronMcFakeValidator_gedGsfElectrons_cfi.py, ElectronMcSignalValidatorPt1000_gedGsfElectrons_cfi.py & ElectronMcSignalValidator_gedGsfElectrons_cfi.py).
The config files (_cfg.py files) that we use have been rewritten to take modifications into account :
ElectronMcFakePostValidation_cfg.py, ElectronMcFakeValidation_gedGsfElectrons_cfg.py,
ElectronMcSignalPostValidationMiniAOD_cfg.py, ElectronMcSignalValidationMiniAOD_cfg.py,
ElectronMcSignalPostValidationPt1000_cfg.py, ElectronMcSignalValidationPt1000_gedGsfElectrons_cfg.py,
ElectronMcSignalPostValidation_cfg.py, ElectronMcSignalValidation_gedGsfElectrons_cfg.py
We have added 3 files for run simplification :
relval_hgcal.tcsh -> used to launch local computations & web page histos
OvalFile.HGCAL -> used to create web pages histos
electronValidationCheck_Env.py -> used for RECO/HGCal initialization. It is a new file wich is called by our config (_cfg.py) files when we create histograms web pages.
Tests have been made with runTheMatrix without any encountered pbms.
@beaudett @fcouderc @rovere
#CMSSW_9_3_X