You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I agree that it is correct that we simulate the actual induced charge on the preamplifiers and it does e.g. influence the number of charges in the charge cloud, I think in many use-case scenarios it is an unnecessary complication to manually multiply the output waveform with the corresponding E_ionisation, to obtain a "calibrated" pulse. This could be integrated into SSD.
One solution would be introducing a keyword to the get_signals! function, e.g. calibrated = true.
Then SSD would return e.g. 100 keV pulse for a 100 keV energy deposition, while still handling things correctly under the hood.
An alternate name for the keyword could be unit = :energy or :charge, respectively. Thoughts?
The text was updated successfully, but these errors were encountered:
While I agree that it is correct that we simulate the actual induced charge on the preamplifiers and it does e.g. influence the number of charges in the charge cloud, I think in many use-case scenarios it is an unnecessary complication to manually multiply the output waveform with the corresponding
E_ionisation
, to obtain a "calibrated" pulse. This could be integrated into SSD.One solution would be introducing a keyword to the
get_signals!
function, e.g.calibrated = true
.Then SSD would return e.g. 100 keV pulse for a 100 keV energy deposition, while still handling things correctly under the hood.
An alternate name for the keyword could be
unit = :energy
or:charge
, respectively. Thoughts?The text was updated successfully, but these errors were encountered: