-
Notifications
You must be signed in to change notification settings - Fork 31
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
Update test_nirspec.py #255
Comments
I created a branch to test option 1 above on my personal fork. The two tests that were failing now pass, but two different ones now fail:
So it's not quite the quick fix we were hoping for, as far as getting a new release out. |
Tried the quick and dirty fix again and it works. I may just have been more careful in other steps this time: ========================================================= test session starts ========================================================== test_aperture.py::test_idl_to_tel PASSED [ 3%] ========================================================= 32 passed in 30.31s ========================================================== |
After importing a PRD with the recent NRS SIAF changes, test_nirspec.py fails two transform tests:
======================================================= short test summary info ======================================================== FAILED test_nirspec.py::test_nirspec_aperture_transforms - assert 0.27277224621730056 < 0.2 FAILED test_nirspec.py::test_nirspec_slit_transformations - assert 0.27277224621730056 < 0.1 ==================================================== 2 failed, 30 passed in 25.56s =====================================================
@charlesrp provided the following explanation:
So we have two options on how to proceed and be able to do valid releases of pysiaf:
1 is obviously not great, but will allow us to get the new release out for NIRCam and MIRI. 2 has a lot more risks, in that Tracy is probably extremely busy, may need more time to test her changes, and will probably want some help creating the PR.
Even if we do decide to do option 1, we need option 2 before the end of commissioning.
The text was updated successfully, but these errors were encountered: