Runtime warning
See original GitHub issueHi, during the usage of skyfield 1.39 I get regular a runtime warning:
/Users/mw/PycharmProjects/Envs/mw4/lib/python3.8/site-packages/skyfield/functions.py:95: RuntimeWarning: invalid value encountered in double_scalars lon = arctan2(y, x) % tau
Does somebody has some hints where to look as it is am internal function and I use skyfield only from api level. Many thanks in advance, Michel
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
warnings — Warning control — Python 3.11.1 documentation
Source code: Lib/warnings.py Warning messages are typically issued in situations where it is ... Base category for warnings about dubious runtime features.
Read more >How do I block python RuntimeWarning from printing to the ...
Every time I run the code it raises a RuntimeWarning . I know what's causing the warning, it's intentional, and it doesn't affect...
Read more >Unobtrusive runtime warnings for libraries - Point-Free
Runtime warnings in libraries are a great way to notify your users that something unexpected has happened, or that an API is being...
Read more >How to Fix: RuntimeWarning: overflow encountered in exp
This warning occurs when you use the NumPy exp function, but use a value that is too large for it to handle. It's...
Read more >How to Fix: RuntimeWarning: Overflow encountered in exp
This warning occurs because the maximum size of data that can be used in NumPy is float64 whose maximum range is 1.7976931348623157e+308. Upon ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m working on that. Your idea checking the tEnd might have helped. We both observed a satellite problem:
So your chart showed the crash of one of these satellites.
I’m glad that we at least worked out why the search routine wasn’t working! The next time I’m in that code, I’ll try to remember the NaN position, and see whether the search routine maybe could fail with a more informative error message if it’s given NaN coordinates to work with.
In the meantime, I hope you have success getting your satellite routines armored against this failure mode!