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

Adds Meeus #114

Merged
merged 13 commits into from
Apr 19, 2017
Merged

Adds Meeus #114

merged 13 commits into from
Apr 19, 2017

Conversation

ChristopherRabotin
Copy link
Owner

WARNING: Meeus does not seem to be in the same frame as what SPICE returns. The Meeus results were compared with those emanating from a Matlab script, and they match (I should probably add those to the tests actually).

However, one should not use this implementation of the Meeus algorithms for perturbation: I surely have a frame issue somewhere which leads to the propagated state being very different from the truth.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.4%) to 74.631% when pulling 7a34f08 on issue-113 into 190acf6 on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.4%) to 74.623% when pulling bec09f9 on issue-113 into 190acf6 on master.

…ous set and this, but now I cannot invert R after 10 predictions.

Same issue happens with a local copy of the code and binary. I can only suspect it's an ephemeride issue, but I really don't know WTF is going on.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.2%) to 74.482% when pulling e662fb7 on issue-113 into 190acf6 on master.

…e RMS are still horribly large (6 million km in position). I'll try to switch to a CKF but I don't expect this to be any better, the issue must lie in my dynamics
… to Prof. McMahon, the issue may very well be a case of garbage in and garbage out:

StatOD is very sensitive to small changes (e.g. going from the de431 to de430 SPICE kernel would break things). Therefore trying to re-fit Meeus into my code designed around and for the SPICE frames is problematic at best.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.4%) to 74.658% when pulling 3fa2215 on issue-113 into 190acf6 on master.

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.

None yet

2 participants