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
drop type specs in RecoEcal #31332
drop type specs in RecoEcal #31332
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31332/18092
|
A new Pull Request was created by @jeongeun (JeongEun Lee) for master. It involves the following packages: RecoEcal/EgammaClusterProducers @perrotta, @jpata, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins.
|
multi5x5SuperClustersUncleaned.endcapClusterProducer = cms.string('multi5x5BasicClustersUncleaned') | ||
|
||
multi5x5SuperClustersUncleaned = multi5x5SuperClustersCleaned.clone( | ||
endcapClusterProducer = cms.string('multi5x5BasicClustersUncleaned') |
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.
"string" can be dropped
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.
No, forget it @jeongeun : the corresponding parameter is not listed in the cloned config
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.
Triggered by this finding, I'm realizing that a Multi5x5SuperClusterProducer
does not require a parameter called "endcapClusterProducer" (which would be needed by a HiSuperClusterProducer
, instead).
If I'm not wrong, one should have replaced here instead
endcapClusterTag= cms.InputTag('multi5x5BasicClustersUncleaned',
'multi5x5EndcapBasicClusters'),
@afiqaize @SohamBhattacharya could you please have a look and tell us if there is a bug here?
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@afiqaize @SohamBhattacharya could you please check if there is actually a bug in the configuration of the |
iirc multi 5x5 is an old SC algo that we don't use anymore in pp reconstruction, so this fix should have no effect. is this is used anywhere at the moment? also, shouldn't it be an error if a module ( |
Thank you @afiqaize
If so, it is probably time to clean it up from the release and avoid maintaining unneeded code in it (but also read below)
Well, as far as I can see it is still kept in some AlCa and HI event contents:
Moreover, I see it entering the
No, because no |
Ok, I do remember it being used in HI (though not until what point) so this is not surprising. As for AlCa, maybe for validation purposes. I'll have to check with other EGM experts. Nevertheless, iiuc what concerns this PR is only the existence of a spurious parameter, which should not affect any output. If this is correct I think we can go ahead with the fix without problems...
...perhaps even adding the validation to prevent similar problems in the future. |
please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
As expected, having fixed the configuration for the Apparently, there are more worklows in which those multi 5x5 are used with respect to what guessed by EGamma (see #31332 (comment)): it is therefore urgent to clean them out from pp reco sequences if they are really not needed. Since now there is the correct [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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Update the safer syntax for existing parameter :
Instead of modifying parameters with full type specs, which can be interpreted as an insertion of a new parameter, it is a safer way to protect from parameter name mistakes and will also help in possible parameter migrations.
(The references were PR#30700, PR#30827, PR#30947,PR#31162,PR#31243)
In this PR, total 10 files updated.
PR validation:
Event Content comparison check was also done and there is no change with these updates.
Tested in CMSSW_11_2_X, the basic test all passed in the CMSSW PR instructions.