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
island photons for XeXe collision era #20929
island photons for XeXe collision era #20929
Conversation
The code-checks are being triggered in jenkins. |
+code-checks |
A new Pull Request was created by @ttrk (Kaya Tatar) for master. It involves the following packages: RecoEcal/Configuration @perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test workflow 148.0 |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@@ -26,8 +26,14 @@ | |||
from Configuration.Eras.Modifier_pp_on_XeXe_2017_cff import pp_on_XeXe_2017 | |||
|
|||
from RecoEcal.EgammaClusterProducers.islandBasicClusters_cfi import islandBasicClusters | |||
from RecoHI.HiEgammaAlgos.HiIslandSuperClusters_cfi import islandSuperClusters | |||
from RecoHI.HiEgammaAlgos.HiCorrectedIslandBarrelSuperClusters_cfi import correctedIslandBarrelSuperClusters | |||
from RecoHI.HiEgammaAlgos.HiCorrectedIslandEndcapSuperClusters_cfi import correctedIslandEndcapSuperClusters |
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.
all of these 3 imports can collide with the same names possibly already imported.
This ambiguity should be removed.
More transparent way may be to apply era modifiers (.toReplaceWith) to the original definitions used in RecoEcal/EgammaClusterProducers
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.
The first option that comes to my mind is to do something like the following. Is that what you are asking for ?
from RecoEcal.EgammaClusterProducers.islandClusteringSequence_cff import islandClusteringSequence
_ecalClustersHI = ecalClusters.copy()
_ecalClustersHI += islandClusteringSequence
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.
that will come as a consequence of the changes I proposed in the original definition location.
Another alternative is to change names of HI-specific islandSuperClusters and other modules to hiIslandSuperClusters and so on.
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.
Can you give an example for the proposed changes in the original definition location ? I want to make sure I understand.
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.
@ttrk : the point is that (for example) the module "islandSuperClusters" has the same name in both
RecoEcal/EgammaClusterProducers/python/islandSuperClusters_cfi.py
and
RecoHI/HiEgammaAlgos/python/HiIslandSuperClusters_cfi.py
(and a different configuration).
Therefore, if you import one of them in this RecoEcal_cff.py you prevent importing the other one, or you end up with ambiguities in the configurations.
The solution could be to rename, e.g., hiIslandSuperClusters the module in HiIslandSuperClusters_cfi.py (and the same for the other modules), and then use the eras to add the correct modules either here (as you do now), or, probably better, inside the islandClusteringSequence, as you also suggested.
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.
@perrotta Thanks for the explanation. I understand the ambiguity resulting from that the modules in different files are given the same names.
However when @slava77 mentioned it as "Another alternative" (#20929 (comment)), it sounded to me as if renaming the HI-specific modules is an "alternative" way and one can solve the ambiguity without renaming modules.
Anyway I will rename the HI-specific modules.
…me" ambiguity with the modules under RecoEcal/EgammaClusterProducers/
…fic islandSuperClusters modules
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+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) |
@ttrk : you probably want to backport this PR to 94X, and 92X as well Please prepare the backport PR(s) if so |
apply the era modifiers to the original definitions in RecoEcal/EgammaClusterProducers as suggested here cms-sw#20929 (comment) and here cms-sw#20929 (comment)
@perrotta : I need to make a new PR which adds an era for pp reference run. It will modify some of the files in this PR. Should I wait for this PR to be merged (to avoid conflicts) or do you recommend something else ? |
Well, this relates to the question I made in the 92X backport of this PR.... If this PR, in its present form, need to enter quickly in 82X (or 94X) for the XeXe run reprocessing or whatever else reason, I'd suggest to have it merged (it is simple, and therefore it could be done in short, probably). If this is just an intermediate step for the pp reference run reco, then you can even modify this PR itself, and then the review process will restart on it. In that case, I imagine that the 92X and 94X backport could be momentarily closed while this one converges. So the question is the same: what are your plans for this PR? |
@perrotta Can we merge this PR and the backports asap ? My branch for the new PR is more or less ready. If these are merged, then I can make the new PR with era for pp reference today/tomorrow. |
Let check with @davidlange6 which are the plans for merging this PR and its backports (@ttrk please take however into account that backport merging normally requires at lest one IB cycle after the PR in the master is merged) |
|
||
from RecoHI.HiEgammaAlgos.HiCorrectedIslandEndcapSuperClusters_cfi import correctedIslandEndcapSuperClusters as _hiCorrectedIslandEndcapSuperClusters | ||
|
||
for e in [pA_2016, peripheralPbPb, pp_on_XeXe_2017]: |
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.
It seems there should be an easy way to avoid this ever lengthening set of modifiers and just have one.. I'll try to suggest something
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 will make a new PR which adds an era for 2017 pp ref run. I can implement your suggestion in the new PR.
merge |
fixes the pp_on_XeXe_2017 era to run island photons and add them into event content
original PR for pp_on_XeXe_2017 era : #20749