<div dir="ltr">The main problem we are facing in Astropy is that if we update constants from one release to the next, results might then change, which might not be acceptable for some users. Therefore, we need to make sure we have a mechanism for users to import a 'fixed/frozen' version of constants that will not change in future releases of Astropy, and this is why there are delays currently in updating some of the constants.<div><br></div><div>Cheers,</div><div>Tom<br><div><div><br></div><div><br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 28 November 2016 at 15:20, Eric Jensen <span dir="ltr"><<a href="mailto:ejensen1@swarthmore.edu" target="_blank">ejensen1@swarthmore.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The IAU passed a resolution relatively recently addressing exactly this problem, and recommending standard values, while acknowledging that best estimates might continue to diverge slightly from these. So it seems like these IAU standard values would be a good option to consider for use in astropy:<br>
<br>
<a href="https://arxiv.org/abs/1510.07674" rel="noreferrer" target="_blank">https://arxiv.org/abs/1510.<wbr>07674</a><br>
<br>
Resolution B3 here:<br>
<br>
<a href="https://www.iau.org/static/resolutions/IAU2015_English.pdf" rel="noreferrer" target="_blank">https://www.iau.org/static/<wbr>resolutions/IAU2015_English.<wbr>pdf</a><br>
<span class="HOEnZb"><font color="#888888"><br>
Eric<br>
</font></span><span class="im HOEnZb"><br>
> On Nov 28, 2016, at 10:11 AM, Eric Winter <<a href="mailto:ewinter@stsci.edu">ewinter@stsci.edu</a>> wrote:<br>
><br>
> Therein lies the problem – who decides on the “best accepted value”? My initial thought would be to use values of constants defined by appropriate authorities, such as NASA, AAS, or IAU. But those values will always (and with good reason) lag behind the “latest value”. I think (this is just IMHO, of course) that official, vetted and reviewed values from trusted authorities should be used for AstroPy – and only such values. If a given user needs a more recent value, they can simply override it in their own code (and document said change, of course).<br>
><br>
> FWIW<br>
> Eric Winter<br>
<br>
</span><div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
AstroPy mailing list<br>
<a href="mailto:AstroPy@scipy.org">AstroPy@scipy.org</a><br>
<a href="https://mail.scipy.org/mailman/listinfo/astropy" rel="noreferrer" target="_blank">https://mail.scipy.org/<wbr>mailman/listinfo/astropy</a><br>
</div></div></blockquote></div><br></div>