Memory issue with satellite.at()?
See original GitHub issueI have an application where I am trying to calculate the position of a satellite on a very fine time grid (say millions of points).
The simple call to
geocentric = satellite.at(t)
seems to run into performance issue, where for large n scales much worse than linearly, and by the time n is O(1 M) the thing is essentially requiring >10 GB or RAM and bringing my terminal down.
I can make a more detailed report, including all the related information, but I want to make a quick check first of whether I am doing something wrong and/or you have any immediate insight into this.
Thanks in advance!
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Satellite run out of memory or high swapping due to NIC updates
Issue. Satellite 6.8 or lower version, Passenger instance consumes high memory and triggers OOM killer or causing high swapping.
Read more >Memory usage has increased drastically · Issue #1791 - GitHub
I upgraded one of my production chains to use the latest Satpy, Pyresample and support libraries, and the chain ran out of memory....
Read more >Satellite 4090 on board the issue of RAM - eehelp.com
Satellite 4090 on board the issue of RAM. Hello. I have a S4090CDS/4.3 (PAS409EYV-EN9X,. It would seem that the RAM is faulty (boots...
Read more >Single-event upset - Wikipedia
A single-event upset (SEU), also known as a single-event error (SEE), is a change of state caused by one single ionizing particle (ions,...
Read more >EDAC software implementation to protect small satellites ...
One of the techniques to increase the reliability of memory chips and reduce transient errors and permanent faults is Error Detection and ...
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
Wow! The
t._nutation_angles = iau2000b(t.tt)
really saved my day.I haven’t made extensive tests, yet, but at the first glance the time/memory footprint is well below the level at which I would notice it.
I don’t know if mine is really a peculiar use case, but it might be worth noting this in the docs.
Thanks!
The new code has now been released in Skyfield 1.21. I’m going to close the issue for now, but please re-open if you run into further problems!