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
#10149 added the TEME frame, and included necessary unit tests. However, the tests are remote_data because that makes sense for the obvious uses cases for this frame (satellites). It's not a huge priority, but it would be a bit more robust (and make our coverage stats look better) if there were some tests for this frame that didn't require remote data.
This is quite a widespread problem, no? Many tests in the coordinates package are marked as remote_data, due to the need to query non-astropy-data for the UTC-UT1 conversion.
Provided this conversion was well tested elsewhere we could remove remote_data marks for many of these tests by manually setting delta_ut1_utc?
That said, it is no fun to mock, and I think it is part of a bigger problem of coordinates importing time causing IERS leap seconds table download. I can't seem to find that issue but I am pretty sure @mhvk knows which one. 😅
Activity
StuartLittlefair commentedon May 4, 2020
This is quite a widespread problem, no? Many tests in the coordinates package are marked as remote_data, due to the need to query non-astropy-data for the UTC-UT1 conversion.
Provided this conversion was well tested elsewhere we could remove remote_data marks for many of these tests by manually setting
delta_ut1_utc?pllim commentedon May 4, 2020
FWIW -- Yes, you can mock it to avoid internet connection.
pllim commentedon May 5, 2020
That said, it is no fun to mock, and I think it is part of a bigger problem of coordinates importing time causing IERS leap seconds table download. I can't seem to find that issue but I am pretty sure @mhvk knows which one. 😅