Skip to content
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

pycbc_inspiral backend test in CI #4859

Open
GarethCabournDavies opened this issue Aug 29, 2024 · 0 comments
Open

pycbc_inspiral backend test in CI #4859

GarethCabournDavies opened this issue Aug 29, 2024 · 0 comments

Comments

@GarethCabournDavies
Copy link
Contributor

(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:

  1. Check that all FFT backends work
  2. 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?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant