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
Increase SiPixel L1 cluster threshold from 2000 to 4000e, synchronize channel threshold between HTL and offline #35518
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35518/25725
|
A new Pull Request was created by @ferencek (Dinko F.) for master. It involves the following packages:
@jpata, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Hi @ferencek, I think also the "legacy" HLT configuration should be updated at |
Take also the opportunity to lower the ChannelThreshold to 10? |
@cmsbuild , please test |
enable gpu |
I think there's a way to reconfigure them all: def customiseForXXXX(process):
for producer in producers_by_type(process, "SiPixelClusterProducer"):
producer.ChannelThreshold = cms.int32(10)
return process |
I am preparing PR for this part |
@tsusa, so you will take care of lowering the ChannelThreshold to 10 in a separate PR, right? |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35518/25731
|
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ce6491/19418/summary.html GPU Comparison SummarySummary:
Comparison SummarySummary:
|
I see that in the reco comparisons the differences are in the Run-3 workflows (expected); they start from the number of clusters and then occasionally propagate downstream to tracking and further higher level quantities.
@cms-sw/trk-dpg-l2 please check/comment. |
@slava77, from the on-track cluster plot for the same wf (12434.0), which shows the difference in 1/486 entries, it seems that those are mostly noise clusters |
+reconstruction
|
+hlt
|
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. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
if hasattr(producer,"ChannelThreshold"): | ||
producer.ChannelThreshold = 10 |
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.
to clarify, this one change is independent and unrelated to the other ones, right ?
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.
Yes, technically the ClusterThreshold_L1
change is decoupled from the ChannelThreshold
change. The former is driven by an actual change in the detector (replace pixel L1) while the latter is fixing a historical oversight where the HLT and offline were not using the same ChannelThreshold
value.
which parts of these changes should be backported to 12.0.x ? |
Please note that this PR should be merged at the same time as #35570 , to make sure the GPU customisation of the HLT remains coherent with the changes introduced here. |
Good question. Danek originally indicated no backports are needed for the Are we even formally allowed to backport these changes as they would modify the local reco in a closed release? The impact on the high-level quantities should be tiny, though. |
Good point - let's keep this only in 12.1.x then. |
+1
|
PR description:
Increase the SiPixel L1 cluster threshold from 2000 to 4000e making it the same as all other layers.
With the new L1 detector the lower thresholds should not be needed anymore as there is a clear separation between real clusters and junk (see the attached plot). The change will affect the cluster charge distribution for L1, the lower edge will shift from 2000
to 4000e.
In addition, the PR sets the
SiPixelClusterProducer
ChannelThreshold
at the HLT to 10 to make it in sync with the offline reconstruction.This is a resubmission of #35506 with the additional Run 3 modifiers for the GPU code and the related HLT modifiers.
PR validation:
Run RECO on raw data from the cosmic run 344420.
if this PR is a backport please specify the original PR and why you need to backport that PR:
No backport needed.
@dkotlins @mmusich