Skip to content

Conversation

@astrofrog
Copy link

@eteq @Cadair - let me know if you have any suggestions!

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the "in ... inside ..." construction here is a bit confusing. Perhaps "the actual coordinate data in astropy.coordinates frames is represented via..."?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

@eteq
Copy link
Owner

eteq commented May 19, 2014

A few minor suggestions/doctest-related tweaks above, and one here, but the content looks great, @astrofrog!

  • Anywhere that you're showing non-integer numbers, I suggest using something like <SphericalRepresentation lon=1.0303... rad, lat=0.6012... rad, distance=7.071... kpc> instead of <SphericalRepresentation lon=1.03037682652 rad, lat=0.601264216679 rad, distance=7.07106781187 kpc>. I've been finding in other coordinate docs that different versions of python/numpy have slightly different rounding behaviors (and presumably its even worse when you go to different architectures...).

@astrofrog
Copy link
Author

@eteq - I implemented the comments. For some reason I'm having issues running the doctests but should hopefully be ok.

@eteq
Copy link
Owner

eteq commented May 20, 2014

Yep, doctests now passing. Merging! Thanks @astrofrog

eteq added a commit that referenced this pull request May 20, 2014
@eteq eteq merged commit f25adbf into eteq:coordinates-docs-update-ape5 May 20, 2014
@astrofrog astrofrog deleted the coordinates-docs-representations branch July 5, 2016 15:45
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.

2 participants