Closed leblancfg closed 7 years ago
Unless I am mistaken, the TEME and ITRF reference frames do not rotate at exactly the same rate, so a velocity expressed with respect to them will indeed usually have a different magnitude in each.
Could you double-check me on this? Open the official PDF on the SGP4 algorithm:
http://ww.celestrak.com/publications/AIAA/2006-6753/AIAA-2006-6753-Rev2.pdf
And compute the magnitude of the vectors vTEME and vITRF there in the official example from the publication. I get different magnitudes:
In [7]: np.linalg.norm([-4.746131487, 0.785818041, 5.531931288])
Out[7]: 7.3311348276107466
In [8]: np.linalg.norm([-3.225636520, -2.872451450, +5.531924446])
Out[8]: 7.0183969941872917
Do you get the same result?
That makes sense, and I confirm I get the same numbers.
Thank you very much for looking into it; I never would have figured that out by myself. I had dismissed the Earth's rotation (0.45 km/s at the equator vs. the ~0.08 km/s discrepancy) as the source of "error", and still don't quite understand how that number shows up. But it does go to show how little I know about coordinate systems and their conversions :expressionless:
Not sure if it's the
TEME_to_ITRF
coordinate conversion method that's causing the issue, but I get different magnitudes (~1%) for thevTEME
andvITRF
velocity vectors -- but not for the altitude!Will need to investigate that method further, but wanted to bring it up first. Seems related to the fact that the method takes units per day, not per second.
Returns