Skip to content

Lunar calculations not yet supported #35

Closed

Description

@bmorris3

We need an astropy issue to be addressed, which is currently being addressed by @eteq, before we can move forward on the moon phase, illumination, position calculations.

Once this issue has been addressed, we can bring in this jplephem implementation of get_moon from this toy notebook.

Activity

  1. added this to the milestone on Jul 21, 2015
  2. cdeil commented on Jul 21, 2015

    @cdeil
    Member

    I've put "whishlist" as milestone for this.
    Probably we want astroplan 0.1 to work with astropy 1.0 and then only require astropy 1.1. later?

  3. eteq commented on Jul 21, 2015

    @eteq
    Member

    The issue @bmorris3 linked to here actually is not a show-stopper and can be worked around in astroplan... but there's another issue (not yet in the astropy issue tracker because I'm still determining it's exact nature) that will be harder to work around from the outside. So for that issue I agree we'll need to think about how to match astroplan to astropy versions. It may not be an issue if the fix ends up in a bug fix release (i.e. astropy 1.0.4) because then we can just require that.

  4. bsipocz commented on May 14, 2016

    @bsipocz
    Member

    Since astropy/astropy#4890 is merged this can be closed I think.

  5. bmorris3 commented on May 15, 2016

    @bmorris3
    ContributorAuthor

    This one can be closed when we actually implement the lunar features moon_altaz, MoonSeparationConstraint, etc using astropy rather than PyEphem.

  6. bmorris3 commented on Aug 4, 2016

    @bmorris3
    ContributorAuthor

    This is closed by #167.

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

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions