Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Base staleness check on TLE Epoch instead of wall clock #63

Merged
merged 6 commits into from
Apr 23, 2024

Conversation

jerematt
Copy link
Collaborator

@jerematt jerematt commented Apr 23, 2024

PR based almost entirely on #46, but adding some unit tests to verify the new functionality.

Closes #45

Thank you @miketwo for the original Issue, PR and changes.

Updates the quick_predict function to use the TLE's epoch for checking if the TLE is too stale,
rather than the current system time, allowing for predictions of TLE's older than a year, if
the prediction time is within a year of the TLE's epoch.

Also removes the now unused Daynum2String function and frozen time debug features.
@jerematt jerematt requested a review from mattmolo as a code owner April 23, 2024 19:21
@jerematt jerematt merged commit 939df92 into master Apr 23, 2024
7 checks passed
@jerematt jerematt deleted the jm-staleness-check branch April 23, 2024 19:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PredictException: time XXX too far from present should use TLE Epoch
2 participants