Skip to content

Ecliptic coordinates missing #1430

Closed

Description

@mperrin

The astropy.coordinates package does not yet support transformation to or from ecliptic coordinates. While the ecliptic is a bit of a slippery concept at very high precision, it's nonetheless frequently seen and often useful, so I think it makes sense for astropy to support it.

I may be able to assist with an implementation myself (though am ludicrously overcommitted at the moment, so no promises) but in any case I wanted to ask raise this issue so others working on coordinates can comment.

Activity

  1. embray commented on Sep 10, 2013

    @embray
    Member

    Last I saw this discussed I know there were plans to add it, but there were some other intermediate steps that needed to be completed first. I don't really know too much about it though.

  2. astrofrog commented on Sep 12, 2013

    @astrofrog
    Member

    I know @eteq is working on refactoring some aspects of astropy.coordinates but I'm not sure what the status is and whether he is planning to add support for ecliptic or alt/az conversions yet, so any help will likely be welcome.

  3. eteq commented on Sep 12, 2013

    @eteq
    Member

    Ecliptic is indeed first on the list of coordinate systems to add after the IAU2000 stack to get from ICRS to Alt/Az. The main catch I see in that is exactly as you said, @mperrin - deciding on which definition we want for what ecliptic actually means and fitting it into the IAU2000 scheme.

    The implementation catch is that it would be unwise to do this before coordinates have been made array-compatible (currently in-progress on a branch of mine), as it has required some changes to how transformations are defined (that's mainly what's taking it a while to get done). So perhaps we should revisit this subject as soon as that is done?

  4. mhvk commented on Sep 13, 2013

    @mhvk
    Contributor

    @eteq -- off-topic, but as you mention Alt/Az: it would be lovely to have that working, and if you want to go the full monkey in term of precision, I'm happy to help with getting Earth-orientation parameters out of IERS (#1145); of course also having sidereal time should help (#1418) -- I think we have enough to make this good at the pulsar timing level; with a bit more effort, perhaps even at that required for VLBI.

  5. mtbannister commented on Sep 20, 2013

    @mtbannister

    I'd love to see ecliptic coordinates supported; the solar system community aren't going to be keen on astropy.coordinates until that exists. Having a transform to the invariant plane would be a handy addition as well.

  6. eteq commented on Sep 25, 2013

    @eteq
    Member

    @mhvk - I like that as a goal (pulsar timing at least, with VLBI even better). It's possible some subtle implementation issues will come up to make this difficult, but until we know that, we'll say that's the target!

    @mtbannister -good to know this would indeed. Once arrayification is in and the baseline ICRS <-> Alt/Az is going, I may well ping you for feedback/implementation assistance.

  7. mtbannister commented on Sep 25, 2013

    @mtbannister

    @eteq I'd be happy to help. Once the coords exist, it'll get immediate implementation over in astroquery (cf. astropy/astroquery#222).

  8. modified the milestones: v1.0.0, v0.4.0 on May 3, 2014
  9. astrofrog commented on Jan 14, 2015

    @astrofrog
    Member

    This is not going to happen for 1.0 so removing the milestone.

    @mtbannister - I'm not sure if you are still interested in helping with this, but if so, do get in touch with @eteq as he will be able to provide information on what needs doing.

  10. removed this from the v1.0.0 milestone on Jan 14, 2015
  11. mtbannister commented on Jan 14, 2015

    @mtbannister

    Cheers @astrofrog. @eteq, @ijiraq has also mentioned he would be interested in helping with this issue.

  12. astrofrog commented on Jan 15, 2015

    @astrofrog
    Member
  13. eteq commented on Jan 22, 2015

    @eteq
    Member

    @mtbannister, @ijiraq - if you want some ideas on how to most easily implement this with the frames added in astropy v1.0, I suggest you check out http://www.iausofa.org/2013_1202_C/sofa/sofa_pn.pdf, particularly the diagram on page 6. (note that v1.0 uses only the "right side" of that transformation, through CIRS). Depending on exactly how you're meaning to define ecliptic, a few options present themselves:

    1. start from GCRS if you want a geocentric ecliptic system, using astropy._erfa.epv00 to get the sun->earth or bary->earth vector
    2. start from ICRS if you want a bary- or heliocentric ecliptic system, using astropy._erfa.epv00 to get the sun->earth vector and/or the bary->sun vector
    3. implement transforms from the "left side" of that diagram to use the "traditional" earth equinox-based approach.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions