Closed sophiafarrell closed 3 years ago
thank you for catching this mistake. For >90% detection efficiency there is no difference, but who knows if we can maintain (like into G3 in the future) such high efficiencies. Therefore, it is important to do this right. The problem has been corrected
(Referencing https://github.com/NESTCollaboration/nest/commit/9363b9689d9fd7afaeef8cbf4178a0baeb2bcba9 so people can track the change). Thanks!
In the
NESTcalc::GetS1
function, there is a basic, no-timing block of code here: https://github.com/NESTCollaboration/nest/blob/3322903b7cd2439c349418ad25e6caeaa820acfe/src/NEST.cpp#L886-L891In these lines,
pulseArea
is smeared bysPEres * sqrt(Nphe)
where theNphe
is defined: https://github.com/NESTCollaboration/nest/blob/3322903b7cd2439c349418ad25e6caeaa820acfe/src/NEST.cpp#L886To my understanding, this slightly (very, very slightly) overestimates the smearing effect, but it should probably not be ignored. My suggestion would be to replace the linked lines above with something like this to make the
pulseArea
calculation more statistically accurate. But, perhaps I am missing something.This is in regards to the question I asked @mszydagis and then directed toward @riffard, but I figured that a git issue is more trackable for everyone. (Tagging @robertsjames here because he had the same question as well.)