Improper ingestion of TLEs with spaces padding epoch
Real time satellite tracking and orbit prediction
Status: Beta
Brought to you by:
csete
Fields in a TLE may be left-padded with either zeros or spaces [1].
In the following TLE, the epoch is the 92nd Julian day of 2014.
0 Flock1-15 0721 1 90115U 98067DS 14 92.08870996 .00166554 00000-0 17775-2 0 1391 2 90115 051.6455 115.1973 0007045 034.4456 325.6785 15.62888609 02
Convert_Satellite_Data in sgp_in.c tries to treat the two fields 'epoch year' and 'epoch (fractional) day' as a single double, i.e. it calls g_ascii_strtod on "14 92.08870996".
This causes a bogus epoch, so the propagated orbit has decayed, resulting in 100% CPU, crashes, wildly erratic orbit etc.
The attached patch fixes it by inserting zeros if needed prior to calling g_ascii_strtod.
[1] http://celestrak.com/columns/v04n03/ "In other words, an epoch can be represented as either 98001.12345678 or 98 1.12345678"
Hi Henry,
Thanks for the patch and sorry for the late reply. Your patch will be applied.
Alex
Thanks for the fix. The patch has been applied.
Thanks Alex!