Decayed Satellite Causing 100% Problems
Real time satellite tracking and orbit prediction
Status: Beta
Brought to you by:
csete
Menu
▾
▴
#50 Decayed Satellite Causing 100% Problems
28942 is causing the 100% cpu problems.
The .sat file read:
[Satellite]
VERSION=1.1
NAME=M-5 R/B
NICKNAME=M-5 R/B
TLE1=1 28942U 06005D 11033.50120833 .19493616 33309-5 18752-3 0 6294
TLE2=2 28942 98.0717 295.5466 0006060 191.0676 169.1534 16.51322780279437
SVN Commit 789 fixes the code getting stuck in a loop. A however follows.
The change pulls the orbit type checks into has_aos as everyplace has_aos was used the orbit types were checked. It also uses calls to decayed(sat) instead of static call to sat->otype.
Problems that arose is that the map module plotted both the satellite and the ground track for the decayed satellite. The ground track issue has been resolved by limiting the points plotted. The satellite still shows. (An interesting visual effect is that the footprint disappears with time as the orbit keeps getting lower.) This will take a little time as the map module assumes that a satellite always exists and therefore there is no code to remove the objects associated with a satellite.
Additionally, there has been no testing on what happens when a satellite decays during an observable pass.