orbital icon indicating copy to clipboard operation
orbital copied to clipboard

Allow different gravity model when parsing TLEs

Open fbender opened this issue 8 years ago • 4 comments

I'd like to use a more recent gravity model than the default one. Here's one trivial proposal, which enables passing any namedtuple with the same entries as the ones provided by SGP4, so you could basically hack together your own model. Long-term, this could probably be based on the body parameter.

Speaking of which, I've never seen anything besides Earth satellites being defined by TLEs, so the body should probably default to earth.

fbender avatar Sep 08 '16 20:09 fbender

You're right, there should be a way to specify this. Saying that, the difference between wgs72 and wgs84 at epoch are on the order of 10 metres which is much less than the uncertainty in the TLE itself (which I mention since with this module we're just getting a mean keplerian orbit from the TLE).

I would merge the PR if you default the new parameter to None with the current behaviour, and document that an EarthGravity tuple from sgp4.earth_gravity can be passed to override the default bevahiour.

In case you're interested, the intent was for python-astrodynamics/astrodynamics to be able to do what orbital can do and more; but development has slowed. I put up an initial proposal I had about wrapping SGP4, but states/orbits still haven't been implemented.

RazerM avatar Sep 08 '16 21:09 RazerM

Sure thing, will do!

document that an EarthGravity tuple from sgp4.earth_gravity can be passed to override the default bevahiour.

How/where should I do that? In the docstring? Or did I miss some other place?

fbender avatar Sep 09 '16 07:09 fbender

In case you're interested, the intent was for python-astrodynamics/astrodynamics to be able to do what orbital can do and more; but development has slowed. I put up an initial proposal I had about wrapping SGP4, but states/orbits still haven't been implemented.

Sounds good, I will definitely check it out! I do have some other stuff you might be interested in, but I need to check if I am allowed to publish it there. Another idea I had when looking at the orbital code was that it lacks a bit of separation. E.g. in my project I have my own orbit propagation method and am just intersted in the Keplerian Elements itself (derived from TLEs) without any extra functionality. Would be nice if astrodynamics would allow greater flexibility in choosing which functionality I'd like to use.

fbender avatar Sep 09 '16 07:09 fbender

How/where should I do that? In the docstring? Or did I miss some other place?

Yep, just the docstring.

RazerM avatar Sep 09 '16 07:09 RazerM