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
To 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.)
The text was updated successfully, but these errors were encountered:
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
In the
NESTcalc::GetS1
function, there is a basic, no-timing block of code here:nest/src/NEST.cpp
Lines 886 to 891 in 3322903
In these lines,
pulseArea
is smeared bysPEres * sqrt(Nphe)
where theNphe
is defined:nest/src/NEST.cpp
Line 886 in 3322903
To 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.)
The text was updated successfully, but these errors were encountered: