[AstroPy] Wrong earth mass in astropy.constants

Eric Winter ewinter at stsci.edu
Mon Nov 28 10:11:16 EST 2016

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).

Eric Winter

On 11/28/16, 7:09 AM, "AstroPy on behalf of Varun Bhalerao" <astropy-bounces at scipy.org on behalf of varunb at iucaa.in> wrote:

    But shouldn't the current version reflect latest value of constants, while versioning is being applied? It seems "current value is different from previous version" is lesser of a problem than "current value is different from current best accepted value"
    -- Varun
    -  Varun Bhalerao  -
    Office: A 214, IUCAA
    Ph: +91 20 2560 4214
    This email is encrypted and signed with OpenPGP.
    > On 28-Nov-2016, at 5:30 pm, astropy-request at scipy.org wrote:
    > Message: 1
    > Date: Sun, 27 Nov 2016 09:50:07 -0500
    > From: Pey Lian Lim <p3y1i4n at gmail.com>
    > To: astropy at scipy.org
    > Subject: [AstroPy]  Wrong earth mass in astropy.constants
    > Message-ID:
    > 	<CAJt49iR+F-9SNTJLBcxfgBWTVhH81oB8e1TYDhgVwhTvrPAMTA at mail.gmail.com>
    > Content-Type: text/plain; charset="utf-8"
    > Astropy is still undecided on exactly what is the best way to version
    > control constants. Please see https://github.com/astropy/astropy/issues/4958
    > .
    > -------------- next part --------------
    > An HTML attachment was scrubbed...
    > URL: <https://mail.scipy.org/pipermail/astropy/attachments/20161127/b0540f3c/attachment-0001.html>

More information about the AstroPy mailing list