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
The test jwst/coron/tests/test_coron.py::test_align_array started showing
AssertionError: Not equal to tolerance rtol=1e-07, atol=1e-06 a few days ago when GitHub Actions runs the unit test suite for MacOS py311.
The differences are pretty small: Max absolute difference: 9.8773848e-06, Max relative difference: 4.67009943e-05. However, it would be good to figure out why this happened (e.g., a numpy/scipy release) and ensure that there are no qualitative differences to worry about here before simply increasing the tolerances.
The text was updated successfully, but these errors were encountered:
The differences from the leastsq fit are relatively small. However the tolerances for the test had to be raised considerably (see #8439) due to how the test is calculated.
I had some hope that scipy dev fixed this (as there were other leastsq issues). However the last time I checked (sometime last week) the nightly version still caused this test to fail.
Issue JP-3614 was created on JIRA by Ned Molter:
The test jwst/coron/tests/test_coron.py::test_align_array started showing
AssertionError: Not equal to tolerance rtol=1e-07, atol=1e-06 a few days ago when GitHub Actions runs the unit test suite for MacOS py311.
The differences are pretty small: Max absolute difference: 9.8773848e-06, Max relative difference: 4.67009943e-05. However, it would be good to figure out why this happened (e.g., a numpy/scipy release) and ensure that there are no qualitative differences to worry about here before simply increasing the tolerances.
The text was updated successfully, but these errors were encountered: