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
I don't think this exists, but I think that we should have a CI test for which pycbc_inspiral (and possibly others) run on the same data using different FFT backends, maybe on the CPU and GPU artchitecture as well, and check that output is comparable. My thinking is:
Check that all FFT backends work
Check that we don't introduce bugs(features) which don't(only) affect the path but not(only) on the one which is being tested by the CI
The outputs won't be the same due to the way the FFT libraries work, so:
tolerances will need to be defined with careful consideration
Is there a way that these could be forced to be identical?
The text was updated successfully, but these errors were encountered:
(partly just thinking out loud)
I don't think this exists, but I think that we should have a CI test for which pycbc_inspiral (and possibly others) run on the same data using different FFT backends, maybe on the CPU and GPU artchitecture as well, and check that output is comparable. My thinking is:
The outputs won't be the same due to the way the FFT libraries work, so:
The text was updated successfully, but these errors were encountered: