-
Notifications
You must be signed in to change notification settings - Fork 348
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
Change decisive to network optimal snr in foundmissed #4426
Conversation
@GarethCabournDavies I'm not sure I follow. This makes sense if you just look at singles, but coincs won't have the same detection threshold in terms of max SNR which blurs out the detection boundary. If we want comparable numbers, wouldn't network optimal SNR make more sense as a default? |
It does - I had thought that max_optimal_snr would be better, but trying to think of arguments why that was true convinced me that combined is better |
Noting that this requires a review to be merged. |
* Change decisive to max snr in foundmissed * Update plotting.ini
* Change decisive to max snr in foundmissed * Update plotting.ini
* Change decisive to max snr in foundmissed * Update plotting.ini
* Change decisive to max snr in foundmissed * Update plotting.ini
For a search including single-detector events, the decisive SNR for whether a signal is detected is actually the maximum SNR
See e.g. comment here