-
Notifications
You must be signed in to change notification settings - Fork 13
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
add EclipticCoords #46
Conversation
Codecov ReportBase: 91.52% // Head: 91.17% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #46 +/- ##
==========================================
- Coverage 91.52% 91.17% -0.35%
==========================================
Files 3 3
Lines 118 136 +18
==========================================
+ Hits 108 124 +16
- Misses 10 12 +2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Thanks, these changes look good to me at first glance! You'll need to do a rebase/merge of master- also feel free to bump the project to 1.2.0 (otherwise I will after merge).
I will take a look! |
@aplavin you should be able to add some tests for Ecliptic coordinates in the |
Thanks for setting tests up, @mileslucas! Currently, these ecliptic coords seem to be approximate: results are close to astropy (tests pass for 1e-3 tol), but not exactly equal. I guess some small extra rotation isn't accounted for... For me, ecliptic coords with this accuracy are fine. More precise conversion may require extra distinct types anyway, as astropy does: geo/helio/bary centric, mean/true. |
Needed ecliptic coordinates recently in my work, the basic implementation is straightforward.
No tests for now: could you please help with adding these coords to generated tables in
test/data
?