Michael Kelley

@hhsieh00 FYI, readthedocs builds documentation on pull requests (see the "checks" below). For your convenience, the time and dynamics documentation are at: https://sbpy--394.org.readthedocs.build/en/394/sbpy/time.html https://sbpy--394.org.readthedocs.build/en/394/sbpy/dynamics.html

Closing in favor of #385

Hi, I had a discussion with Josef Durech at the ACM meeting last month, who is also interested in contributing to shape model work. This aspect of sbpy is, as...

I'm still happy to have this contribution, but we're going to make a release in the next week, so I will re-milestone this to v0.5.

Coverage reporting is nominally working elsewhere, so I'll close this.

I can confirm that it isn't working with those examples, but is working for Ceres. I've opened a help desk ticket on this.

They have fixed the issue upstream.

From my understanding of https://ssd-api.jpl.nasa.gov/doc/horizons.html#command the Horizons API only supports ephemerides/vectors/etc from single object queries. Wildcards and the like will return a list of object matches, essentially prompting the user...

And, here are some code examples that I am trying to design to: ```python Examples -------- Object specifications: >>> from astroquery.jplhorizons import Horizons2 >>> Horizons2.query_observer("Jupiter") >>> >>> Horizons2.query_observer("1", center="568") >>>...

Thanks, @bsipocz . I agree with all your points! I'll try `QTable` first.