Something went wrong on our end
Function get_nearest_time() behaves as expected now
Merged
requested to merge ghsc/users/erigler/geomag-algorithms:fix-FilterAlgorithm-get_nearest_time into master
All threads resolved!
Compare changes
- Erin (Josh) Rigler authored
The previous unit test relied on broken behavior of get_nearest_time() to pass. With get_nearest_time() fixed, the unit test needed to be updated accordingly.
@@ -313,7 +313,7 @@ def test_get_nearest__oneday_average():