From pdzwig at summaventures.com Wed Jan 8 18:53:44 2020 From: pdzwig at summaventures.com (Peter Dzwig) Date: Wed, 8 Jan 2020 23:53:44 +0000 Subject: [AstroPy] pyspeckit query Message-ID: <47a4ecca-5f11-43ee-e5a5-44b3d4a25b5a@summaventures.com> Does anyone know where I can get hold of the detailed formatting requirements of pyspeckit's (spec).measurements.lines? It seems to be rejecting some of *my* (I thought) fairly standard line-formatting for some reason. Thanks in advance if anyone is able to help, Peter Dzwig -- Dr. Peter Dzwig From teuben at astro.umd.edu Wed Jan 8 19:18:49 2020 From: teuben at astro.umd.edu (Peter Teuben) Date: Wed, 8 Jan 2020 19:18:49 -0500 Subject: [AstroPy] pyspeckit query In-Reply-To: <47a4ecca-5f11-43ee-e5a5-44b3d4a25b5a@summaventures.com> References: <47a4ecca-5f11-43ee-e5a5-44b3d4a25b5a@summaventures.com> Message-ID: <3c098dbe-ed1d-247e-56b1-20d7287f3162@astro.umd.edu> An example of a legal entry, and your entry would benefit the discussion. I can also imagine lots of other failure modes, for example line file (if that is what you use) in the wrong place. Is there an error message from pyspeckit??? grepping this through the code is another good strategy to find the culprit. another Peter. On 1/8/20 6:53 PM, Peter Dzwig wrote: > Does anyone know where I can get hold of the detailed formatting > requirements of pyspeckit's (spec).measurements.lines? It seems to be > rejecting some of *my* (I thought) fairly standard line-formatting for > some reason. > > Thanks in advance if anyone is able to help, > > Peter Dzwig From erik.tollerud at gmail.com Wed Jan 8 20:33:31 2020 From: erik.tollerud at gmail.com (Erik Tollerud) Date: Wed, 8 Jan 2020 15:33:31 -1000 Subject: [AstroPy] ANN: Astropy v4.0 released Message-ID: Dear colleagues, We are very happy to announce the v4.0 release of the Astropy package, a core Python package for Astronomy: http://www.astropy.org Astropy is a community-driven Python package intended to contain much of the core functionality and common tools needed for astronomy and astrophysics. It is part of the Astropy Project, which aims to foster an ecosystem of interoperable astronomy packages for Python. New and improved major functionality in this release includes: * Support for Planck 2018 Cosmological Parameters * Improved Consistency of Physical Constants and Units * Scientific enhancements to the Galactocentric Frame * New ymdhms Time Format * New Context Manager for plotting time values * Dynamic and improved handling of leap second * Major Improvements in Compatibility of Quantity Objects with NumPy Functions * Multiple interface improvements to WCSAxes * Fitting of WCS to Pairs of Pixel/World Coordinates * Support for WCS Transformations between Pixel and Time Values * Improvements to Folding for Time Series * New Table Methods and significant performance improvements for Tables * Improved downloading and caching of remote files In addition, hundreds of smaller improvements and fixes have been made. An overview of the changes is provided at: http://docs.astropy.org/en/stable/whatsnew/4.0.html The Astropy v4.0.x series now replaces v2.0.x as the long term support release, and will be supported until the end of 2021. Also note that the Astropy 4.x series only supports Python 3. Python 2 users can continue to use the 2.x series but as of now it is no longer supported (as Python 2 itself is no longer supported). For assistance converting Python 2 code to Python 3, see the Python 3 for scientists conversion guide. Instructions for installing Astropy are provided on our website, and extensive documentation can be found at: http://docs.astropy.org If you make use of the Anaconda Python Distribution, you can update to Astropy v4.0 with: conda update astropy Whereas if you usually use pip, you can do: pip install astropy --upgrade Please report any issues, or request new features via our GitHub repository: https://github.com/astropy/astropy/issues Over 350 developers have contributed code to Astropy so far, and you can find out more about the team behind Astropy here: http://www.astropy.org/team.html If you use Astropy directly for your work, or as a dependency to another package, please remember to acknowledgment it by citing the appropriate Astropy paper. For the most up-to-date suggestions, see the acknowledgement page, but as of this release the recommendation is: This research made use of Astropy, a community-developed core Python package for Astronomy (Astropy Collaboration, 2018). Special thanks to the coordinator for this release: Brigitta Sipocz. We hope that you enjoy using Astropy as much as we enjoyed developing it! Erik Tollerud, Tom Robitaille, Kelle Cruz, and Tom Aldcroft on behalf of The Astropy Collaboration https://www.astropy.org/announcements/release-4.0.html From adam.g.ginsburg at gmail.com Thu Jan 9 10:18:37 2020 From: adam.g.ginsburg at gmail.com (Adam Ginsburg) Date: Thu, 9 Jan 2020 10:18:37 -0500 Subject: [AstroPy] pyspeckit query In-Reply-To: <3c098dbe-ed1d-247e-56b1-20d7287f3162@astro.umd.edu> References: <47a4ecca-5f11-43ee-e5a5-44b3d4a25b5a@summaventures.com> <3c098dbe-ed1d-247e-56b1-20d7287f3162@astro.umd.edu> Message-ID: Hi Peters, That section of pyspeckit is under-documented. I can perhaps help figure out a problem if you describe your use case more directly, as Peter Teuben suggested. It would be best to continue this conversation via a github issue, which may bring other contributors into the discussion. On Wed, Jan 8, 2020 at 7:27 PM Peter Teuben wrote: > An example of a legal entry, and your entry would benefit the > discussion. I can also imagine lots of other failure modes, for example > line file (if that is what you use) in the wrong place. Is there an > error message from pyspeckit? grepping this through the code is > another good strategy to find the culprit. > > another Peter. > > On 1/8/20 6:53 PM, Peter Dzwig wrote: > > Does anyone know where I can get hold of the detailed formatting > > requirements of pyspeckit's (spec).measurements.lines? It seems to be > > rejecting some of *my* (I thought) fairly standard line-formatting for > > some reason. > > > > Thanks in advance if anyone is able to help, > > > > Peter Dzwig > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy > -- Adam Ginsburg Assistant Professor, Department of Astronomy University of Florida, Gainesville http://www.adamgginsburg.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From pdzwig at summaventures.com Thu Jan 9 12:25:00 2020 From: pdzwig at summaventures.com (Peter Dzwig) Date: Thu, 9 Jan 2020 17:25:00 +0000 Subject: [AstroPy] pyspeckit query In-Reply-To: References: <47a4ecca-5f11-43ee-e5a5-44b3d4a25b5a@summaventures.com> <3c098dbe-ed1d-247e-56b1-20d7287f3162@astro.umd.edu> Message-ID: Dear Peter and Adam, thank you very much for your response. As a first step, would you be happy to take this offline to avoid un-necessarily flooding the list? I am sure that some of the stuff would bore the list rigid! Regards, Peter On 09/01/2020 15:18, Adam Ginsburg wrote: > Hi Peters, > ? ? ?That section of pyspeckit is under-documented.? I can perhaps help > figure out a problem if you describe your use case more directly, as > Peter Teuben suggested.? It would be best to continue this conversation > via a github issue, which may bring other contributors into the discussion. > > On Wed, Jan 8, 2020 at 7:27 PM Peter Teuben > wrote: > > An example of a legal entry, and your entry would benefit the > discussion. I can also imagine lots of other failure modes, for example > line file (if that is what you use) in the wrong place. Is there an > error message from pyspeckit??? grepping this through the code is > another good strategy to find the culprit. > > another Peter. > > On 1/8/20 6:53 PM, Peter Dzwig wrote: > > Does anyone know where I can get hold of the detailed formatting > > requirements of pyspeckit's (spec).measurements.lines? It seems to be > > rejecting some of *my* (I thought) fairly standard line-formatting for > > some reason. > > > > Thanks in advance if anyone is able to help, > > > > Peter Dzwig > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy > > > > -- > Adam Ginsburg > Assistant Professor, Department of Astronomy > University of Florida, Gainesville > http://www.adamgginsburg.com/ > > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy > -- Dr. Peter Dzwig From teuben at astro.umd.edu Thu Jan 9 12:27:50 2020 From: teuben at astro.umd.edu (Peter Teuben) Date: Thu, 9 Jan 2020 12:27:50 -0500 Subject: [AstroPy] pyspeckit query In-Reply-To: References: <47a4ecca-5f11-43ee-e5a5-44b3d4a25b5a@summaventures.com> <3c098dbe-ed1d-247e-56b1-20d7287f3162@astro.umd.edu> Message-ID: I think Adam's suggestion is a good one:?? it would benefit everybody if you explain the problem in a git issue. even if it's a "pilot" error, this will benefit those looking at closed issues and how they got resolved. I've used pyspeckit a bit, but not the lines you are using. So this is new to me as well. p. On 1/9/20 12:25 PM, Peter Dzwig wrote: > Dear Peter and Adam, > > thank you very much for your response. As a first step, would you be > happy to take this offline to avoid un-necessarily flooding the list? I > am sure that some of the stuff would bore the list rigid! > > Regards, > > Peter > > On 09/01/2020 15:18, Adam Ginsburg wrote: >> Hi Peters, >> ? ? ?That section of pyspeckit is under-documented.? I can perhaps help >> figure out a problem if you describe your use case more directly, as >> Peter Teuben suggested.? It would be best to continue this conversation >> via a github issue, which may bring other contributors into the discussion. >> >> On Wed, Jan 8, 2020 at 7:27 PM Peter Teuben > > wrote: >> >> An example of a legal entry, and your entry would benefit the >> discussion. I can also imagine lots of other failure modes, for example >> line file (if that is what you use) in the wrong place. Is there an >> error message from pyspeckit??? grepping this through the code is >> another good strategy to find the culprit. >> >> another Peter. >> >> On 1/8/20 6:53 PM, Peter Dzwig wrote: >> > Does anyone know where I can get hold of the detailed formatting >> > requirements of pyspeckit's (spec).measurements.lines? It seems to be >> > rejecting some of *my* (I thought) fairly standard line-formatting for >> > some reason. >> > >> > Thanks in advance if anyone is able to help, >> > >> > Peter Dzwig >> _______________________________________________ >> AstroPy mailing list >> AstroPy at python.org >> https://mail.python.org/mailman/listinfo/astropy >> >> >> >> -- >> Adam Ginsburg >> Assistant Professor, Department of Astronomy >> University of Florida, Gainesville >> http://www.adamgginsburg.com/ >> >> _______________________________________________ >> AstroPy mailing list >> AstroPy at python.org >> https://mail.python.org/mailman/listinfo/astropy >> From pdzwig at summaventures.com Thu Jan 9 16:09:41 2020 From: pdzwig at summaventures.com (Peter Dzwig) Date: Thu, 9 Jan 2020 21:09:41 +0000 Subject: [AstroPy] pyspeckit query In-Reply-To: References: <47a4ecca-5f11-43ee-e5a5-44b3d4a25b5a@summaventures.com> <3c098dbe-ed1d-247e-56b1-20d7287f3162@astro.umd.edu> Message-ID: OK, I have added it as an issue on github as an outline only at this stage. I can supply the Jupyter notebook/source and the input file later if required. I suspect that the code is baulking at the MgII line for some reason, so let's start with that. See: https://github.com/pyspeckit/pyspeckit/issues/322 Peter On 09/01/2020 17:27, Peter Teuben wrote: > I think Adam's suggestion is a good one:?? it would benefit everybody if > you explain the problem in a git issue. even if it's a "pilot" error, > this will benefit those looking at closed issues and how they got > resolved. I've used pyspeckit a bit, but not the lines you are using. So > this is new to me as well. > > > p. > > On 1/9/20 12:25 PM, Peter Dzwig wrote: >> Dear Peter and Adam, >> >> thank you very much for your response. As a first step, would you be >> happy to take this offline to avoid un-necessarily flooding the list? I >> am sure that some of the stuff would bore the list rigid! >> >> Regards, >> >> Peter >> >> On 09/01/2020 15:18, Adam Ginsburg wrote: >>> Hi Peters, >>> ?? ? ?That section of pyspeckit is under-documented.? I can perhaps help >>> figure out a problem if you describe your use case more directly, as >>> Peter Teuben suggested.? It would be best to continue this conversation >>> via a github issue, which may bring other contributors into the >>> discussion. >>> >>> On Wed, Jan 8, 2020 at 7:27 PM Peter Teuben >> > wrote: >>> >>> ???? An example of a legal entry, and your entry would benefit the >>> ???? discussion. I can also imagine lots of other failure modes, for >>> example >>> ???? line file (if that is what you use) in the wrong place. Is there an >>> ???? error message from pyspeckit??? grepping this through the code is >>> ???? another good strategy to find the culprit. >>> >>> ???? another Peter. >>> >>> ???? On 1/8/20 6:53 PM, Peter Dzwig wrote: >>> ???? > Does anyone know where I can get hold of the detailed formatting >>> ???? > requirements of pyspeckit's (spec).measurements.lines? It >>> seems to be >>> ???? > rejecting some of *my* (I thought) fairly standard >>> line-formatting for >>> ???? > some reason. >>> ???? > >>> ???? > Thanks in advance if anyone is able to help, >>> ???? > >>> ???? > Peter Dzwig >>> ???? _______________________________________________ >>> ???? AstroPy mailing list >>> ???? AstroPy at python.org >>> ???? https://mail.python.org/mailman/listinfo/astropy >>> >>> >>> >>> --? >>> Adam Ginsburg >>> Assistant Professor, Department of Astronomy >>> University of Florida, Gainesville >>> http://www.adamgginsburg.com/ >>> >>> _______________________________________________ >>> AstroPy mailing list >>> AstroPy at python.org >>> https://mail.python.org/mailman/listinfo/astropy >>> > _______________________________________________ > AstroPy mailing list > AstroPy at python.org > https://mail.python.org/mailman/listinfo/astropy -- Dr. Peter Dzwig From stuart at cadair.com Sat Jan 11 08:15:37 2020 From: stuart at cadair.com (Stuart Mumford) Date: Sat, 11 Jan 2020 13:15:37 +0000 Subject: [AstroPy] SunPy 1.1.0 and 1.0.7 Released Message-ID: <3ba88fed3fa496e79ac5b49de08a2e625dfecaae.camel@cadair.com> Dear all, The SunPy project is happy to announce the release of SunPy 1.1! SunPy is an open-source Python library for Solar Physics data analysis and visualization. This release is our first major release post-1.0 and part of our new release pattern. The major highlights of this release are: * The `~sunpy.coordinates` subpackage now supports four additional coordinate frames (HCI, HEE, GSE, and GEI). * A new subpackage `sunpy.data.data_manager` has been added to support versioned data for functions and methods. * Support in `sunpy.map` and `sunpy.net` for the SUVI instrument on GOES satellites. * Initial support for WISPR data from Parker Solar Probe in `sunpy.map`. * The import times for `sunpy` and some subpackages are significantly shorter, with no loss of functionality. See What's New in SunPy 1.1 ( https://docs.sunpy.org/en/stable/whatsnew/1.1.html) for more details and the Full Changelog ( https://docs.sunpy.org/en/stable/whatsnew/changelog.html) for the full list of over 100 changes in 1.1. This release of SunPy contains 1137 commits in 242 merged pull requests closing 106 issues from 24 people, 10 of which are first time contributors to SunPy. To update you can run these following commands: Pip users: pip install -U sunpy Conda Users: conda update sunpy In addition to this we have released v1.0.7 which fixes some bugs in the 1.0 LTS series. The people who have contributed to the code for this release are: Albert Y. Shih Arthur Eigenbrot Brigitta Sipocz David P?rez-Su?rez David Stansby Dominik Sta?czak * Guntbert Reiter * Himanshu Pathak * Jack Ireland Juanjo Baz?n * Laura Hayes Michael S Kirk Nabil Freij Quinn Arbolante * Raahul Singh * Rajiv Ranjan Singh * Steven Christe Stuart Mumford Tom Augspurger * Vishnunarayan K I. Will Barnes Yash Sharma neerajkulk * Where a * indicates their first contribution to SunPy. Please enjoy, The SunPy Developers From scrane22301 at gmail.com Sun Jan 12 11:04:26 2020 From: scrane22301 at gmail.com (Saurabh Rane) Date: Sun, 12 Jan 2020 21:34:26 +0530 Subject: [AstroPy] Regarding open source contribution Message-ID: Respected sir, I came accross your organization while looking for open source projects. I'm fascinated by your work and want to contribute in any way possible. I know python language ,web development and Android development very well. I went through some of your documentation of python modules. Please guide me how can contribute and where to start. Git hub repo: https://github.com/sau22rane Thank you. Yours sincerely, Rane Saurabh -------------- next part -------------- An HTML attachment was scrubbed... URL: From 201804446 at post.au.dk Wed Jan 15 08:20:58 2020 From: 201804446 at post.au.dk (Sebastian Bugge Loeschcke) Date: Wed, 15 Jan 2020 14:20:58 +0100 Subject: [AstroPy] Question regarding the BoxLeastSquares Autopower function Message-ID: <63310c26dd9e32983f99266d8f75b45b@post.au.dk> Hi. I have a question regarding the autopower function of the _class _astropy.timeseries.BoxLeastSquares. The example from the documentation: >>> model = BoxLeastSquares(t, y) >>> results = model.autopower(0.16) >>> results.period[np.argmax(results.power)] >>> 1.9923406038842544 I know that the autopower function generates a heuristically determined period grid. However, I do not understand how the duration parameter for the autopower function is determined. _In this example, the duration is 0.16. _ Is it determined by analysing the light curve data and finding the duration of an event? Or do you choose a lower value to generate a larger period grid to test? I hope someone can help. Kind regards Sebastian Loeschcke Aarhus University, Denmark. Department of Computer Science _Link to the documentation:_ https://docs.astropy.org/en/latest/api/astropy.timeseries.BoxLeastSquares.html#astropy.timeseries.BoxLeastSquares.autopower -------------- next part -------------- An HTML attachment was scrubbed... URL: From jiffyclub at gmail.com Wed Jan 15 16:47:46 2020 From: jiffyclub at gmail.com (Matt Davis) Date: Wed, 15 Jan 2020 13:47:46 -0800 Subject: [AstroPy] SciPy 2020 Conference Message-ID: Hi Astropy Community, I want to bring the SciPy 2020 conference to your attention: https://www.scipy2020.scipy.org/. SciPy is one of my favorite yearly events with great tutorials, talks, and members of the scientific Python community. We're currently looking for talk, poster, and tutorial submission proposals through February 11, 2020. See more dates and details below. Thanks, Matt Davis SciPy 2020 Communications Committee Co-chair SciPy 2020, the 19th annual Scientific Computing with Python conference, will be held July 6-12, 2020 in Austin, Texas. The annual SciPy Conference brings together over 900 participants from industry, academia, and government to showcase their latest projects, learn from skilled users and developers, and collaborate on code development. The call for SciPy 2020 talks, posters, and tutorials is now open through February 11, 2020. *Talks and Posters (July 8-10, 2020)*In addition to the general track, this year will have the following specialized tracks, mini symposia, and sessions: *Tracks* High Performance Python Machine Learning and Data Science *Mini Symposia* Astronomy and Astrophysics Biology and Bioinformatics Earth, Ocean, Geo and Atmospheric Science Materials Science *Special Sessions* Maintainers Track SciPy Tools Plenary Session For additional details and instructions, please see the conference website . *Tutorials (July 6-7, 2020)* Tutorials should be focused on covering a well-defined topic in a hands-on manner. We are looking for awesome techniques or packages, helping new or advanced Python programmers develop better or faster scientific applications. We encourage submissions to be designed to allow at least 50% of the time for hands-on exercises even if this means the subject matter needs to be limited. Tutorials will be 4 hours in duration. In your tutorial application, you can indicate what prerequisite skills and knowledge will be needed for your tutorial, and the approximate expected level of knowledge of your students (i.e., beginner, intermediate, advanced). Instructors of accepted tutorials will receive a stipend. For examples of content and format, you can refer to tutorials from past SciPy tutorial sessions (SciPy 2018 , SciPy2019 ) and some accepted submissions . For additional details and instructions see the conference website . Submission page: https://easychair.org/conferences/?conf=scipy2020 Submission Deadline: February 11, 2020 -------------- next part -------------- An HTML attachment was scrubbed... URL: From shalmalee.kapse at students.mq.edu.au Thu Jan 16 01:58:10 2020 From: shalmalee.kapse at students.mq.edu.au (SHALMALEE KAPSE) Date: Thu, 16 Jan 2020 17:58:10 +1100 Subject: [AstroPy] Astropy reproject to align two HST images Message-ID: Hi. I am trying to align two images I downloaded from MAST HST portal. For this, I am using astropy-reproject package. However, I am running into an error, every time I use reproject, despite providing the WCS information. Following is the error: ValueError: an astropy.io.fits.HDUList is required for Lookup table distortion. I am using reproject version 0.6, and astropy both versions (3.2.3 and 4.0). Information about the images: One image is from HST/WFC3 and second one is from HST/ACS. I am attaching the two images along with my reproject code (.ipynb). Please let me know how to proceed and solve this issue. Thanks in advance. astropy_reproject_NGC_2257.ipynb f336w_01_flt.fits f814w_01_flt.fits Thanks and regards, Shalmalee Kapse, PhD Candidate, Department of Physics and Astronomy, Macquarie University,NSW - 2109, Australia. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shupe at ipac.caltech.edu Thu Jan 16 10:32:44 2020 From: shupe at ipac.caltech.edu (Shupe, David L.) Date: Thu, 16 Jan 2020 15:32:44 +0000 Subject: [AstroPy] Astropy reproject to align two HST images In-Reply-To: References: Message-ID: <1DA15A21-05BA-444D-BAD5-F5A3273CED41@caltech.edu> Hi Shalmalee, The error you are encountering is due to the WCS constructor needing more information from your input FITS files. I have modified your notebook to make it work through the reproject step. Here are my suggestions: Construct WCS?s explicitly like this, passing the HDULists as an additional argument so that the distortion parts are picked up: hdul1 = fits.open('f336w_01_flt.fits') hdul2 = fits.open('f814w_01_flt.fits?) output_wcs = WCS(hdul1[1].header, hdul1) input_wcs = WCS(hdul2[1].header, hdul2) In the call to reproject, pass a tuple of (array, WCS) as the first argument: array, footprint = reproject_interp((hdul1[1].data, input_wcs), output_wcs, shape_out=hdul2[1].data.shape) I was unable to make the plotting step work but at least these changes made the reproject step work without raising an exception. Kind regards, David Shupe Caltech/IPAC On Jan 15, 2020, at 10:58 PM, SHALMALEE KAPSE > wrote: Hi. I am trying to align two images I downloaded from MAST HST portal. For this, I am using astropy-reproject package. However, I am running into an error, every time I use reproject, despite providing the WCS information. Following is the error: ValueError: an astropy.io.fits.HDUList is required for Lookup table distortion. I am using reproject version 0.6, and astropy both versions (3.2.3 and 4.0). Information about the images: One image is from HST/WFC3 and second one is from HST/ACS. I am attaching the two images along with my reproject code (.ipynb). Please let me know how to proceed and solve this issue. Thanks in advance. [https://ssl.gstatic.com/docs/doclist/images/icon_10_generic_list.png] astropy_reproject_NGC_2257.ipynb[X] [https://ssl.gstatic.com/docs/doclist/images/icon_10_generic_list.png] f336w_01_flt.fits[X] [https://ssl.gstatic.com/docs/doclist/images/icon_10_generic_list.png] f814w_01_flt.fits[X] Thanks and regards, Shalmalee Kapse, PhD Candidate, Department of Physics and Astronomy, Macquarie University,NSW - 2109, Australia. _______________________________________________ AstroPy mailing list AstroPy at python.org https://mail.python.org/mailman/listinfo/astropy -------------- next part -------------- An HTML attachment was scrubbed... URL: