Mailman 3 নভেম্বর 2016 - AstroPy

Re: [AstroPy] Wrong earth mass in astropy.constants
by Varun Bhalerao 29 নভেম্বর, 2016

29 নভেম্বর, 2016

Thanks! 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 www.iucaa.in/~varunb This email is encrypted and signed with OpenPGP. > On 28-Nov-2016, at 5:30 pm, astropy-request(a)scipy.org wrote: > > Message: 1 > Date: Sun, 27 Nov 2016 09:50:07 -0500 > From: Pey Lian Lim <p3y1i4n(a)gmail.com> > To: astropy(a)scipy.org > Subject: [AstroPy] Wrong earth mass in astropy.constants > Message-ID: > <CAJt49iR+F-9SNTJLBcxfgBWTVhH81oB8e1TYDhgVwhTvrPAMTA(a)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 > . >

6 7

numpy.arange and quantities
by Ole Streicher 29 নভেম্বর, 2016

29 নভেম্বর, 2016

Hi, how can I create a sequence of quantities, when start, end, and step are given? The simplest approach doesn't work (astropy 1.2.1): >>> import numpy >>> import astropy.units as u >>> z0 = 0 >>> z1 = 9 * u.km >>> dz = 100 * u.m >>> r = numpy.arange(z0, z1, dz) Traceback (most recent call last): File "<stdin>", line 1, in <module> ValueError: setting an array element with a sequence. Best regards Ole

3 4

Wrong earth mass in astropy.constants
by Pey Lian Lim 27 নভেম্বর, 2016

27 নভেম্বর, 2016

Astropy is still undecided on exactly what is the best way to version control constants. Please see https://github.com/astropy/astropy/issues/4958 .

1 0

Wrong earth mass in astropy.constants
by Varun Bhalerao 27 নভেম্বর, 2016

27 নভেম্বর, 2016

Astropy.constants has the following value for earth mass: In [70]: const.M_earth Out[70]: <Constant name=u'Earth mass' value=5.9742e+24 uncertainty=5e+19 unit='kg' reference=u"Allen's Astrophysical Quantities 4th Ed."> Looking into Allen's, the reference is a 1992 book (Lerch, F.J. et al. 1992). This does not agree with the current value: 5.9722e24 +- 6e20 That value seems to come from a 2011 IAU publication: http://asa.usno.navy.mil/static/files/2016/Astronomical_Constants_2016.pdf (or even https://en.wikipedia.org/wiki/Earth_mass) The website of the IAU working group seems to be http://maia.usno.navy.mil/NSFA/NSFA_cbe.html - and there are even small differences in G, R_earth etc! Can the values be updated? Regards, -- Varun ____________________ - Varun Bhalerao - Office: A 214, IUCAA Ph: +91 20 2560 4214 www.iucaa.in/~varunb This email is encrypted and signed with OpenPGP.

1 0

Interested in Hosting Python in Astronomy 2018?
by Stuart Mumford 25 নভেম্বর, 2016

25 নভেম্বর, 2016

Hello all, I am chair of the SOC for Python in Astronomy 2017, which is scheduled for May 8-12 at the Lorentz Center in Leiden, the Netherlands http://openastronomy.org/pyastro/2017). I am getting in touch because we would like to start the process of choosing the 2018 venue as soon as possible and, ideally, announce the 2018 location at the upcoming 2017 conference. If you are interested in hosting the 2018 Python in Astronomy conference and have not already filled out our venue information form, please do so: https://goo.gl/forms/hWkoDPX8KWEwZGUQ2(Note: if you already filled in this form with 2017 in mind, you will be considered for 2018) The SOC for 2017 will shortlist some venues and be in touch. We also plan to talk to you or a representative of your venue at the 2017 conference and then announce the 2018 venue at the conference dinner. Thanks, Stuart Mumford, on behalf of the Python in Astronomy 2017 SOC.

1 0

Need some advise about inputting a old coordinate
by Paul Kuin 24 নভেম্বর, 2016

24 নভেম্বর, 2016

I have a coordinate ra, dec in (1900) which I assume is the B1900 equinox. If I put that in the SkyCoord call it does seem to default to ICRS. Its not FK4 or FK5, so how do I enter that coordinate? Can someone help me, please? What I did so far - things that work is when the frame is ICRS or FK4: pos = coordinates.SkyCoord(FK4(ra=Angle("5h11.5m"), dec=Angle("-71d46m")),) and p2000=pos.transform_to("icrs") with pos <SkyCoord (FK4: equinox=B1950.000, obstime=B1950.000): (ra, dec) in deg (77.875, -71.76666667)> and p2000 <SkyCoord (ICRS): (ra, dec) in deg (77.69083577, -71.70770648)> That all works but it is not a B1950 frame, unfortunately, but B1900. p1900 = coordinates.SkyCoord(ra=Angle("5h11.5m"), dec=Angle("-71d46m"),equinox=astropy.time.Time(2415020.3135,format="jd")) p1900 <SkyCoord (ICRS): (ra, dec) in deg (77.875, -71.76666667)> I hope I'm not too confusing, but it seems not possible. Any help is being appreciated! Cheers, Paul -- * * * * * * * * http://www.mssl.ucl.ac.uk/~npmk/ * * * * Dr. N.P.M. Kuin (n.kuin(a)ucl.ac.uk) phone +44-(0)1483 (prefix) -204111 (work) mobile +44(0)7908715953 skype ID: npkuin Mullard Space Science Laboratory – University College London – Holmbury St Mary – Dorking – Surrey RH5 6NT– U.K.

1 0

descriptive package descriptions?
by Peter Teuben 21 নভেম্বর, 2016

21 নভেম্বর, 2016

the one line packages descriptions, as for example seen on anaconda's https://anaconda.org/astropy/repo could use some cleanup/normalization. How are these generated? The astropy group could make them more coherent between them. I'm thinking of the unix man page description under the NAME field. A few are still labeled "No Summary", and my eye also caught an author's colorful opinion. The entry for "emcee" is labeled "kick ass blablabla". Perhaps cute in 2015. But I really object to putting an opinion in a searchable line like that. We should stick to facts. I'm not even sure how to measure kick-ass anyways. And how is one to trump that one, if one ever write one that actually runs in reasonable time There will be no end in sight in the language we'll have to use to describe codes. peter

3 2

Reminder: Python in Astronomy 2017 Deadline
by Stuart Mumford 19 নভেম্বর, 2016

19 নভেম্বর, 2016

Hello all, Applications for the Python in Astronomy 2017 conference (http://openastronomy.org/pyastro/2017/) are open until *December 9th*, 2016. The conference will be held on 8th - 12th May 2017 at the Lorentz Center in Leiden, the Netherlands. Please fill out this form <https://docs.google.com/forms/d/e/1FAIpQLSfFvzolQvW5PJRbgIoPs73t4LgMIDNX2lX…>to apply. The Python in Astronomy conferences aim to bring together a wide variety of people who currently use, develop or teach people about Python packages in the context of all forms of Astronomy. Participant selection will be made with the goal of growingthe Python in Astronomy community and we particularly encourage requests to attend from junior astronomers and people who are new to contributing to open source software. This conference is neither intended to be an introduction to Python bootcamp nor only for expert-level Python developers, but we do expect all participants to have at least a basic familiarity with Python. Please fill out the application and indicate the level of financial support you will likely require in order to attend. Once the participants have been selected, we’ll get back in touch with everyone about their specific financial support requirements. Stuart Mumford, SOC Chair Matt Craig Kelle Cruz Daniela Huppenkothen Abigail Stevens Erik Tollerud

1 0

Re: [AstroPy] Rotate an image and create new FITS header with updated astrometry
by Brigitta Sipocz 16 নভেম্বর, 2016

16 নভেম্বর, 2016

Hi Marcio, While it doesn't do exactly what you ask for, you may want to check out the affiliated package reproject (http://reproject.readthedocs.io/en/stable/). It does flux conserving image reprojection: http://reproject.readthedocs.io/en/stable/ Cheers, Brigitta On 15 November 2016 at 14:26, Marcio Melendez <marcio.melendez(a)gmail.com> wrote: > Hi all, > Is there a similar function to IDL's HROT in python, e.g., a function to > rotate an image and create a new FITS header with updated astrometry. > > Thanks! > > -- > Marcio B. Melendez, Ph.D > JWST ISIM Optics Support Scientist > KBRwyle Science, Technology and Engineering Group > NASA Goddard Space Flight Center Greenbelt, MD 20771 > Bldg. 29 Rm. T29-10, phone: 301-286-8517 > > _______________________________________________ > AstroPy mailing list > AstroPy(a)scipy.org > https://mail.scipy.org/mailman/listinfo/astropy > >

3 4

Re: [AstroPy] Rotate an image and create new FITS header with updated astrometry
by Marcio Melendez 16 নভেম্বর, 2016

16 নভেম্বর, 2016

Hi Peter, I use Montage mainly for display purpose, to get the correct sky orientation, but I have never used it to perform any operation. I see that there is a rotation utility, mRotate, but from the description "This module is meant for quick-look only; it is *not flux conserving*." which is not useful for what I need. Are there any other options? Thanks! On Tue, Nov 15, 2016 at 10:32 AM, Peter Teuben <teuben(a)astro.umd.edu> wrote: > the best is to use the python interface to montage. it's a contributed > package for astropy. > > > On 11/15/2016 09:26 AM, Marcio Melendez wrote: > > Hi all, > Is there a similar function to IDL's HROT in python, e.g., a function to > rotate an image and create a new FITS header with updated astrometry. > > Thanks! > > -- > Marcio B. Melendez, Ph.D > JWST ISIM Optics Support Scientist > KBRwyle Science, Technology and Engineering Group > NASA Goddard Space Flight Center Greenbelt, MD 20771 > Bldg. 29 Rm. T29-10, phone: 301-286-8517 > > > _______________________________________________ > AstroPy mailing listAstroPy@scipy.orghttps://mail.scipy.org/mailman/listinfo/astropy > > > > _______________________________________________ > AstroPy mailing list > AstroPy(a)scipy.org > https://mail.scipy.org/mailman/listinfo/astropy > > -- Marcio B. Melendez, Ph.D JWST ISIM Optics Support Scientist KBRwyle Science, Technology and Engineering Group NASA Goddard Space Flight Center Greenbelt, MD 20771 Bldg. 29 Rm. T29-10, phone: 301-286-8517

4 3