Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow change of gravity model in Satrec
See original GitHub issueThe new Satrec class uses the WGS-72 gravity model:
There is some discussion in Vallado et al. “Revisiting Spacetrack Report #3: Rev 1” but I haven’t fully understood it yet. Do you have any supporting documentation that says that WGS-72 should always be used, or do you think it could be left as a parameter?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:10 (10 by maintainers)
Top Results From Across the Web
need a way to pass gravity model to TLE loader #544 - GitHub
I am loading a large TLE file using: satellites = load.tle_file(args.tle_catalog) But I want those satellites to use WGS84 gravity model for ...
Read more >Sensitivity of the Gravity Model and Orbital Frame for ... - MDPI
This paper describes the sensitivity of both the orbital frame domain selection and the gravity model on the performance of on-board real-time orbit ......
Read more >Sensitivity of the Gravity Model and Orbital Frame for ... - MDPI
Abstract: This paper describes the sensitivity of both the orbital frame domain selection and the gravity model on the performance of ...
Read more >Earth Satellites — Skyfield documentation - Rhodes Mill
Expect a satellite's orbit to constantly change as the SGP4 propagation routine models effects like atmospheric drag and the Moon's gravity.
Read more >sgp4 - PyPI
When the satellite record is initialized, your choice of gravity model results in a slate of eight constants being copied in: tumin —...
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 Free
Top 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
I know this is not a decision by consensus case, but as a 3rd party user of the API, I vote for allowing the option to change the gravity model.
I don’t think it’s a major complication to the API to make the gravity-constant a keyword argument to default to wgs72 to be consistent with the choice from the paper, and it allows people who have been using wgs84 to not worry about the implications of upgrading to the new API in order to take advantage of the speed-up and array functionality.
I have just released 2.5 that includes this improvement. Enjoy!