Skip to content
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

Update ZDC LYSO Pedestal Sigma Parameter #1541

Closed
wants to merge 5 commits into from
Closed
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/detectors/ZDC/ZDC.cc
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ extern "C" {
.capADC = 32768,
.dyRangeADC = 2000 * dd4hep::MeV,
.pedMeanADC = 400,
.pedSigmaADC = 3.2,
.pedSigmaADC = 0.2,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Basically, here you claim that 15-bit ADC can not resolve your pedestal. That is unrealistic.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The current parameters cause issues for O(5-10 MeV) photons. 5-10 MeV photons may be a reasonable lower limit target for the LYSO.

We do not have expected noise estimates yet. But the current version has a threshold cut at 4*3.2 = 12.8 ADC channels, which is a deposited energy per tower of about 0.8 MeV. For LYSO, a 0.8 MeV deposit corresponds to a light yield of about 25,000 photons.

If we don't want to decrease to pedestal width from 3.2 ADC channels, we maybe can decrease the dynamic range of the LYSO from the current 2 GeV value.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The current numbers should have been implemented following request of the Simulation group to DSC's. Ideally, the simulations reflect performance of the detector as can be constructed, not performance that is desired. Is it possible to get these updated parameters endorsed by DSCs?

My original comment about ADC is not meant to imply that ADC noise defines the floor, but to point out that ballpark numbers aren't feasible and that one could seek for a higher resolution ADC if the noise is less than one unit. Reducing dynamic range will not help for noise defined by the sensor.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good. Thanks. We'll chat with the DSC about the parameter values.

.resolutionTDC = 10 * dd4hep::picosecond,
.corrMeanScale = "1.0",
.readout = "EcalFarForwardZDCHits",
Expand All @@ -46,7 +46,7 @@ extern "C" {
.capADC = 32768,
.dyRangeADC = 2000. * dd4hep::MeV,
.pedMeanADC = 400,
.pedSigmaADC = 3.2,
.pedSigmaADC = 0.2,
.resolutionTDC = 10 * dd4hep::picosecond,
.thresholdFactor = 4.0,
.thresholdValue = 0.0,
Expand All @@ -67,7 +67,7 @@ extern "C" {
.dimScaledLocalDistXY = {50.0*dd4hep::mm, 50.0*dd4hep::mm},
.splitCluster = true,
.minClusterHitEdep = 0.1 * dd4hep::MeV,
.minClusterCenterEdep = 3.0 * dd4hep::MeV,
.minClusterCenterEdep = 1.0 * dd4hep::MeV,
.transverseEnergyProfileMetric = "globalDistEtaPhi",
.transverseEnergyProfileScale = 1.,
},
Expand Down
Loading