-
Notifications
You must be signed in to change notification settings - Fork 4.6k
HGCAL RecHits Calibration for V16 geometry scenario #36728
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
c8fc8bb
424f5dd
cb4ac8a
1d4a3bb
85870a5
b1e60ce
a2c4777
a75738c
b654f38
eb55bd2
1a7c1c6
bb1066b
2e499e2
9c8c05a
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 |
|---|---|---|
|
|
@@ -4,6 +4,8 @@ | |
|
|
||
| fCPerMIP_v10 = cms.vdouble(2.06,3.43,5.15) #120um, 200um, 300um | ||
|
|
||
| fCPerMIP_v16 = fCPerMIP_v10 | ||
|
||
|
|
||
| # HGCAL producer of rechits starting from digis | ||
| HGCalUncalibRecHit = cms.EDProducer( | ||
| "HGCalUncalibRecHitProducer", | ||
|
|
@@ -75,6 +77,10 @@ | |
| phase2_hgcalV10.toModify( HGCalUncalibRecHit.HGCEEConfig , fCPerMIP = fCPerMIP_v10 ) | ||
| phase2_hgcalV10.toModify( HGCalUncalibRecHit.HGCHEFConfig , fCPerMIP = fCPerMIP_v10 ) | ||
|
|
||
| from Configuration.Eras.Modifier_phase2_hgcalV12_cff import phase2_hgcalV12 | ||
| phase2_hgcalV12.toModify( HGCalUncalibRecHit.HGCEEConfig , fCPerMIP = fCPerMIP_v16 ) | ||
| phase2_hgcalV12.toModify( HGCalUncalibRecHit.HGCHEFConfig , fCPerMIP = fCPerMIP_v16 ) | ||
|
|
||
| from Configuration.Eras.Modifier_phase2_hfnose_cff import phase2_hfnose | ||
| phase2_hfnose.toModify( HGCalUncalibRecHit.HGCHFNoseConfig , | ||
| isSiFE = True , | ||
|
|
||
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.
Would it make sense to call the first
weightasdummy_weight, to make it clear that it is associated with a non-existing layer?That would also make the formula a little more explicit by using that value instead of
weightsPerLayer[0], to make it clear that you are also adding at the end a dummy value, not the first weight, that would make no sense.The same would be true for
res[0] = dummy_weightas well.Actually, you could directly add
[weightsPerLayer[-1]]as the last element and remove theres[-1] = res[-2], to make it explicit that the last layer has no mean.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'm still convinced that extending the second array with the last element, and not with the first, dummy one, would make the code easier and remove the necessity of setting
res[-1]manually, no?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.
Ok, I removed it.