-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Move Sequence to Task for RecoLocalCalo config files #27474
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27474/10802
|
A new Pull Request was created by @jeongeun for master. It involves the following packages: RecoLocalCalo/Configuration @perrotta, @cmsbuild, @kpedro88, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
HGCalRecHit, | ||
hgcalLayerClusters, | ||
hgcalMultiClusters, | ||
particleFlowRecHitHGCTask, |
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 wonder whether one couldn't simply add here particleFlowRecHitHGC
from RecoParticleFlow.PFClusterProducer.particleFlowRecHitHGC_cfi
, instead of the task which only contains that module.
@lgray @felicepantaleo @rovere : was there a reason for having originally a sequence defined with one single module in RecoParticleFlow/PFClusterProducer/python/particleFlowRecHitHGC_cff.py
? (As a corollary: could that cff file be removed now when moving to unscheduled execution?)
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 cannot comment for the past history, but I see not special reason.
As for the Task, we could bypass it but I'm not sure if there is any added value.
please test |
The tests are being triggered in jenkins. |
@@ -26,11 +26,13 @@ | |||
# | |||
# sequence CaloLocalReco and CaloGlobalReco | |||
# | |||
calolocalreco = cms.Sequence(ecalLocalRecoSequence+hcalLocalRecoSequence) | |||
calolocalrecoTask = cms.Task(ecalLocalRecoTask,hcalLocalRecoTask) | |||
calolocalreco = cms.Sequence(calolocalrecoTask) | |||
caloglobalreco = cms.Sequence(hcalGlobalRecoSequence) |
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.
Why not also migrating this sequence?
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.
Thank you for your every comments.
I kept this sequence that have one module(hbhereco).
In this PR, I modified the sequences that has more than one modules.
In cmssw/RecoLocalCalo/Configuration/python/hcalGlobalReco_cff.py
from RecoLocalCalo.HcalRecProducers.HBHEIsolatedNoiseReflagger_cfi import *
hcalGlobalRecoSequence = cms.Sequence(hbhereco)
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.
Indeed, this sequence is never used, it only includes hcalGlobalRecoSequence
from RecoLocalCalo/Configuration/python/hcalGlobalReco_cff.py
(which in its turn is only used for the globalreco_tracking
reconstruction sequence) and it can be misleading here: I would suggest to just remove it
@@ -20,7 +20,8 @@ | |||
# | |||
# sequence CaloLocalReco and CaloGlobalReco | |||
# | |||
calolocalreco = cms.Sequence(ecalLocalRecoSequence+hcalLocalRecoSequence) | |||
calolocalrecoTask = cms.Task(ecalLocalRecoTask,hcalLocalRecoTask) | |||
calolocalreco = cms.Sequence(calolocalrecoTask) | |||
caloglobalreco = cms.Sequence(hcalGlobalRecoSequence) |
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.
Why not also migrating this sequence?
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.
Indeed, this sequence is never used, it only includes hcalGlobalRecoSequence
from RecoLocalCalo/Configuration/python/hcalGlobalReco_cff.py
(which in its turn is only used for the globalreco_tracking
reconstruction sequence) and it can be misleading here: I would suggest to just remove it
please abort |
Jenkins tests are aborted. |
please test workflow 29093.52 |
The tests are being triggered in jenkins. |
+upgrade |
+1 |
For completeness, and for simmetry with the other reconstruction sequences, one could further adapt also Configuration/StandardSequences/python/ReconstructionHeavyIons_cff.py |
+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, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 @perrotta thanks |
PR description: Move Sequence to Task for RecoLocalCalo's config files
I replaced the sequence by instantiating it with a task.
PR validation:
Tested in CMSSW_11_0_X_2019-07-07-2300 release.
The PR passes the basic test procedure suggested in the CMSSW PR instructions.