-
Notifications
You must be signed in to change notification settings - Fork 356
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
Try to fix test_skymax on Numpy 2 #4991
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test is not worth having the test suite failing over, so I approve any patch that just gets this working again.
It's possible dynamic range stuff will make the simple fix not work unless dynamic range is applied.
It might also make more sense to just cast to complex64 at the 3 lines where we do load_frequencyseries
Looks like I need to tell |
The inspiral example is also failing:
@GarethCabournDavies I think this is what you were describing on Slack? If you have a fix, could you push it here? |
The decompress block of code is more important than the skymax test code ... We should check whether a copy should be being done there. |
This is Gareth's proposed fix. I think there are optimization improvement possibilities, but the *real* fix is not to generate compressed waveforms with different precision to what you will use when decompressing.
I applied Gareth's proposed fix here |
This is an attempt at fixing #4990.
I am assuming
compute_max_snr_over_sky_loc_stat()
wants the input arrays to be in single precision for speed/memory considerations.In my local tests, this will still fail because the results differ from the expected values by 1e-6 or less, so we may have to update the reference values.