Skip to content

Additions/cleanup for 3.2 whatsnew - #8805

Merged
mhvk merged 5 commits into
astropy:masterfrom
eteq:more-whatsnew-3.2
Jun 10, 2019
Merged

mhvk merged 5 commits into
astropy:masterfrom
eteq:more-whatsnew-3.2

Conversation

@eteq

@eteq eteq commented Jun 6, 2019

Copy link
Copy Markdown
Member

This adds a section to the what's new about CODATA and does some other spiffification and cleanup. Still doesn't have the "but the numbers", but that's part of the release process in my mind (agree @bsipocz ?)

@eteq eteq added this to the v3.2 milestone Jun 6, 2019
@codecov

codecov Bot commented Jun 6, 2019 •

Copy link
Copy Markdown

Codecov Report

Merging #8805 into master will increase coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #8805      +/-   ##
==========================================
+ Coverage   86.99%   86.99%   +<.01%     
==========================================
  Files         400      400              
  Lines       59459    59460       +1     
  Branches     1100     1100              
==========================================
+ Hits        51724    51725       +1     
  Misses       7094     7094              
  Partials      641      641
Impacted Files Coverage Δ
astropy/utils/timer.py 100% <0%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 18b43dd...f6b22fd. Read the comment docs.

@bsipocz

bsipocz commented Jun 6, 2019

Copy link
Copy Markdown
Member

but that's part of the release process in my mind (agree @bsipocz ?)

I suppose it is.

Comment thread docs/whatsnew/3.2.rst Outdated
============================

The new redefinition of the SI system and its base units came into force on May
20, 2019. Accompanying that redefinition was a new set of physical constants

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Please change the middle-endian. Whether to stick with ISO 8601 (according to the astropy style guide to docs) or a more narrative "20 May 2019", I don't mind.

@mhvk mhvk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nitpick and other stuff from the peanut gallery...

Comment thread docs/whatsnew/3.2.rst

t = Time('J2018') + np.linspace(-1, 0, 1000)*u.year

bme_origin = BarycentricMeanEcliptic([0]*len(t)*u.deg, [0]*len(t)*u.deg, equinox=t)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Not directly relevant here, but should we consider the fact that we do not just broadcast the coordinates with the times a bug?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Good point. I was surprised by that, and just accepted it, but if it surprised me maybe I shouldn't have! Will make an issue.

Comment thread docs/whatsnew/3.2.rst Outdated
plt.plot(t.jyear, it.ra.wrap_at(180*u.deg).deg, label='BarycentricTrueEcliptic')

plt.xlabel('J-year')
plt.ylabel('ICRS R.A. of ecliptic origin')

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Only real comment: could you add "(degree)" so that the units are clear?
And maybe for x, "Julian year"

Comment thread docs/whatsnew/3.2.rst Outdated
im = bme_origin.transform_to(ICRS())
it = bte_origin.transform_to(ICRS())

plt.plot(t.jyear, im.ra.wrap_at(180*u.deg).deg, label='BarycentricMeanEcliptic')

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Maybe (to instill good habits, since we're showing the source):

from astropy.visualization import quantity_support

quantity_support()

at the top, and then here delete the .deg?

Pity we don't have time_support yet!

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Good point, and I figured I'd demo inferring the unit from the qunatity in the ylabel for good measure!

@eteq

eteq commented Jun 10, 2019

Copy link
Copy Markdown
Member Author

Thanks @mhvk and @bsipocz - I think I've addressed all of the suggestions!

@mhvk mhvk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looks good to me. Since already approved by @bsipocz as well, will merge.
(and good to raise an issue, indeed)

@mhvk
mhvk merged commit 1758c7d into astropy:master Jun 10, 2019
bsipocz pushed a commit that referenced this pull request Jun 10, 2019
Additions/cleanup for 3.2 whatsnew
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants