-
Notifications
You must be signed in to change notification settings - Fork 190
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
Matched filtering with both peak signs simultaneously #2914
Matched filtering with both peak signs simultaneously #2914
Conversation
for more information, see https://pre-commit.ci
…ace into mf_with_both_peak_signs
for more information, see https://pre-commit.ci
This PR should not be merged as it is, because even if this is working without error, the behavior is strange. I suspect that, in the numba kernel, there is a corner case as mentioned by @samuelgarcia that wrote it with inequalities, such that if templates are at the same spot, we are keeping all peaks. Currently, if only neg or pos is selected for the peak type, this is working fine. But with both, we have way too many peaks detected.... |
@samuelgarcia I've found the bug and I've patched it. This is maybe too late for the release, but since it was tagged at some point. Now this branch is working as expected! |
… into mf_with_both_peak_signs
…mf_with_both_peak_signs
for more information, see https://pre-commit.ci
@samuelgarcia I've added the optimisation we discussed for convolution in this PR, and this is ready to go on my side |
Bien joué. |
This PR should allow matched filtering to work with both positive and negative peak sign detection. If both is selected, then templates are duplicated with a sign inversion, and added to the dictionary of templates.
I've also added a drastic speed up of the function, by simplification of the convolution