-
Notifications
You must be signed in to change notification settings - Fork 6
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
TST: specialized OMNI HRO routines need testing #34
Comments
Need to evaluate the usage of these routines before writing tests |
Notes on usage of |
@aburrell, do we want to maintain support for older scipy? pysatNASA/pysatNASA/instruments/methods/omni.py Lines 140 to 150 in d5cf79a
scipy 1.4 was released in 2019. I think we could add a limit and drop this. Not sure how we would test for this otherwise |
Also, I don't see how to trigger the following lines without also creating a valueError later on due to non-integer windows. Is this the intended behaviour? pysatNASA/pysatNASA/instruments/methods/omni.py Lines 114 to 120 in d5cf79a
|
I think dropping the older scipy is fine. Maybe change lines 114-120 to just raise an earlier ValueError, or adjust the input to prevent the ValueError from happening. |
The valueError comes directly from pandas when the rolling routines are invoked |
Turns out it was a bug! 🐞 |
time_shift_to_magnetic_poles
calculate_imf_steadiness
(w/ custommax_wnum
)calculate_imf_steadiness
calculate_dayside_reconnection
calculate_clock_angle
The text was updated successfully, but these errors were encountered: