-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
Virtual Packet Cutoff during Montecarlo #654
Comments
This small change results in bins with actual neglegible data being zero instead of having very small contributions. Fixes: tardis-sn#654
Do we still need this? I agree conceptually with you that setting the weight or energy of the packet to 0 is the cleaner approach to discard virtual packets. However, I am wondering about cases where fluctuations in these parts of the spectrum ever become relevant. |
The current implementation creates three possible 'states' for a bin. It's either zero meaning no packet at all, ~1e-100 meaning only discarded packets registered for the bin or it has an actual value. There are two cases where this issue was relevant in the past.
As the fix is easy, quick and has no bad side effects that I know of the important question that needs to be answered should be "Why shouldn't we merge this?" instead of "Why should we merge this?" |
Fine - I'd be in favour of merging. |
Will be dealt with once the testing framework is fully operational |
@wkerzendorf, @yeganer - thoughts on this? Should we merge this. Will require an update of reference data. |
Solved with merge of #911 . |
In the montecarlo simulation there's a cutoff for virtual packets which boils down to:
This removes the contribution of weakly contributing packets almost completely (
exp(-100) ~ 1e-44
).But because this isn't exactly 0 the packet will still register and add to the bin. If the packet is the only packet in that bin the resulting luminosity will be very small and numerical problems can surface when comparing different bins.
The solution I propose is to either set the
weight
or theenergy
of the packet to0
. This removes any contribution and even allows small performance improvements by skipping the spectrum update(which needs to be atomic)The text was updated successfully, but these errors were encountered: