-
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
Drop type specs in RecoHI {Configuration, HiTracking} #32386
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32386/20252
|
A new Pull Request was created by @jeongeun (JeongEun Lee) for master. It involves the following packages: RecoHI/Configuration @perrotta, @jpata, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@@ -11,8 +11,9 @@ | |||
|
|||
#Tracks | |||
hiSignalGlobalPrimTracks = hiGlobalPrimTracks.clone() | |||
hiSignalSelectedTracks = hiSelectedTracks.clone() | |||
hiSelectedTracks.src = cms.InputTag("hiSignalGlobalPrimTracks") | |||
hiSignalSelectedTracks = hiSelectedTracks.clone( |
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.
Here the hiSignalSelectedTracks
are updated with the input collection "hiSignalGlobalPrimTracks", but then later the heavyIonTrackingTask
is feeed with the (unmodified) hiSelectedTracks
: I wonder how it can even work
I suppose you already tested it, e.g. with the HI workflows in the matrix tests (140.43, 140.46, 158.01): but it is possible that you wouldn't get an error in that case, because it does not seem to me that this Reconstruction_hiSignal_cff.py is ever included in any actual reconstruction sequence.
Let then involve the HI reco contact, @mandrenguyen :
- I already noticed in my comment for the previous version of this PR that already the original formulation of this PR was bugged; I don't think this update is actually fixing it
- I don't see this Reconstruction_hiSignal_cff.py ever used in the configs in CMSSW
- Do you have any suggestion (based on a possible usage of this python snippet) for fixing it? If this file isn't really used anywhere, wouldn't it be more convenient to profit of this PR in order to completely remove it, instead of spending more efforts in trying to fix it?
@mandrenguyen did you have time to check whether RecoHI/Configuration/python/Reconstruction_hiSignal_cff.py is needed to remain in the release? If it is not needed, I would suggest @jeongeun to profit of this PR and remove it; if we decide not to remove it, instead, please Matt suggest some fix for it (see also previous discussions in #32386 (comment) and https://github.com/cms-sw/cmssw/pull/32171/files#r526776262) |
@perrotta Sorry for the slow response. This cff is deprecated and can be removed from the release. |
Thank you @mandrenguyen |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32386/20370
|
please test |
I think I (wrongly) suggested to remove too many |
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 differences wrt the baseline should originate from the updated configuration in
HILowPtConformalPixelTracks_cfi.py
I'd suggest reverting a few more PSet's, for safety.
maxEta = cms.double(100.), | ||
trackQuality = cms.string("any"), | ||
numTracksThreshold = cms.int32(2) | ||
TkFilterParameters = dict( |
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.
This is perhaps correct, but for safety (not all parameters are re-defined here) I'd revert it to a PSet
, as before
HitProducer = cms.string('siPixelRecHits'), | ||
TTRHBuilder = cms.string('WithTrackAngle'), | ||
hiConformalPixelTracksPhase1SeedLayers = lowPtQuadStepSeedLayers.clone( | ||
BPix = dict( |
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.
This should get reverted to PSet
HitProducer = 'siPixelRecHits', | ||
TTRHBuilder = 'WithTrackAngle', | ||
), | ||
FPix = dict( |
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.
This should get reverted to PSet
'BPix1+FPix1_pos', 'BPix1+FPix1_neg', | ||
'BPix2+FPix1_pos', 'BPix2+FPix1_neg', | ||
'FPix1_pos+FPix2_pos', 'FPix1_neg+FPix2_neg'], | ||
BPix = dict( |
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.
This should get reverted to PSet
TTRHBuilder = cms.string('TTRHBuilderWithoutAngle4PixelPairs'), | ||
HitProducer = cms.string('siPixelRecHits'), | ||
), | ||
FPix = dict( |
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.
This should get reverted to PSet
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32386/20434
|
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-8a06e1/11739/summary.html Comparison SummarySummary:
|
+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 previous PR for RecoHI is PR#32031)
In this PR, total 29 files changed.
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.