-
Notifications
You must be signed in to change notification settings - Fork 4.6k
[HGCAL] Corrections in noise vector in CLUE #32021
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
Changes from 4 commits
ad4acda
49c1fc0
9555756
feb70d5
7d64f80
35d775c
ed0b9b6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -6,18 +6,21 @@ | |||||
|
|
||||||
| from RecoLocalCalo.HGCalRecProducers.HGCalUncalibRecHit_cfi import HGCalUncalibRecHit | ||||||
|
|
||||||
| from SimCalorimetry.HGCalSimProducers.hgcalDigitizer_cfi import fC_per_ele, hgceeDigitizer, hgchebackDigitizer, hfnoseDigitizer | ||||||
| from SimCalorimetry.HGCalSimProducers.hgcalDigitizer_cfi import fC_per_ele, HGCAL_noises, hgceeDigitizer, hgchebackDigitizer, hfnoseDigitizer | ||||||
|
|
||||||
| hgcalLayerClusters = hgcalLayerClusters_.clone() | ||||||
|
|
||||||
| hgcalLayerClusters.timeOffset = hgceeDigitizer.tofDelay | ||||||
| hgcalLayerClusters.plugin.dEdXweights = cms.vdouble(dEdX.weights) | ||||||
| #With the introduction of 7 regional factors (6 for silicon plus 1 for scintillator), | ||||||
| #we extend fcPerMip (along with noises below) so that it is guaranteed that they have 6 entries. | ||||||
| hgcalLayerClusters.plugin.fcPerMip = cms.vdouble(HGCalUncalibRecHit.HGCEEConfig.fCPerMIP + HGCalUncalibRecHit.HGCHEFConfig.fCPerMIP) | ||||||
| hgcalLayerClusters.plugin.thicknessCorrection = cms.vdouble(HGCalRecHit.thicknessCorrection) | ||||||
| hgcalLayerClusters.plugin.sciThicknessCorrection = HGCalRecHit.sciThicknessCorrection | ||||||
| hgcalLayerClusters.plugin.deltasi_index_regemfac = HGCalRecHit.deltasi_index_regemfac | ||||||
| hgcalLayerClusters.plugin.fcPerEle = cms.double(fC_per_ele) | ||||||
| hgcalLayerClusters.plugin.noises = cms.PSet(refToPSet_ = cms.string('HGCAL_noises')) | ||||||
| #Extending noises as fcPerMip, see comment above. | ||||||
| hgcalLayerClusters.plugin.noises = cms.vdouble(HGCAL_noises.values + HGCAL_noises.values) | ||||||
|
||||||
| hgcalLayerClusters.plugin.noises = cms.vdouble(HGCAL_noises.values + HGCAL_noises.values) | |
| hgcalLayerClusters.plugin.noises = HGCAL_noises.values + HGCAL_noises.values |
please drop type specifications for all parameters which already exist.
This is a safer way to protect from parameter name mistakes and will also help in possible parameter migrations.
it looks like this file did not make it to #30147 and the "drop type specs" migration task:
- in the lines above the
hgcalLayerClusters = hgcalLayerClusters_.clone()appears separately from the parameters modified later - in the lines below inside a clone
nHitsTime = cms.uint32(3)from the old code still appears with type details
@jeongeun please check/clarify what happened.
I made a few comments to this file mainly for the updated lines, but it looks like our migration missed this file somehow
Outdated
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.
| nHitsTime = cms.uint32(3), | |
| nHitsTime = 3, |
or can be dropped because it's the same in the original hgcalLayerClusters_
Outdated
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.
| maxNumberOfThickIndices = cms.uint32(3), | |
| maxNumberOfThickIndices = 3, |
Outdated
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.
| noises = cms.vdouble(HGCAL_noises.values), | |
| noises = HGCAL_noises.values.value(), |
please drop type specifications for all parameters which already exist.
This is a safer way to protect from parameter name mistakes and will also help in possible parameter migrations.
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.
May I suggest the possibly cleaner (I hope the syntax is still correct...):