From derek at astro.physik.uni-goettingen.de  Fri Aug  1 17:59:06 2014
From: derek at astro.physik.uni-goettingen.de (Derek Homeier)
Date: Fri, 1 Aug 2014 23:59:06 +0200
Subject: [AstroPy] Need Help about Astropy.table.Table.write
In-Reply-To: <53DA4C29.50702@stsci.edu>
References: <53D24B5F.7010804@astro.umd.edu>	<53D23889.6050807@gmail.com>	<7203702.775961406052856075.JavaMail.coremail@mailweb>	<22638082.966731406290068860.JavaMail.coremail@mailweb>	<1466815.967341406291311814.JavaMail.coremail@mailweb>	<1406293210.2874.4.camel@iota.localdomain>	<C8ADBFC8-9F49-4B45-8AE5-1094A799C600@astro.physik.uni-goettingen.de>	<53D66561.3090808@stsci.edu>	<alpine.DEB.2.11.1407291847100.2866@anacreon>	<53D7E8DA.6010701@stsci.edu>	<18CAC28B-2EDB-4921-A6D3-1B35832D8142@colorado.edu>	<53D7F888.70904@stsci.edu>	<373AD7D4-D5AB-484E-BFCD-28D5289BA012@astro.physik.uni-goettingen.de>
	<53DA49E5.7060403@stsci.edu> <53DA4C29.50702@stsci.edu>
Message-ID: <6DC0353A-E884-49BC-B073-02EB4E77CF83@astro.physik.uni-goettingen.de>

On 31 Jul 2014, at 04:01 pm, Michael Droettboom <mdroe at stsci.edu> wrote:

>>> As with newton or kelvin? But that leads a bit astray from the original problem.
>>> I certainly think capitalisation variants should be tolerated,
>>> 
>> The problem is that capitalization is meaningful in units. mm vs. Mm is an obvious one.
>> 
> 
> Sorry, I meant to add an even more problematic example.  s (seconds) vs. S (Siemens) is another good one.  wcslib provides flags to convert 'S' to 's' (since that's the more common usage), but that's just a mess.  I *really* would prefer that files just said what they mean.  We're in a growing pain period here, where many legacy FITS files have never used the units in a meaningful way before -- we're never going to get to a place where they are useful for calculation if we aren't strict about their specific meanings.

Completely agree for the case of abbreviations and prefixes. When I wrote ?should be tolerated? - 
not ?accepted? - I did not want to argue against raising a warning in these cases, and especially not
for writing them to new files at least without a warning. But as you say there is a huge legacy of
FITS files sometimes without any policy on units usage we have to find a strategy to deal with,
one way or the other. ANGSTROM[S] vs. angstrom is certainly one of the least problems here.
I mentioned FORTRAN 6 because I got the impression there are probably lots of users (or software)
that may regard non-capitalised keywords a violation of the standard?

Cheers,
							Derek



From nathan12343 at gmail.com  Mon Aug  4 14:06:57 2014
From: nathan12343 at gmail.com (Nathan Goldbaum)
Date: Mon, 4 Aug 2014 11:06:57 -0700
Subject: [AstroPy] Fwd: [yt-users] ANN: yt-3.0 released!
In-Reply-To: <CALO3=5ENaiPC5Yd1cc0CTDqXn629W4Rh4gdsozFPNxpyff0hYQ@mail.gmail.com>
References: <CALO3=5ENaiPC5Yd1cc0CTDqXn629W4Rh4gdsozFPNxpyff0hYQ@mail.gmail.com>
Message-ID: <CAJXewOntvP3wOBp7PiC2jGPd3P+EjDX-GHKXEfChzDz7HL69tw@mail.gmail.com>

---------- Forwarded message ----------
From: Matthew Turk <matthewturk at gmail.com>
Date: Mon, Aug 4, 2014 at 9:50 AM
Subject: [yt-users] ANN: yt-3.0 released!
To: Discussion of the yt analysis package <yt-users at lists.spacepope.org>, "
yt-dev at lists.spacepope.org" <yt-dev at lists.spacepope.org>


The yt community is proud to announce the release of yt 3.0.

yt (http://yt-project.org) is an open source, community-developed
toolkit for analysis and visualization of volumetric data of all
types, with a particular emphasis on astrophysical simulations and
nuclear engineering simulations.

This release of yt features an entirely rewritten infrastructure for
data ingestion, indexing, and representation.  While past versions of
yt were focused on analysis and visualization of data structured as
regular grids, this release features full support for particle
(discrete point) data such as N-body and SPH data, irregular
hexahedral mesh data, and data organized via octrees.  This
infrastructure will be extended in future versions for high-fidelity
representation of unstructured mesh datasets.

Highlighted changes in yt 3.0:

 * Units now permeate the code base, enabling self-consistent unit
transformations of all arrays and quantities returned by yt.
 * Particle data is now supported using a lightweight octree.  SPH
data can be smoothed onto an adaptively-defined mesh using standard
SPH smoothing
 * Support for octree AMR codes
 * Preliminary Support for non-Cartesian data, such as cylindrical,
spherical, and geographical
 * Revamped analysis framework for halos and halo catalogs, including
direct ingestion and analysis of halo catalogs of several different
formats
 * Support for multi-fluid datasets and datasets containing multiple
particle types
 * Flexible support for dynamically defining new particle types using
filters on existing particle types or by combining different particle
types.
 * Vastly improved support for loading generic grid, AMR, hexahedral
mesh, and particle without hand-coding a frontend for a particular
data format.
 * New frontends for ART, ARTIO, Boxlib, Chombo, FITS, GDF, Subfind,
Rockstar, Pluto, RAMSES, SDF, Gadget, OWLS, PyNE, Tipsy, as well as
rewritten frontends for Enzo, FLASH, Athena, and generic data.
 * First release to support installation of yt on Windows
 * Extended capabilities for construction of simulated observations,
and new facilities for analyzing and visualizing FITS images and cube
data
 * Many performance improvements

This release is the first of several; while most functionality from
the previous generation of yt has been updated to work with yt 3.0, it
does not yet have feature parity in all respects.  While the core of
yt is stable, we suggest the support for analysis modules and volume
rendering be viewed as a late-stage beta, with a series of additional
releases (3.1, 3.2, etc) appearing over the course of the next year to
improve support in these areas.

For more information, including installation instructions, links to
community resources, and information on contributing to yt?s
development, please see the yt homepage at http://yt-project.org and
the documentation for yt-3.0 at http://yt-project.org/docs/3.0

yt is the product of a large community of developers and users and we
are extraordinarily grateful for and proud of their contributions.  yt
3.0 features contributions from over 60 individuals, constituting
almost 5000 commits. For many contributors, this is the first release
featuring their work.

Please forward this announcement on to any interested parties, and
look for information soon about upcoming workshops focused on yt and
applying it to your data.

Thank you,
_______________________________________________
yt-users mailing list
yt-users at lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140804/a0b32bb8/attachment.html>

From ghang.naoc at gmail.com  Fri Aug  8 11:34:46 2014
From: ghang.naoc at gmail.com (gonghang.naoc)
Date: Fri, 8 Aug 2014 23:34:46 +0800
Subject: [AstroPy] what are your favourite or top 5 modules?
Message-ID: <CABb23ms+sM7giAkRFV6JK+QeFWb1iL3yzyEA-j0TCN09mCRgBA@mail.gmail.com>

Hi all,

We can see lots of dazzling python programmes here. However it is
impossible we try every python module. Is there a simple list which can
satisfy our demand? And every one agrees that module is good and necessary.

It surely depends. My operating system is fedora20,64 bit. And generally I
deal with optical and high energy data.  What should I install?

Thanks.
best
hang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140808/5ddd7d85/attachment.html>

From lzkelley at gmail.com  Mon Aug 11 14:23:39 2014
From: lzkelley at gmail.com (Luke Zoltan Kelley)
Date: Mon, 11 Aug 2014 11:23:39 -0700
Subject: [AstroPy] missing modules in ipython notebook
Message-ID: <D397768C-0143-4123-B170-F44186D9CC50@gmail.com>

I'm using astropy 0.3.2 in an ipython notebook; my ipython is from canopy, version 2.1.0.  I can't access certain modules: astropy.io and astropy.table seem to be completely missing.  They don't appear in tab-completion, and if I try to access them I get something like:

In [8]: astropy.io
ERROR:astropy:AttributeError: 'module' object has no attribute 'io'
ERROR : AttributeError: 'module' object has no attribute 'io' [IPython.core.interactiveshell]
---------------------------------------------------------------------------
AttributeError
                            Traceback (most recent call last)
<ipython-input-8-d9b3d4bf20e3> in <module>()
----> 1 astropy.io
AttributeError : 'module' object has no attribute 'io'


Using the same version of astropy in a normal ipython session and the modules work fine.

Has anyone experienced any similar problems?

Thanks!
Luke

From jjk at uvic.ca  Mon Aug 11 14:35:18 2014
From: jjk at uvic.ca (JJ Kavelaars)
Date: Mon, 11 Aug 2014 11:35:18 -0700
Subject: [AstroPy] missing modules in ipython notebook
In-Reply-To: <D397768C-0143-4123-B170-F44186D9CC50@gmail.com>
References: <D397768C-0143-4123-B170-F44186D9CC50@gmail.com>
Message-ID: <9A47DC01-EE7F-4644-B0DD-C97EBC39FE4D@uvic.ca>

try:

import astropy.io

help(astropy.io)

The sub-packages are not loaded when you do import astropy

JJ

On Aug 11, 2014, at 11:23 AM, Luke Zoltan Kelley <lzkelley at gmail.com> wrote:

> I'm using astropy 0.3.2 in an ipython notebook; my ipython is from canopy, version 2.1.0.  I can't access certain modules: astropy.io and astropy.table seem to be completely missing.  They don't appear in tab-completion, and if I try to access them I get something like:
> 
> In [8]: astropy.io
> ERROR:astropy:AttributeError: 'module' object has no attribute 'io'
> ERROR : AttributeError: 'module' object has no attribute 'io' [IPython.core.interactiveshell]
> ---------------------------------------------------------------------------
> AttributeError
>                            Traceback (most recent call last)
> <ipython-input-8-d9b3d4bf20e3> in <module>()
> ----> 1 astropy.io
> AttributeError : 'module' object has no attribute 'io'
> 
> 
> Using the same version of astropy in a normal ipython session and the modules work fine.
> 
> Has anyone experienced any similar problems?
> 
> Thanks!
> Luke
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy



From lzkelley at gmail.com  Mon Aug 11 14:42:01 2014
From: lzkelley at gmail.com (Luke Zoltan Kelley)
Date: Mon, 11 Aug 2014 11:42:01 -0700
Subject: [AstroPy] missing modules in ipython notebook
In-Reply-To: <9A47DC01-EE7F-4644-B0DD-C97EBC39FE4D@uvic.ca>
References: <D397768C-0143-4123-B170-F44186D9CC50@gmail.com>
	<9A47DC01-EE7F-4644-B0DD-C97EBC39FE4D@uvic.ca>
Message-ID: <BC835258-0DAA-4A59-A9A5-7C76A7F57A9D@gmail.com>

using 'import astropy.io' does let me access 'io' --- but then not 'io.ascii' (for example).
However, when I use 'import astropy.io' I also get access to 'astropy.table' (which I wasn't before).

Why are modules loading in such a different way from how they do in ipython (or just python)?


On Aug 11, 2014, at 11:35 AM, JJ Kavelaars <jjk at uvic.ca> wrote:

> try:
> 
> import astropy.io
> 
> help(astropy.io)
> 
> The sub-packages are not loaded when you do import astropy
> 
> JJ
> 
> On Aug 11, 2014, at 11:23 AM, Luke Zoltan Kelley <lzkelley at gmail.com> wrote:
> 
>> I'm using astropy 0.3.2 in an ipython notebook; my ipython is from canopy, version 2.1.0.  I can't access certain modules: astropy.io and astropy.table seem to be completely missing.  They don't appear in tab-completion, and if I try to access them I get something like:
>> 
>> In [8]: astropy.io
>> ERROR:astropy:AttributeError: 'module' object has no attribute 'io'
>> ERROR : AttributeError: 'module' object has no attribute 'io' [IPython.core.interactiveshell]
>> ---------------------------------------------------------------------------
>> AttributeError
>>                           Traceback (most recent call last)
>> <ipython-input-8-d9b3d4bf20e3> in <module>()
>> ----> 1 astropy.io
>> AttributeError : 'module' object has no attribute 'io'
>> 
>> 
>> Using the same version of astropy in a normal ipython session and the modules work fine.
>> 
>> Has anyone experienced any similar problems?
>> 
>> Thanks!
>> Luke
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
> 
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy



From embray at stsci.edu  Mon Aug 11 17:03:08 2014
From: embray at stsci.edu (Erik Bray)
Date: Mon, 11 Aug 2014 17:03:08 -0400
Subject: [AstroPy] missing modules in ipython notebook
In-Reply-To: <BC835258-0DAA-4A59-A9A5-7C76A7F57A9D@gmail.com>
References: <D397768C-0143-4123-B170-F44186D9CC50@gmail.com>	<9A47DC01-EE7F-4644-B0DD-C97EBC39FE4D@uvic.ca>
	<BC835258-0DAA-4A59-A9A5-7C76A7F57A9D@gmail.com>
Message-ID: <53E92F8C.3040703@stsci.edu>

On 08/11/2014 02:42 PM, Luke Zoltan Kelley wrote:
> using 'import astropy.io' does let me access 'io' --- but then not 'io.ascii' (for example).
> However, when I use 'import astropy.io' I also get access to 'astropy.table' (which I wasn't before).
>
> Why are modules loading in such a different way from how they do in ipython (or just python)?

Hi,

I'm not sure what you mean by "in IPython".  There's nothing special about the 
way imports work in IPython as opposed to anywhere else.  I think people tend to 
get more confused about it in IPython though due to its autocomplete features.

This is normal for Python packages--by default when do, say, "import astropy" 
Python does not automatically populate the "astropy." namespace with all 
submodules of "astropy" (it may not even know there *are* submodules until and 
unless you explicitly request them, for example, by running "import astropy.io").

However, if the astropy.__init__ module contains code like:

     from . import io
     from . import table
     from . import ... etc ...

*then* the astropy. namespace is populated with the names of those submodules. 
The reason most large packages don't do this (see for example SciPy) is that 
importing all those submodules can add a lot of extra overhead to just running 
"import astropy"--especially if the user only intended to use one or two submodules.

The reason "astropy.table" was populated when you ran "import astropy.io" is 
because something in the IO framework imported the table submodule itself, so 
that part of the astropy namespace became populated.

Erik

> On Aug 11, 2014, at 11:35 AM, JJ Kavelaars <jjk at uvic.ca> wrote:
>
>> try:
>>
>> import astropy.io
>>
>> help(astropy.io)
>>
>> The sub-packages are not loaded when you do import astropy
>>
>> JJ
>>
>> On Aug 11, 2014, at 11:23 AM, Luke Zoltan Kelley <lzkelley at gmail.com> wrote:
>>
>>> I'm using astropy 0.3.2 in an ipython notebook; my ipython is from canopy, version 2.1.0.  I can't access certain modules: astropy.io and astropy.table seem to be completely missing.  They don't appear in tab-completion, and if I try to access them I get something like:
>>>
>>> In [8]: astropy.io
>>> ERROR:astropy:AttributeError: 'module' object has no attribute 'io'
>>> ERROR : AttributeError: 'module' object has no attribute 'io' [IPython.core.interactiveshell]
>>> ---------------------------------------------------------------------------
>>> AttributeError
>>>                            Traceback (most recent call last)
>>> <ipython-input-8-d9b3d4bf20e3> in <module>()
>>> ----> 1 astropy.io
>>> AttributeError : 'module' object has no attribute 'io'
>>>
>>>
>>> Using the same version of astropy in a normal ipython session and the modules work fine.
>>>
>>> Has anyone experienced any similar problems?
>>>
>>> Thanks!
>>> Luke
>>> _______________________________________________
>>> AstroPy mailing list
>>> AstroPy at scipy.org
>>> http://mail.scipy.org/mailman/listinfo/astropy
>>
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>



From kylebarbary at gmail.com  Mon Aug 11 20:37:36 2014
From: kylebarbary at gmail.com (Kyle Barbary)
Date: Mon, 11 Aug 2014 17:37:36 -0700
Subject: [AstroPy] [ANN] sep v0.1.0: Source Extractor functionality in python
Message-ID: <CANO7-x-vh_BUaGuKbHpn_7A-uE6E_VWPKiVDyE0siN49mY2A3g@mail.gmail.com>

Hi all,

I?m pleased to announce the first release of the SEP python module. SEP
makes available from Python a few of the algorithms used in Source
Extractor. So far, this includes global background estimation, object
detection, and circular aperture photometry. It operates on plain ol? numpy
arrays.

The Python module is largely a wrapper for a C library (also named SEP)
that is derived directly from the Source Extractor code base, so it is very
fast.

https://github.com/kbarbary/sep-python

*Install*

   - with pip: pip install sep
   - with conda (linux only): conda install -c
   https://conda.binstar.org/kbarbary sep

Feedback, bug reports, and contributions welcome.

Finally, note that there has been some discussion of including SEP in the
photutils (astropy-affiliated) package, and this may still happen. However,
it may be some time until it is included in a photutils release, so I
wanted to make it available as a stand-alone package as well.

- Kyle
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140811/4a69c474/attachment.html>

From anizami at macalester.edu  Tue Aug 12 11:18:04 2014
From: anizami at macalester.edu (Asra Nizami)
Date: Tue, 12 Aug 2014 11:18:04 -0400
Subject: [AstroPy] Release of WCSAxes 0.2
Message-ID: <CAO=bY=DZEH5pqgvWbvz=Ob09VNFNWn6GTmUbPfwsX8PKJNHDSg@mail.gmail.com>

Hi everyone,

I have released a 0.2 version of WCSAxes, a framework for plotting
astronomical images in Matplotlib. The package is available at



https://pypi.python.org/pypi/wcsaxes/0.2



and the latest documentation can be found at



http://wcsaxes.readthedocs.org/en/latest/



I have been working on WCSAxes as part of my GSoC project for Astropy and
this release includes some new features and small bug fixes. The new
features of this version are

* the ability to draw minor ticks

* more control over tick labels

* more control over setting the color and linewidth of frames

This release also includes  contributions from Thomas Robitaille and
Christoph Deil.



Best,

Asra

-- 
Asra Nizami
Macalester College '16
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140812/6064a9ff/attachment.html>

From ghang.naoc at gmail.com  Wed Aug 13 02:06:34 2014
From: ghang.naoc at gmail.com (gonghang.naoc)
Date: Wed, 13 Aug 2014 14:06:34 +0800
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
Message-ID: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>

Hi,
I reinstalled my system just now. The previsous system had a mess of python
modules with chaotic dependency. Could somebody please give me a simple
list to instll? Potentially I need numpy,scipy,epd, ureka,iraf,pyraf,
anaconda or somethig else which you can suggest.

A simple and versatile combo is the best.

Thanks.
best

hang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140813/4d7c7558/attachment.html>

From thomas.robitaille at gmail.com  Wed Aug 13 02:53:32 2014
From: thomas.robitaille at gmail.com (Thomas Robitaille)
Date: Wed, 13 Aug 2014 08:53:32 +0200
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
Message-ID: <53EB0B6C.6060703@gmail.com>

Hi Hang,

I doubt you will get a single answer here, but I think Anaconda is now
widely thought to be a good solution for a generic Scientific Python
installation, but Ureka is probably what you want since you also want IRAF:

http://ssb.stsci.edu/ureka/

http://ssb.stsci.edu/ureka/1.4.1/docs/components.html

Cheers,
Tom

gonghang.naoc wrote:
> Hi,
> I reinstalled my system just now. The previsous system had a mess of
> python modules with chaotic dependency. Could somebody please give me a
> simple list to instll? Potentially I need numpy,scipy,epd,
> ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
>  
> A simple and versatile combo is the best.
>  
> Thanks.
> best
>  
> hang
>  
> 
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy


From embray at stsci.edu  Wed Aug 13 10:25:52 2014
From: embray at stsci.edu (Erik Bray)
Date: Wed, 13 Aug 2014 10:25:52 -0400
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <53EB0B6C.6060703@gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<53EB0B6C.6060703@gmail.com>
Message-ID: <53EB7570.4020003@stsci.edu>

On 08/13/2014 02:53 AM, Thomas Robitaille wrote:
> Hi Hang,
>
> I doubt you will get a single answer here, but I think Anaconda is now
> widely thought to be a good solution for a generic Scientific Python
> installation, but Ureka is probably what you want since you also want IRAF:
>
> http://ssb.stsci.edu/ureka/
>
> http://ssb.stsci.edu/ureka/1.4.1/docs/components.html

As an aside, you also listed separately Numpy, SciPy, EPD, Ureka, and Anaconda.

First of all EPD no longer exists as such and now is called Canopy.  All of 
Canopy, Anaconda, and Ureka are standalone scientific Python *distributions*, 
each with their own copies of Python itself, Numpy, SciPy, and many other 
popular packages.  In principle they can all coexist on your system, though if 
you have to ask I'd recommend deciding which one best suits your needs and 
sticking with just the one.

As Tom said, if you need IRAF you should use Ureka, as it's the only scientific 
Python distribution developed specifically for the Astronomy community and that 
includes IRAF and Pyraf.  Full disclosure: I work for STScI which is the primary 
contributor to Ureka, but I don't personally have much connection to the project 
and don't use it personally.  I hear it works pretty well though.

Erik

>
> gonghang.naoc wrote:
>> Hi,
>> I reinstalled my system just now. The previsous system had a mess of
>> python modules with chaotic dependency. Could somebody please give me a
>> simple list to instll? Potentially I need numpy,scipy,epd,
>> ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
>>
>> A simple and versatile combo is the best.
>>
>> Thanks.
>> best
>>
>> hang
>>
>>
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>



From ghang.naoc at gmail.com  Wed Aug 13 11:13:00 2014
From: ghang.naoc at gmail.com (gonghang.naoc)
Date: Wed, 13 Aug 2014 23:13:00 +0800
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <53EB7570.4020003@stsci.edu>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<53EB0B6C.6060703@gmail.com> <53EB7570.4020003@stsci.edu>
Message-ID: <CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>

Hi Tom, Erik,
Thank you both. Glad to hear there is a simple choice. I will stick with
Anaconda.
best
hang


On Wed, Aug 13, 2014 at 10:25 PM, Erik Bray <embray at stsci.edu> wrote:

> On 08/13/2014 02:53 AM, Thomas Robitaille wrote:
> > Hi Hang,
> >
> > I doubt you will get a single answer here, but I think Anaconda is now
> > widely thought to be a good solution for a generic Scientific Python
> > installation, but Ureka is probably what you want since you also want
> IRAF:
> >
> > http://ssb.stsci.edu/ureka/
> >
> > http://ssb.stsci.edu/ureka/1.4.1/docs/components.html
>
> As an aside, you also listed separately Numpy, SciPy, EPD, Ureka, and
> Anaconda.
>
> First of all EPD no longer exists as such and now is called Canopy.  All of
> Canopy, Anaconda, and Ureka are standalone scientific Python
> *distributions*,
> each with their own copies of Python itself, Numpy, SciPy, and many other
> popular packages.  In principle they can all coexist on your system,
> though if
> you have to ask I'd recommend deciding which one best suits your needs and
> sticking with just the one.
>
> As Tom said, if you need IRAF you should use Ureka, as it's the only
> scientific
> Python distribution developed specifically for the Astronomy community and
> that
> includes IRAF and Pyraf.  Full disclosure: I work for STScI which is the
> primary
> contributor to Ureka, but I don't personally have much connection to the
> project
> and don't use it personally.  I hear it works pretty well though.
>
> Erik
>
> >
> > gonghang.naoc wrote:
> >> Hi,
> >> I reinstalled my system just now. The previsous system had a mess of
> >> python modules with chaotic dependency. Could somebody please give me a
> >> simple list to instll? Potentially I need numpy,scipy,epd,
> >> ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
> >>
> >> A simple and versatile combo is the best.
> >>
> >> Thanks.
> >> best
> >>
> >> hang
> >>
> >>
> >> _______________________________________________
> >> AstroPy mailing list
> >> AstroPy at scipy.org
> >> http://mail.scipy.org/mailman/listinfo/astropy
> > _______________________________________________
> > AstroPy mailing list
> > AstroPy at scipy.org
> > http://mail.scipy.org/mailman/listinfo/astropy
> >
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140813/bd35a3a4/attachment.html>

From stsci.perry at gmail.com  Wed Aug 13 11:15:31 2014
From: stsci.perry at gmail.com (Perry Greenfield)
Date: Wed, 13 Aug 2014 11:15:31 -0400
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<53EB0B6C.6060703@gmail.com> <53EB7570.4020003@stsci.edu>
	<CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>
Message-ID: <4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>

So you don't really need IRAF? Or are you installing that separately (and layering pyraf onto anaconda)?

Perry

On Aug 13, 2014, at 11:13 AM, gonghang.naoc wrote:

> Hi Tom, Erik,
> Thank you both. Glad to hear there is a simple choice. I will stick with Anaconda.
> best
> hang
> 
> 
> On Wed, Aug 13, 2014 at 10:25 PM, Erik Bray <embray at stsci.edu> wrote:
> On 08/13/2014 02:53 AM, Thomas Robitaille wrote:
> > Hi Hang,
> >
> > I doubt you will get a single answer here, but I think Anaconda is now
> > widely thought to be a good solution for a generic Scientific Python
> > installation, but Ureka is probably what you want since you also want IRAF:
> >
> > http://ssb.stsci.edu/ureka/
> >
> > http://ssb.stsci.edu/ureka/1.4.1/docs/components.html
> 
> As an aside, you also listed separately Numpy, SciPy, EPD, Ureka, and Anaconda.
> 
> First of all EPD no longer exists as such and now is called Canopy.  All of
> Canopy, Anaconda, and Ureka are standalone scientific Python *distributions*,
> each with their own copies of Python itself, Numpy, SciPy, and many other
> popular packages.  In principle they can all coexist on your system, though if
> you have to ask I'd recommend deciding which one best suits your needs and
> sticking with just the one.
> 
> As Tom said, if you need IRAF you should use Ureka, as it's the only scientific
> Python distribution developed specifically for the Astronomy community and that
> includes IRAF and Pyraf.  Full disclosure: I work for STScI which is the primary
> contributor to Ureka, but I don't personally have much connection to the project
> and don't use it personally.  I hear it works pretty well though.
> 
> Erik
> 
> >
> > gonghang.naoc wrote:
> >> Hi,
> >> I reinstalled my system just now. The previsous system had a mess of
> >> python modules with chaotic dependency. Could somebody please give me a
> >> simple list to instll? Potentially I need numpy,scipy,epd,
> >> ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
> >>
> >> A simple and versatile combo is the best.
> >>
> >> Thanks.
> >> best
> >>
> >> hang
> >>
> >>
> >> _______________________________________________
> >> AstroPy mailing list
> >> AstroPy at scipy.org
> >> http://mail.scipy.org/mailman/listinfo/astropy
> > _______________________________________________
> > AstroPy mailing list
> > AstroPy at scipy.org
> > http://mail.scipy.org/mailman/listinfo/astropy
> >
> 
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
> 
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy



From ghang.naoc at gmail.com  Wed Aug 13 11:21:03 2014
From: ghang.naoc at gmail.com (gonghang.naoc)
Date: Wed, 13 Aug 2014 23:21:03 +0800
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<53EB0B6C.6060703@gmail.com> <53EB7570.4020003@stsci.edu>
	<CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>
	<4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>
Message-ID: <CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>

Yes,I need it. I am thinking about which 'iraf' I should use, the
standalone version of NOAO, Ureka or pyraf?


On Wed, Aug 13, 2014 at 11:15 PM, Perry Greenfield <stsci.perry at gmail.com>
wrote:

> So you don't really need IRAF? Or are you installing that separately (and
> layering pyraf onto anaconda)?
>
> Perry
>
> On Aug 13, 2014, at 11:13 AM, gonghang.naoc wrote:
>
> > Hi Tom, Erik,
> > Thank you both. Glad to hear there is a simple choice. I will stick with
> Anaconda.
> > best
> > hang
> >
> >
> > On Wed, Aug 13, 2014 at 10:25 PM, Erik Bray <embray at stsci.edu> wrote:
> > On 08/13/2014 02:53 AM, Thomas Robitaille wrote:
> > > Hi Hang,
> > >
> > > I doubt you will get a single answer here, but I think Anaconda is now
> > > widely thought to be a good solution for a generic Scientific Python
> > > installation, but Ureka is probably what you want since you also want
> IRAF:
> > >
> > > http://ssb.stsci.edu/ureka/
> > >
> > > http://ssb.stsci.edu/ureka/1.4.1/docs/components.html
> >
> > As an aside, you also listed separately Numpy, SciPy, EPD, Ureka, and
> Anaconda.
> >
> > First of all EPD no longer exists as such and now is called Canopy.  All
> of
> > Canopy, Anaconda, and Ureka are standalone scientific Python
> *distributions*,
> > each with their own copies of Python itself, Numpy, SciPy, and many other
> > popular packages.  In principle they can all coexist on your system,
> though if
> > you have to ask I'd recommend deciding which one best suits your needs
> and
> > sticking with just the one.
> >
> > As Tom said, if you need IRAF you should use Ureka, as it's the only
> scientific
> > Python distribution developed specifically for the Astronomy community
> and that
> > includes IRAF and Pyraf.  Full disclosure: I work for STScI which is the
> primary
> > contributor to Ureka, but I don't personally have much connection to the
> project
> > and don't use it personally.  I hear it works pretty well though.
> >
> > Erik
> >
> > >
> > > gonghang.naoc wrote:
> > >> Hi,
> > >> I reinstalled my system just now. The previsous system had a mess of
> > >> python modules with chaotic dependency. Could somebody please give me
> a
> > >> simple list to instll? Potentially I need numpy,scipy,epd,
> > >> ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
> > >>
> > >> A simple and versatile combo is the best.
> > >>
> > >> Thanks.
> > >> best
> > >>
> > >> hang
> > >>
> > >>
> > >> _______________________________________________
> > >> AstroPy mailing list
> > >> AstroPy at scipy.org
> > >> http://mail.scipy.org/mailman/listinfo/astropy
> > > _______________________________________________
> > > AstroPy mailing list
> > > AstroPy at scipy.org
> > > http://mail.scipy.org/mailman/listinfo/astropy
> > >
> >
> > _______________________________________________
> > AstroPy mailing list
> > AstroPy at scipy.org
> > http://mail.scipy.org/mailman/listinfo/astropy
> >
> > _______________________________________________
> > AstroPy mailing list
> > AstroPy at scipy.org
> > http://mail.scipy.org/mailman/listinfo/astropy
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140813/a5d726ed/attachment.html>

From bjd2385 at rit.edu  Wed Aug 13 11:22:41 2014
From: bjd2385 at rit.edu (Brandon Doyle)
Date: Wed, 13 Aug 2014 11:22:41 -0400
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<53EB0B6C.6060703@gmail.com> <53EB7570.4020003@stsci.edu>
	<CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>
	<4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>
	<CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>
Message-ID: <CAA-aB-b+pKD7V_1Z5odD3coij9MVV8Djj1mx6YPFrx1arCv5iQ@mail.gmail.com>

I've been looking into PyRAF...so it requires that you have IRAF installed
on your computer?


On Wed, Aug 13, 2014 at 11:21 AM, gonghang.naoc <ghang.naoc at gmail.com>
wrote:

> Yes,I need it. I am thinking about which 'iraf' I should use, the
> standalone version of NOAO, Ureka or pyraf?
>
>
> On Wed, Aug 13, 2014 at 11:15 PM, Perry Greenfield <stsci.perry at gmail.com>
> wrote:
>
>> So you don't really need IRAF? Or are you installing that separately (and
>> layering pyraf onto anaconda)?
>>
>> Perry
>>
>> On Aug 13, 2014, at 11:13 AM, gonghang.naoc wrote:
>>
>> > Hi Tom, Erik,
>> > Thank you both. Glad to hear there is a simple choice. I will stick
>> with Anaconda.
>> > best
>> > hang
>> >
>> >
>> > On Wed, Aug 13, 2014 at 10:25 PM, Erik Bray <embray at stsci.edu> wrote:
>> > On 08/13/2014 02:53 AM, Thomas Robitaille wrote:
>> > > Hi Hang,
>> > >
>> > > I doubt you will get a single answer here, but I think Anaconda is now
>> > > widely thought to be a good solution for a generic Scientific Python
>> > > installation, but Ureka is probably what you want since you also want
>> IRAF:
>> > >
>> > > http://ssb.stsci.edu/ureka/
>> > >
>> > > http://ssb.stsci.edu/ureka/1.4.1/docs/components.html
>> >
>> > As an aside, you also listed separately Numpy, SciPy, EPD, Ureka, and
>> Anaconda.
>> >
>> > First of all EPD no longer exists as such and now is called Canopy.
>>  All of
>> > Canopy, Anaconda, and Ureka are standalone scientific Python
>> *distributions*,
>> > each with their own copies of Python itself, Numpy, SciPy, and many
>> other
>> > popular packages.  In principle they can all coexist on your system,
>> though if
>> > you have to ask I'd recommend deciding which one best suits your needs
>> and
>> > sticking with just the one.
>> >
>> > As Tom said, if you need IRAF you should use Ureka, as it's the only
>> scientific
>> > Python distribution developed specifically for the Astronomy community
>> and that
>> > includes IRAF and Pyraf.  Full disclosure: I work for STScI which is
>> the primary
>> > contributor to Ureka, but I don't personally have much connection to
>> the project
>> > and don't use it personally.  I hear it works pretty well though.
>> >
>> > Erik
>> >
>> > >
>> > > gonghang.naoc wrote:
>> > >> Hi,
>> > >> I reinstalled my system just now. The previsous system had a mess of
>> > >> python modules with chaotic dependency. Could somebody please give
>> me a
>> > >> simple list to instll? Potentially I need numpy,scipy,epd,
>> > >> ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
>> > >>
>> > >> A simple and versatile combo is the best.
>> > >>
>> > >> Thanks.
>> > >> best
>> > >>
>> > >> hang
>> > >>
>> > >>
>> > >> _______________________________________________
>> > >> AstroPy mailing list
>> > >> AstroPy at scipy.org
>> > >> http://mail.scipy.org/mailman/listinfo/astropy
>> > > _______________________________________________
>> > > AstroPy mailing list
>> > > AstroPy at scipy.org
>> > > http://mail.scipy.org/mailman/listinfo/astropy
>> > >
>> >
>> > _______________________________________________
>> > AstroPy mailing list
>> > AstroPy at scipy.org
>> > http://mail.scipy.org/mailman/listinfo/astropy
>> >
>> > _______________________________________________
>> > AstroPy mailing list
>> > AstroPy at scipy.org
>> > http://mail.scipy.org/mailman/listinfo/astropy
>>
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
>>
>
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140813/59c0f815/attachment.html>

From mcraig at mnstate.edu  Wed Aug 13 11:27:55 2014
From: mcraig at mnstate.edu (Matthew Craig)
Date: Wed, 13 Aug 2014 10:27:55 -0500
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<53EB0B6C.6060703@gmail.com> <53EB7570.4020003@stsci.edu>
	<CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>
	<4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>
	<CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>
Message-ID: <AF519169-377B-45DB-890C-20A3D83766F1@mnstate.edu>

My own $0.02, as someone who uses anaconda almost exclusively: if you want IRAF also install Ureka.

It will:

+ not mess up any of your regular workflow in anaconda
+ function as a full-powered python distro when you need it to
+ prevent you from spending tens of hours solving the problem of IRAF/pyraf installation?other people have solved that problem already!

Matt Craig 

On sabbatical 2013-14: email is the best way to reach me
----
Professor
Department of Physics and Astronomy 
Minnesota State University Moorhead
1104 7th Ave S, Moorhead MN 56563

phone: On sabbatical 2013-14: email is the best way to reach me 
fax: (218) 477-2290

On Aug 13, 2014, at 10:21 AM, gonghang.naoc <ghang.naoc at gmail.com> wrote:

> Yes,I need it. I am thinking about which 'iraf' I should use, the standalone version of NOAO, Ureka or pyraf?
> 
> 
> On Wed, Aug 13, 2014 at 11:15 PM, Perry Greenfield <stsci.perry at gmail.com> wrote:
> So you don't really need IRAF? Or are you installing that separately (and layering pyraf onto anaconda)?
> 
> Perry
> 
> On Aug 13, 2014, at 11:13 AM, gonghang.naoc wrote:
> 
> > Hi Tom, Erik,
> > Thank you both. Glad to hear there is a simple choice. I will stick with Anaconda.
> > best
> > hang
> >
> >
> > On Wed, Aug 13, 2014 at 10:25 PM, Erik Bray <embray at stsci.edu> wrote:
> > On 08/13/2014 02:53 AM, Thomas Robitaille wrote:
> > > Hi Hang,
> > >
> > > I doubt you will get a single answer here, but I think Anaconda is now
> > > widely thought to be a good solution for a generic Scientific Python
> > > installation, but Ureka is probably what you want since you also want IRAF:
> > >
> > > http://ssb.stsci.edu/ureka/
> > >
> > > http://ssb.stsci.edu/ureka/1.4.1/docs/components.html
> >
> > As an aside, you also listed separately Numpy, SciPy, EPD, Ureka, and Anaconda.
> >
> > First of all EPD no longer exists as such and now is called Canopy.  All of
> > Canopy, Anaconda, and Ureka are standalone scientific Python *distributions*,
> > each with their own copies of Python itself, Numpy, SciPy, and many other
> > popular packages.  In principle they can all coexist on your system, though if
> > you have to ask I'd recommend deciding which one best suits your needs and
> > sticking with just the one.
> >
> > As Tom said, if you need IRAF you should use Ureka, as it's the only scientific
> > Python distribution developed specifically for the Astronomy community and that
> > includes IRAF and Pyraf.  Full disclosure: I work for STScI which is the primary
> > contributor to Ureka, but I don't personally have much connection to the project
> > and don't use it personally.  I hear it works pretty well though.
> >
> > Erik
> >
> > >
> > > gonghang.naoc wrote:
> > >> Hi,
> > >> I reinstalled my system just now. The previsous system had a mess of
> > >> python modules with chaotic dependency. Could somebody please give me a
> > >> simple list to instll? Potentially I need numpy,scipy,epd,
> > >> ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
> > >>
> > >> A simple and versatile combo is the best.
> > >>
> > >> Thanks.
> > >> best
> > >>
> > >> hang
> > >>
> > >>
> > >> _______________________________________________
> > >> AstroPy mailing list
> > >> AstroPy at scipy.org
> > >> http://mail.scipy.org/mailman/listinfo/astropy
> > > _______________________________________________
> > > AstroPy mailing list
> > > AstroPy at scipy.org
> > > http://mail.scipy.org/mailman/listinfo/astropy
> > >
> >
> > _______________________________________________
> > AstroPy mailing list
> > AstroPy at scipy.org
> > http://mail.scipy.org/mailman/listinfo/astropy
> >
> > _______________________________________________
> > AstroPy mailing list
> > AstroPy at scipy.org
> > http://mail.scipy.org/mailman/listinfo/astropy
> 
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
> 
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140813/91d4a824/attachment.html>

From ghang.naoc at gmail.com  Wed Aug 13 11:32:35 2014
From: ghang.naoc at gmail.com (gonghang.naoc)
Date: Wed, 13 Aug 2014 23:32:35 +0800
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <CAA-aB-b+pKD7V_1Z5odD3coij9MVV8Djj1mx6YPFrx1arCv5iQ@mail.gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<53EB0B6C.6060703@gmail.com> <53EB7570.4020003@stsci.edu>
	<CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>
	<4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>
	<CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>
	<CAA-aB-b+pKD7V_1Z5odD3coij9MVV8Djj1mx6YPFrx1arCv5iQ@mail.gmail.com>
Message-ID: <CABb23msY_otMkN7aMZeFukLVD1eQmZ4NR+Aj071Ti8pbugz3Fg@mail.gmail.com>

I installed both long time ago. I am sure a single pyraf without iraf can
work, although there is a something here
http://www.stsci.edu/institute/software_hardware/pyraf
'PyRAF can be installed along with an existing IRAF installation'
That means pyraf can work alone?



On Wed, Aug 13, 2014 at 11:22 PM, Brandon Doyle <bjd2385 at rit.edu> wrote:

> I've been looking into PyRAF...so it requires that you have IRAF installed
> on your computer?
>
>
> On Wed, Aug 13, 2014 at 11:21 AM, gonghang.naoc <ghang.naoc at gmail.com>
> wrote:
>
>> Yes,I need it. I am thinking about which 'iraf' I should use, the
>> standalone version of NOAO, Ureka or pyraf?
>>
>>
>> On Wed, Aug 13, 2014 at 11:15 PM, Perry Greenfield <stsci.perry at gmail.com
>> > wrote:
>>
>>> So you don't really need IRAF? Or are you installing that separately
>>> (and layering pyraf onto anaconda)?
>>>
>>> Perry
>>>
>>> On Aug 13, 2014, at 11:13 AM, gonghang.naoc wrote:
>>>
>>> > Hi Tom, Erik,
>>> > Thank you both. Glad to hear there is a simple choice. I will stick
>>> with Anaconda.
>>> > best
>>> > hang
>>> >
>>> >
>>> > On Wed, Aug 13, 2014 at 10:25 PM, Erik Bray <embray at stsci.edu> wrote:
>>> > On 08/13/2014 02:53 AM, Thomas Robitaille wrote:
>>> > > Hi Hang,
>>> > >
>>> > > I doubt you will get a single answer here, but I think Anaconda is
>>> now
>>> > > widely thought to be a good solution for a generic Scientific Python
>>> > > installation, but Ureka is probably what you want since you also
>>> want IRAF:
>>> > >
>>> > > http://ssb.stsci.edu/ureka/
>>> > >
>>> > > http://ssb.stsci.edu/ureka/1.4.1/docs/components.html
>>> >
>>> > As an aside, you also listed separately Numpy, SciPy, EPD, Ureka, and
>>> Anaconda.
>>> >
>>> > First of all EPD no longer exists as such and now is called Canopy.
>>>  All of
>>> > Canopy, Anaconda, and Ureka are standalone scientific Python
>>> *distributions*,
>>> > each with their own copies of Python itself, Numpy, SciPy, and many
>>> other
>>> > popular packages.  In principle they can all coexist on your system,
>>> though if
>>> > you have to ask I'd recommend deciding which one best suits your needs
>>> and
>>> > sticking with just the one.
>>> >
>>> > As Tom said, if you need IRAF you should use Ureka, as it's the only
>>> scientific
>>> > Python distribution developed specifically for the Astronomy community
>>> and that
>>> > includes IRAF and Pyraf.  Full disclosure: I work for STScI which is
>>> the primary
>>> > contributor to Ureka, but I don't personally have much connection to
>>> the project
>>> > and don't use it personally.  I hear it works pretty well though.
>>> >
>>> > Erik
>>> >
>>> > >
>>> > > gonghang.naoc wrote:
>>> > >> Hi,
>>> > >> I reinstalled my system just now. The previsous system had a mess of
>>> > >> python modules with chaotic dependency. Could somebody please give
>>> me a
>>> > >> simple list to instll? Potentially I need numpy,scipy,epd,
>>> > >> ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
>>> > >>
>>> > >> A simple and versatile combo is the best.
>>> > >>
>>> > >> Thanks.
>>> > >> best
>>> > >>
>>> > >> hang
>>> > >>
>>> > >>
>>> > >> _______________________________________________
>>> > >> AstroPy mailing list
>>> > >> AstroPy at scipy.org
>>> > >> http://mail.scipy.org/mailman/listinfo/astropy
>>> > > _______________________________________________
>>> > > AstroPy mailing list
>>> > > AstroPy at scipy.org
>>> > > http://mail.scipy.org/mailman/listinfo/astropy
>>> > >
>>> >
>>> > _______________________________________________
>>> > AstroPy mailing list
>>> > AstroPy at scipy.org
>>> > http://mail.scipy.org/mailman/listinfo/astropy
>>> >
>>> > _______________________________________________
>>> > AstroPy mailing list
>>> > AstroPy at scipy.org
>>> > http://mail.scipy.org/mailman/listinfo/astropy
>>>
>>> _______________________________________________
>>> AstroPy mailing list
>>> AstroPy at scipy.org
>>> http://mail.scipy.org/mailman/listinfo/astropy
>>>
>>
>>
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
>>
>>
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140813/e7627d5f/attachment.html>

From ghang.naoc at gmail.com  Wed Aug 13 11:34:20 2014
From: ghang.naoc at gmail.com (gonghang.naoc)
Date: Wed, 13 Aug 2014 23:34:20 +0800
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <CABb23msY_otMkN7aMZeFukLVD1eQmZ4NR+Aj071Ti8pbugz3Fg@mail.gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<53EB0B6C.6060703@gmail.com> <53EB7570.4020003@stsci.edu>
	<CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>
	<4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>
	<CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>
	<CAA-aB-b+pKD7V_1Z5odD3coij9MVV8Djj1mx6YPFrx1arCv5iQ@mail.gmail.com>
	<CABb23msY_otMkN7aMZeFukLVD1eQmZ4NR+Aj071Ti8pbugz3Fg@mail.gmail.com>
Message-ID: <CABb23mt5PFB+sAte8f-cL4Hoivpnhvfo9+SR-wCJmBUv_d8H_Q@mail.gmail.com>

Sorry. I am NOT sure a single pyraf without iraf can work, although there
is something here.


On Wed, Aug 13, 2014 at 11:32 PM, gonghang.naoc <ghang.naoc at gmail.com>
wrote:

> I installed both long time ago. I am sure a single pyraf without iraf can
> work, although there is a something here
> http://www.stsci.edu/institute/software_hardware/pyraf
> 'PyRAF can be installed along with an existing IRAF installation'
> That means pyraf can work alone?
>
>
>
> On Wed, Aug 13, 2014 at 11:22 PM, Brandon Doyle <bjd2385 at rit.edu> wrote:
>
>> I've been looking into PyRAF...so it requires that you have IRAF
>> installed on your computer?
>>
>>
>> On Wed, Aug 13, 2014 at 11:21 AM, gonghang.naoc <ghang.naoc at gmail.com>
>> wrote:
>>
>>> Yes,I need it. I am thinking about which 'iraf' I should use, the
>>> standalone version of NOAO, Ureka or pyraf?
>>>
>>>
>>> On Wed, Aug 13, 2014 at 11:15 PM, Perry Greenfield <
>>> stsci.perry at gmail.com> wrote:
>>>
>>>> So you don't really need IRAF? Or are you installing that separately
>>>> (and layering pyraf onto anaconda)?
>>>>
>>>> Perry
>>>>
>>>> On Aug 13, 2014, at 11:13 AM, gonghang.naoc wrote:
>>>>
>>>> > Hi Tom, Erik,
>>>> > Thank you both. Glad to hear there is a simple choice. I will stick
>>>> with Anaconda.
>>>> > best
>>>> > hang
>>>> >
>>>> >
>>>> > On Wed, Aug 13, 2014 at 10:25 PM, Erik Bray <embray at stsci.edu> wrote:
>>>> > On 08/13/2014 02:53 AM, Thomas Robitaille wrote:
>>>> > > Hi Hang,
>>>> > >
>>>> > > I doubt you will get a single answer here, but I think Anaconda is
>>>> now
>>>> > > widely thought to be a good solution for a generic Scientific Python
>>>> > > installation, but Ureka is probably what you want since you also
>>>> want IRAF:
>>>> > >
>>>> > > http://ssb.stsci.edu/ureka/
>>>> > >
>>>> > > http://ssb.stsci.edu/ureka/1.4.1/docs/components.html
>>>> >
>>>> > As an aside, you also listed separately Numpy, SciPy, EPD, Ureka, and
>>>> Anaconda.
>>>> >
>>>> > First of all EPD no longer exists as such and now is called Canopy.
>>>>  All of
>>>> > Canopy, Anaconda, and Ureka are standalone scientific Python
>>>> *distributions*,
>>>> > each with their own copies of Python itself, Numpy, SciPy, and many
>>>> other
>>>> > popular packages.  In principle they can all coexist on your system,
>>>> though if
>>>> > you have to ask I'd recommend deciding which one best suits your
>>>> needs and
>>>> > sticking with just the one.
>>>> >
>>>> > As Tom said, if you need IRAF you should use Ureka, as it's the only
>>>> scientific
>>>> > Python distribution developed specifically for the Astronomy
>>>> community and that
>>>> > includes IRAF and Pyraf.  Full disclosure: I work for STScI which is
>>>> the primary
>>>> > contributor to Ureka, but I don't personally have much connection to
>>>> the project
>>>> > and don't use it personally.  I hear it works pretty well though.
>>>> >
>>>> > Erik
>>>> >
>>>> > >
>>>> > > gonghang.naoc wrote:
>>>> > >> Hi,
>>>> > >> I reinstalled my system just now. The previsous system had a mess
>>>> of
>>>> > >> python modules with chaotic dependency. Could somebody please give
>>>> me a
>>>> > >> simple list to instll? Potentially I need numpy,scipy,epd,
>>>> > >> ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
>>>> > >>
>>>> > >> A simple and versatile combo is the best.
>>>> > >>
>>>> > >> Thanks.
>>>> > >> best
>>>> > >>
>>>> > >> hang
>>>> > >>
>>>> > >>
>>>> > >> _______________________________________________
>>>> > >> AstroPy mailing list
>>>> > >> AstroPy at scipy.org
>>>> > >> http://mail.scipy.org/mailman/listinfo/astropy
>>>> > > _______________________________________________
>>>> > > AstroPy mailing list
>>>> > > AstroPy at scipy.org
>>>> > > http://mail.scipy.org/mailman/listinfo/astropy
>>>> > >
>>>> >
>>>> > _______________________________________________
>>>> > AstroPy mailing list
>>>> > AstroPy at scipy.org
>>>> > http://mail.scipy.org/mailman/listinfo/astropy
>>>> >
>>>> > _______________________________________________
>>>> > AstroPy mailing list
>>>> > AstroPy at scipy.org
>>>> > http://mail.scipy.org/mailman/listinfo/astropy
>>>>
>>>> _______________________________________________
>>>> AstroPy mailing list
>>>> AstroPy at scipy.org
>>>> http://mail.scipy.org/mailman/listinfo/astropy
>>>>
>>>
>>>
>>> _______________________________________________
>>> AstroPy mailing list
>>> AstroPy at scipy.org
>>> http://mail.scipy.org/mailman/listinfo/astropy
>>>
>>>
>>
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140813/3c93c1c9/attachment.html>

From bjd2385 at rit.edu  Wed Aug 13 11:47:06 2014
From: bjd2385 at rit.edu (Brandon Doyle)
Date: Wed, 13 Aug 2014 11:47:06 -0400
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <CABb23mt5PFB+sAte8f-cL4Hoivpnhvfo9+SR-wCJmBUv_d8H_Q@mail.gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<53EB0B6C.6060703@gmail.com> <53EB7570.4020003@stsci.edu>
	<CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>
	<4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>
	<CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>
	<CAA-aB-b+pKD7V_1Z5odD3coij9MVV8Djj1mx6YPFrx1arCv5iQ@mail.gmail.com>
	<CABb23msY_otMkN7aMZeFukLVD1eQmZ4NR+Aj071Ti8pbugz3Fg@mail.gmail.com>
	<CABb23mt5PFB+sAte8f-cL4Hoivpnhvfo9+SR-wCJmBUv_d8H_Q@mail.gmail.com>
Message-ID: <CAA-aB-ZdLQEESh_Mx2OdL3gzZ2P2mZUHZ1f+9j2Mf8OWuKK7hQ@mail.gmail.com>

I think the best thing I can do is simply to try it on one of the servers
at CIS...I'll send along the results.


On Wed, Aug 13, 2014 at 11:34 AM, gonghang.naoc <ghang.naoc at gmail.com>
wrote:

> Sorry. I am NOT sure a single pyraf without iraf can work, although there
> is something here.
>
>
> On Wed, Aug 13, 2014 at 11:32 PM, gonghang.naoc <ghang.naoc at gmail.com>
> wrote:
>
>> I installed both long time ago. I am sure a single pyraf without iraf can
>> work, although there is a something here
>> http://www.stsci.edu/institute/software_hardware/pyraf
>> 'PyRAF can be installed along with an existing IRAF installation'
>> That means pyraf can work alone?
>>
>>
>>
>> On Wed, Aug 13, 2014 at 11:22 PM, Brandon Doyle <bjd2385 at rit.edu> wrote:
>>
>>> I've been looking into PyRAF...so it requires that you have IRAF
>>> installed on your computer?
>>>
>>>
>>> On Wed, Aug 13, 2014 at 11:21 AM, gonghang.naoc <ghang.naoc at gmail.com>
>>> wrote:
>>>
>>>> Yes,I need it. I am thinking about which 'iraf' I should use, the
>>>> standalone version of NOAO, Ureka or pyraf?
>>>>
>>>>
>>>> On Wed, Aug 13, 2014 at 11:15 PM, Perry Greenfield <
>>>> stsci.perry at gmail.com> wrote:
>>>>
>>>>> So you don't really need IRAF? Or are you installing that separately
>>>>> (and layering pyraf onto anaconda)?
>>>>>
>>>>> Perry
>>>>>
>>>>> On Aug 13, 2014, at 11:13 AM, gonghang.naoc wrote:
>>>>>
>>>>> > Hi Tom, Erik,
>>>>> > Thank you both. Glad to hear there is a simple choice. I will stick
>>>>> with Anaconda.
>>>>> > best
>>>>> > hang
>>>>> >
>>>>> >
>>>>> > On Wed, Aug 13, 2014 at 10:25 PM, Erik Bray <embray at stsci.edu>
>>>>> wrote:
>>>>> > On 08/13/2014 02:53 AM, Thomas Robitaille wrote:
>>>>> > > Hi Hang,
>>>>> > >
>>>>> > > I doubt you will get a single answer here, but I think Anaconda is
>>>>> now
>>>>> > > widely thought to be a good solution for a generic Scientific
>>>>> Python
>>>>> > > installation, but Ureka is probably what you want since you also
>>>>> want IRAF:
>>>>> > >
>>>>> > > http://ssb.stsci.edu/ureka/
>>>>> > >
>>>>> > > http://ssb.stsci.edu/ureka/1.4.1/docs/components.html
>>>>> >
>>>>> > As an aside, you also listed separately Numpy, SciPy, EPD, Ureka,
>>>>> and Anaconda.
>>>>> >
>>>>> > First of all EPD no longer exists as such and now is called Canopy.
>>>>>  All of
>>>>> > Canopy, Anaconda, and Ureka are standalone scientific Python
>>>>> *distributions*,
>>>>> > each with their own copies of Python itself, Numpy, SciPy, and many
>>>>> other
>>>>> > popular packages.  In principle they can all coexist on your system,
>>>>> though if
>>>>> > you have to ask I'd recommend deciding which one best suits your
>>>>> needs and
>>>>> > sticking with just the one.
>>>>> >
>>>>> > As Tom said, if you need IRAF you should use Ureka, as it's the only
>>>>> scientific
>>>>> > Python distribution developed specifically for the Astronomy
>>>>> community and that
>>>>> > includes IRAF and Pyraf.  Full disclosure: I work for STScI which is
>>>>> the primary
>>>>> > contributor to Ureka, but I don't personally have much connection to
>>>>> the project
>>>>> > and don't use it personally.  I hear it works pretty well though.
>>>>> >
>>>>> > Erik
>>>>> >
>>>>> > >
>>>>> > > gonghang.naoc wrote:
>>>>> > >> Hi,
>>>>> > >> I reinstalled my system just now. The previsous system had a mess
>>>>> of
>>>>> > >> python modules with chaotic dependency. Could somebody please
>>>>> give me a
>>>>> > >> simple list to instll? Potentially I need numpy,scipy,epd,
>>>>> > >> ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
>>>>> > >>
>>>>> > >> A simple and versatile combo is the best.
>>>>> > >>
>>>>> > >> Thanks.
>>>>> > >> best
>>>>> > >>
>>>>> > >> hang
>>>>> > >>
>>>>> > >>
>>>>> > >> _______________________________________________
>>>>> > >> AstroPy mailing list
>>>>> > >> AstroPy at scipy.org
>>>>> > >> http://mail.scipy.org/mailman/listinfo/astropy
>>>>> > > _______________________________________________
>>>>> > > AstroPy mailing list
>>>>> > > AstroPy at scipy.org
>>>>> > > http://mail.scipy.org/mailman/listinfo/astropy
>>>>> > >
>>>>> >
>>>>> > _______________________________________________
>>>>> > AstroPy mailing list
>>>>> > AstroPy at scipy.org
>>>>> > http://mail.scipy.org/mailman/listinfo/astropy
>>>>> >
>>>>> > _______________________________________________
>>>>> > AstroPy mailing list
>>>>> > AstroPy at scipy.org
>>>>> > http://mail.scipy.org/mailman/listinfo/astropy
>>>>>
>>>>> _______________________________________________
>>>>> AstroPy mailing list
>>>>> AstroPy at scipy.org
>>>>> http://mail.scipy.org/mailman/listinfo/astropy
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> AstroPy mailing list
>>>> AstroPy at scipy.org
>>>> http://mail.scipy.org/mailman/listinfo/astropy
>>>>
>>>>
>>>
>>> _______________________________________________
>>> AstroPy mailing list
>>> AstroPy at scipy.org
>>> http://mail.scipy.org/mailman/listinfo/astropy
>>>
>>>
>>
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140813/f233ed64/attachment.html>

From hodge at stsci.edu  Wed Aug 13 11:49:14 2014
From: hodge at stsci.edu (Phil Hodge)
Date: Wed, 13 Aug 2014 11:49:14 -0400
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <CABb23mt5PFB+sAte8f-cL4Hoivpnhvfo9+SR-wCJmBUv_d8H_Q@mail.gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>	<53EB0B6C.6060703@gmail.com>
	<53EB7570.4020003@stsci.edu>	<CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>	<4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>	<CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>	<CAA-aB-b+pKD7V_1Z5odD3coij9MVV8Djj1mx6YPFrx1arCv5iQ@mail.gmail.com>	<CABb23msY_otMkN7aMZeFukLVD1eQmZ4NR+Aj071Ti8pbugz3Fg@mail.gmail.com>
	<CABb23mt5PFB+sAte8f-cL4Hoivpnhvfo9+SR-wCJmBUv_d8H_Q@mail.gmail.com>
Message-ID: <53EB88FA.3000108@stsci.edu>

On 08/13/2014 11:34 AM, gonghang.naoc wrote:
> Sorry. I am NOT sure a single pyraf without iraf can work, although 
> there is something here.

If you want to run IRAF tasks, you need IRAF.  If you install both IRAF 
and PyRAF, you'll be able to run IRAF tasks either via the IRAF cl or 
via PyRAF.

Phil


From sontag at stsci.edu  Wed Aug 13 11:48:06 2014
From: sontag at stsci.edu (Chris Sontag)
Date: Wed, 13 Aug 2014 11:48:06 -0400
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <CABb23msY_otMkN7aMZeFukLVD1eQmZ4NR+Aj071Ti8pbugz3Fg@mail.gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>	<53EB0B6C.6060703@gmail.com>
	<53EB7570.4020003@stsci.edu>	<CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>	<4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>	<CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>	<CAA-aB-b+pKD7V_1Z5odD3coij9MVV8Djj1mx6YPFrx1arCv5iQ@mail.gmail.com>
	<CABb23msY_otMkN7aMZeFukLVD1eQmZ4NR+Aj071Ti8pbugz3Fg@mail.gmail.com>
Message-ID: <53EB88B6.2020500@stsci.edu>

PyRAF *can* technically work alone (without IRAF), but this would only be useful in very limited situations.  This is probably not your use case.

PyRAF is not a replacement for IRAF, it is a Python shell around it, and a Python API to it.  It does not include IRAF.

For nearly all such cases, you do actually want IRAF tasks in your work-flow (you would know this, not I), and if so, then you do want to install IRAF.  To install IRAF, simply use Ureka or go to iraf.net.  I agree Ureka works very well for this (though I also work at STScI).

Chris


On 8/13/14 11:32 AM, gonghang.naoc wrote:
> I installed both long time ago. I am sure a single pyraf without iraf can work, although there is a something here
> http://www.stsci.edu/institute/software_hardware/pyraf
> 'PyRAF can be installed along with an existing IRAF installation'
> That means pyraf can work alone?
>
>
> On Wed, Aug 13, 2014 at 11:22 PM, Brandon Doyle <bjd2385 at rit.edu <mailto:bjd2385 at rit.edu>> wrote:
>
>     I've been looking into PyRAF...so it requires that you have IRAF installed on your computer?
>
>
>     On Wed, Aug 13, 2014 at 11:21 AM, gonghang.naoc <ghang.naoc at gmail.com <mailto:ghang.naoc at gmail.com>> wrote:
>
>         Yes,I need it. I am thinking about which 'iraf' I should use, the standalone version of NOAO, Ureka or pyraf?
>
>
>         On Wed, Aug 13, 2014 at 11:15 PM, Perry Greenfield <stsci.perry at gmail.com <mailto:stsci.perry at gmail.com>> wrote:
>
>             So you don't really need IRAF? Or are you installing that separately (and layering pyraf onto anaconda)?
>
>             Perry
>
>             On Aug 13, 2014, at 11:13 AM, gonghang.naoc wrote:
>
>             > Hi Tom, Erik,
>             > Thank you both. Glad to hear there is a simple choice. I will stick with Anaconda.
>             > best
>             > hang
>             >
>             >
>             > On Wed, Aug 13, 2014 at 10:25 PM, Erik Bray <embray at stsci.edu <mailto:embray at stsci.edu>> wrote:
>             > On 08/13/2014 02:53 AM, Thomas Robitaille wrote:
>             > > Hi Hang,
>             > >
>             > > I doubt you will get a single answer here, but I think Anaconda is now
>             > > widely thought to be a good solution for a generic Scientific Python
>             > > installation, but Ureka is probably what you want since you also want IRAF:
>             > >
>             > > http://ssb.stsci.edu/ureka/
>             > >
>             > > http://ssb.stsci.edu/ureka/1.4.1/docs/components.html
>             >
>             > As an aside, you also listed separately Numpy, SciPy, EPD, Ureka, and Anaconda.
>             >
>             > First of all EPD no longer exists as such and now is called Canopy.  All of
>             > Canopy, Anaconda, and Ureka are standalone scientific Python *distributions*,
>             > each with their own copies of Python itself, Numpy, SciPy, and many other
>             > popular packages.  In principle they can all coexist on your system, though if
>             > you have to ask I'd recommend deciding which one best suits your needs and
>             > sticking with just the one.
>             >
>             > As Tom said, if you need IRAF you should use Ureka, as it's the only scientific
>             > Python distribution developed specifically for the Astronomy community and that
>             > includes IRAF and Pyraf.  Full disclosure: I work for STScI which is the primary
>             > contributor to Ureka, but I don't personally have much connection to the project
>             > and don't use it personally.  I hear it works pretty well though.
>             >
>             > Erik
>             >
>             > >
>             > > gonghang.naoc wrote:
>             > >> Hi,
>             > >> I reinstalled my system just now. The previsous system had a mess of
>             > >> python modules with chaotic dependency. Could somebody please give me a
>             > >> simple list to instll? Potentially I need numpy,scipy,epd,
>             > >> ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
>             > >>
>             > >> A simple and versatile combo is the best.
>             > >>
>             > >> Thanks.
>             > >> best
>             > >>
>             > >> hang
>             > >>
>             > >>
>             > >> _______________________________________________
>             > >> AstroPy mailing list
>             > >> AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>             > >> http://mail.scipy.org/mailman/listinfo/astropy
>             > > _______________________________________________
>             > > AstroPy mailing list
>             > > AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>             > > http://mail.scipy.org/mailman/listinfo/astropy
>             > >
>             >
>             > _______________________________________________
>             > AstroPy mailing list
>             > AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>             > http://mail.scipy.org/mailman/listinfo/astropy
>             >
>             > _______________________________________________
>             > AstroPy mailing list
>             > AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>             > http://mail.scipy.org/mailman/listinfo/astropy
>
>             _______________________________________________
>             AstroPy mailing list
>             AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>             http://mail.scipy.org/mailman/listinfo/astropy
>
>
>
>         _______________________________________________
>         AstroPy mailing list
>         AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>         http://mail.scipy.org/mailman/listinfo/astropy
>
>
>
>     _______________________________________________
>     AstroPy mailing list
>     AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>     http://mail.scipy.org/mailman/listinfo/astropy
>
>
>
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140813/ffd0d21b/attachment.html>

From stsci.perry at gmail.com  Wed Aug 13 12:04:31 2014
From: stsci.perry at gmail.com (Perry Greenfield)
Date: Wed, 13 Aug 2014 12:04:31 -0400
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <53EB88B6.2020500@stsci.edu>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>	<53EB0B6C.6060703@gmail.com>
	<53EB7570.4020003@stsci.edu>	<CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>	<4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>	<CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>	<CAA-aB-b+pKD7V_1Z5odD3coij9MVV8Djj1mx6YPFrx1arCv5iQ@mail.gmail.com>
	<CABb23msY_otMkN7aMZeFukLVD1eQmZ4NR+Aj071Ti8pbugz3Fg@mail.gmail.com>
	<53EB88B6.2020500@stsci.edu>
Message-ID: <FBAB3D2F-92A2-41E0-B7D9-A66C04DA8719@gmail.com>


On Aug 13, 2014, at 11:48 AM, Chris Sontag wrote:

> PyRAF *can* technically work alone (without IRAF), but this would only be useful in very limited situations.  This is probably not your use case.
> 
> PyRAF is not a replacement for IRAF, it is a Python shell around it, and a Python API to it.  It does not include IRAF.
> 
> For nearly all such cases, you do actually want IRAF tasks in your work-flow (you would know this, not I), and if so, then you do want to install IRAF.  To install IRAF, simply use Ureka or go to iraf.net.  I agree Ureka works very well for this (though I also work at STScI).
> 
> Chris
> 
To elaborate, the main reason for using PyRAF without IRAF: one wants to construct tasks that run like IRAF tasks from the PyRAF user interface, but actually call python code. This is mainly to retain the the CL-like task invocation syntax (which has some advantages).

Perry

From ghang.naoc at gmail.com  Wed Aug 13 12:07:03 2014
From: ghang.naoc at gmail.com (gonghang.naoc)
Date: Thu, 14 Aug 2014 00:07:03 +0800
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <53EB88B6.2020500@stsci.edu>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<53EB0B6C.6060703@gmail.com> <53EB7570.4020003@stsci.edu>
	<CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>
	<4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>
	<CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>
	<CAA-aB-b+pKD7V_1Z5odD3coij9MVV8Djj1mx6YPFrx1arCv5iQ@mail.gmail.com>
	<CABb23msY_otMkN7aMZeFukLVD1eQmZ4NR+Aj071Ti8pbugz3Fg@mail.gmail.com>
	<53EB88B6.2020500@stsci.edu>
Message-ID: <CABb23mv2-XrAq-pcxn2O1BaRywgg72E5nuQVkmxW5jOQ+aRqng@mail.gmail.com>

oh,two pythoners in one single post. Python should be very popular at STSCI.


On Wed, Aug 13, 2014 at 11:48 PM, Chris Sontag <sontag at stsci.edu> wrote:

>  PyRAF *can* technically work alone (without IRAF), but this would only be
> useful in very limited situations.  This is probably not your use case.
>
> PyRAF is not a replacement for IRAF, it is a Python shell around it, and a
> Python API to it.  It does not include IRAF.
>
> For nearly all such cases, you do actually want IRAF tasks in your
> work-flow (you would know this, not I), and if so, then you do want to
> install IRAF.  To install IRAF, simply use Ureka or go to iraf.net.  I
> agree Ureka works very well for this (though I also work at STScI).
>
> Chris
>
>
>
> On 8/13/14 11:32 AM, gonghang.naoc wrote:
>
>  I installed both long time ago. I am sure a single pyraf without iraf
> can work, although there is a something here
>  http://www.stsci.edu/institute/software_hardware/pyraf
>  'PyRAF can be installed along with an existing IRAF installation'
> That means pyraf can work alone?
>
>
>
> On Wed, Aug 13, 2014 at 11:22 PM, Brandon Doyle <bjd2385 at rit.edu> wrote:
>
>>  I've been looking into PyRAF...so it requires that you have IRAF
>> installed on your computer?
>>
>>
>> On Wed, Aug 13, 2014 at 11:21 AM, gonghang.naoc <ghang.naoc at gmail.com>
>> wrote:
>>
>>> Yes,I need it. I am thinking about which 'iraf' I should use, the
>>> standalone version of NOAO, Ureka or pyraf?
>>>
>>>
>>>  On Wed, Aug 13, 2014 at 11:15 PM, Perry Greenfield <
>>> stsci.perry at gmail.com> wrote:
>>>
>>>> So you don't really need IRAF? Or are you installing that separately
>>>> (and layering pyraf onto anaconda)?
>>>>
>>>> Perry
>>>>
>>>> On Aug 13, 2014, at 11:13 AM, gonghang.naoc wrote:
>>>>
>>>> > Hi Tom, Erik,
>>>> > Thank you both. Glad to hear there is a simple choice. I will stick
>>>> with Anaconda.
>>>> > best
>>>> > hang
>>>> >
>>>> >
>>>> > On Wed, Aug 13, 2014 at 10:25 PM, Erik Bray <embray at stsci.edu> wrote:
>>>> > On 08/13/2014 02:53 AM, Thomas Robitaille wrote:
>>>> > > Hi Hang,
>>>> > >
>>>> > > I doubt you will get a single answer here, but I think Anaconda is
>>>> now
>>>> > > widely thought to be a good solution for a generic Scientific Python
>>>> > > installation, but Ureka is probably what you want since you also
>>>> want IRAF:
>>>> > >
>>>> > > http://ssb.stsci.edu/ureka/
>>>> > >
>>>> > > http://ssb.stsci.edu/ureka/1.4.1/docs/components.html
>>>> >
>>>> > As an aside, you also listed separately Numpy, SciPy, EPD, Ureka, and
>>>> Anaconda.
>>>> >
>>>> > First of all EPD no longer exists as such and now is called Canopy.
>>>>  All of
>>>> > Canopy, Anaconda, and Ureka are standalone scientific Python
>>>> *distributions*,
>>>> > each with their own copies of Python itself, Numpy, SciPy, and many
>>>> other
>>>> > popular packages.  In principle they can all coexist on your system,
>>>> though if
>>>> > you have to ask I'd recommend deciding which one best suits your
>>>> needs and
>>>> > sticking with just the one.
>>>> >
>>>> > As Tom said, if you need IRAF you should use Ureka, as it's the only
>>>> scientific
>>>> > Python distribution developed specifically for the Astronomy
>>>> community and that
>>>> > includes IRAF and Pyraf.  Full disclosure: I work for STScI which is
>>>> the primary
>>>> > contributor to Ureka, but I don't personally have much connection to
>>>> the project
>>>> > and don't use it personally.  I hear it works pretty well though.
>>>> >
>>>> > Erik
>>>> >
>>>> > >
>>>> > > gonghang.naoc wrote:
>>>> > >> Hi,
>>>> > >> I reinstalled my system just now. The previsous system had a mess
>>>> of
>>>> > >> python modules with chaotic dependency. Could somebody please give
>>>> me a
>>>> > >> simple list to instll? Potentially I need numpy,scipy,epd,
>>>> > >> ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
>>>> > >>
>>>> > >> A simple and versatile combo is the best.
>>>> > >>
>>>> > >> Thanks.
>>>> > >> best
>>>> > >>
>>>> > >> hang
>>>> > >>
>>>> > >>
>>>> > >> _______________________________________________
>>>> > >> AstroPy mailing list
>>>> > >> AstroPy at scipy.org
>>>> > >> http://mail.scipy.org/mailman/listinfo/astropy
>>>> > > _______________________________________________
>>>> > > AstroPy mailing list
>>>> > > AstroPy at scipy.org
>>>> > > http://mail.scipy.org/mailman/listinfo/astropy
>>>> > >
>>>> >
>>>> > _______________________________________________
>>>> > AstroPy mailing list
>>>> > AstroPy at scipy.org
>>>> > http://mail.scipy.org/mailman/listinfo/astropy
>>>> >
>>>> > _______________________________________________
>>>> > AstroPy mailing list
>>>> > AstroPy at scipy.org
>>>> > http://mail.scipy.org/mailman/listinfo/astropy
>>>>
>>>> _______________________________________________
>>>> AstroPy mailing list
>>>> AstroPy at scipy.org
>>>> http://mail.scipy.org/mailman/listinfo/astropy
>>>>
>>>
>>>
>>> _______________________________________________
>>> AstroPy mailing list
>>> AstroPy at scipy.org
>>> http://mail.scipy.org/mailman/listinfo/astropy
>>>
>>>
>>
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
>>
>>
>
>
> _______________________________________________
> AstroPy mailing listAstroPy at scipy.orghttp://mail.scipy.org/mailman/listinfo/astropy
>
>
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140814/85d4b337/attachment.html>

From ghang.naoc at gmail.com  Wed Aug 13 12:10:06 2014
From: ghang.naoc at gmail.com (gonghang.naoc)
Date: Thu, 14 Aug 2014 00:10:06 +0800
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <FBAB3D2F-92A2-41E0-B7D9-A66C04DA8719@gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<53EB0B6C.6060703@gmail.com> <53EB7570.4020003@stsci.edu>
	<CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>
	<4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>
	<CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>
	<CAA-aB-b+pKD7V_1Z5odD3coij9MVV8Djj1mx6YPFrx1arCv5iQ@mail.gmail.com>
	<CABb23msY_otMkN7aMZeFukLVD1eQmZ4NR+Aj071Ti8pbugz3Fg@mail.gmail.com>
	<53EB88B6.2020500@stsci.edu>
	<FBAB3D2F-92A2-41E0-B7D9-A66C04DA8719@gmail.com>
Message-ID: <CABb23muWPvDCYS=5VhaRWO1S4LzCPdiotTsDD8Feufj3Ep3UMw@mail.gmail.com>

Is there a trend that people are gradually dropping iraf and switch to
pyraf or something like Ureka?
Why do not we drop that old fashioned cl script and switch to pyraf
completely? Pyraf alone could really  replace iraf completely?


On Thu, Aug 14, 2014 at 12:04 AM, Perry Greenfield <stsci.perry at gmail.com>
wrote:

>
> On Aug 13, 2014, at 11:48 AM, Chris Sontag wrote:
>
> > PyRAF *can* technically work alone (without IRAF), but this would only
> be useful in very limited situations.  This is probably not your use case.
> >
> > PyRAF is not a replacement for IRAF, it is a Python shell around it, and
> a Python API to it.  It does not include IRAF.
> >
> > For nearly all such cases, you do actually want IRAF tasks in your
> work-flow (you would know this, not I), and if so, then you do want to
> install IRAF.  To install IRAF, simply use Ureka or go to iraf.net.  I
> agree Ureka works very well for this (though I also work at STScI).
> >
> > Chris
> >
> To elaborate, the main reason for using PyRAF without IRAF: one wants to
> construct tasks that run like IRAF tasks from the PyRAF user interface, but
> actually call python code. This is mainly to retain the the CL-like task
> invocation syntax (which has some advantages).
>
> Perry
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140814/e512025d/attachment.html>

From stsci.perry at gmail.com  Wed Aug 13 12:16:20 2014
From: stsci.perry at gmail.com (Perry Greenfield)
Date: Wed, 13 Aug 2014 12:16:20 -0400
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <CABb23mv2-XrAq-pcxn2O1BaRywgg72E5nuQVkmxW5jOQ+aRqng@mail.gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<53EB0B6C.6060703@gmail.com> <53EB7570.4020003@stsci.edu>
	<CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>
	<4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>
	<CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>
	<CAA-aB-b+pKD7V_1Z5odD3coij9MVV8Djj1mx6YPFrx1arCv5iQ@mail.gmail.com>
	<CABb23msY_otMkN7aMZeFukLVD1eQmZ4NR+Aj071Ti8pbugz3Fg@mail.gmail.com>
	<53EB88B6.2020500@stsci.edu>
	<CABb23mv2-XrAq-pcxn2O1BaRywgg72E5nuQVkmxW5jOQ+aRqng@mail.gmail.com>
Message-ID: <A9821C91-1CD2-4C3D-A728-79BC9A8E497C@gmail.com>

Oh, it is :-).

We don't write any software for IRAF and haven't in years (though we have much legacy code in it). We are almost entirely focussed on Python these days.

Perry

On Aug 13, 2014, at 12:07 PM, gonghang.naoc wrote:

> oh,two pythoners in one single post. Python should be very popular at STSCI.
> 
> 
> On Wed, Aug 13, 2014 at 11:48 PM, Chris Sontag <sontag at stsci.edu> wrote:
> PyRAF *can* technically work alone (without IRAF), but this would only be useful in very limited situations.  This is probably not your use case.
> 
> PyRAF is not a replacement for IRAF, it is a Python shell around it, and a Python API to it.  It does not include IRAF.
> 
> For nearly all such cases, you do actually want IRAF tasks in your work-flow (you would know this, not I), and if so, then you do want to install IRAF.  To install IRAF, simply use Ureka or go to iraf.net.  I agree Ureka works very well for this (though I also work at STScI).
> 
> Chris
> 
> 
> 
> On 8/13/14 11:32 AM, gonghang.naoc wrote:
>> I installed both long time ago. I am sure a single pyraf without iraf can work, although there is a something here
>> http://www.stsci.edu/institute/software_hardware/pyraf
>> 'PyRAF can be installed along with an existing IRAF installation'
>> That means pyraf can work alone?
>>  
>> 
>> 
>> On Wed, Aug 13, 2014 at 11:22 PM, Brandon Doyle <bjd2385 at rit.edu> wrote:
>> I've been looking into PyRAF...so it requires that you have IRAF installed on your computer?
>> 
>> 
>> On Wed, Aug 13, 2014 at 11:21 AM, gonghang.naoc <ghang.naoc at gmail.com> wrote:
>> Yes,I need it. I am thinking about which 'iraf' I should use, the standalone version of NOAO, Ureka or pyraf?
>> 
>> 
>> On Wed, Aug 13, 2014 at 11:15 PM, Perry Greenfield <stsci.perry at gmail.com> wrote:
>> So you don't really need IRAF? Or are you installing that separately (and layering pyraf onto                                 anaconda)?
>> 
>> Perry
>> 
>> On Aug 13, 2014, at 11:13 AM, gonghang.naoc wrote:
>> 
>> > Hi Tom, Erik,
>> > Thank you both. Glad to hear there is a simple choice. I will stick with Anaconda.
>> > best
>> > hang
>> >
>> >
>> > On Wed, Aug 13, 2014 at 10:25 PM, Erik Bray <embray at stsci.edu> wrote:
>> > On 08/13/2014 02:53 AM, Thomas Robitaille wrote:
>> > > Hi Hang,
>> > >
>> > > I doubt you will get a single answer here, but I think Anaconda is now
>> > > widely thought to be a good solution for a generic Scientific Python
>> > > installation, but Ureka is probably what you want since you also want IRAF:
>> > >
>> > > http://ssb.stsci.edu/ureka/
>> > >
>> > > http://ssb.stsci.edu/ureka/1.4.1/docs/components.html
>> >
>> > As an aside, you also listed separately Numpy, SciPy, EPD, Ureka, and Anaconda.
>> >
>> > First of all EPD no longer exists as such and now is called Canopy.  All of
>> > Canopy, Anaconda, and Ureka are standalone scientific Python *distributions*,
>> > each with their own copies of Python itself, Numpy, SciPy, and many other
>> > popular packages.  In principle they can all coexist on your system, though if
>> > you have to ask I'd recommend deciding which one best suits your needs and
>> > sticking with just the one.
>> >
>> > As Tom said, if you need IRAF you should use Ureka, as it's the only scientific
>> > Python distribution developed specifically for the Astronomy community and that
>> > includes IRAF and Pyraf.  Full disclosure: I work for STScI which is the primary
>> > contributor to Ureka, but I don't personally have much connection to the project
>> > and don't use it personally.  I hear it works pretty well though.
>> >
>> > Erik
>> >
>> > >
>> > > gonghang.naoc wrote:
>> > >> Hi,
>> > >> I reinstalled my system just now. The previsous system had a mess of
>> > >> python modules with chaotic dependency. Could somebody please give me a
>> > >> simple list to instll? Potentially I need numpy,scipy,epd,
>> > >> ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
>> > >>
>> > >> A simple and versatile combo is the best.
>> > >>
>> > >> Thanks.
>> > >> best
>> > >>
>> > >> hang
>> > >>
>> > >>
>> > >> _______________________________________________
>> > >> AstroPy mailing list
>> > >> AstroPy at scipy.org
>> > >> http://mail.scipy.org/mailman/listinfo/astropy
>> > > _______________________________________________
>> > > AstroPy mailing list
>> > > AstroPy at scipy.org
>> > > http://mail.scipy.org/mailman/listinfo/astropy
>> > >
>> >
>> > _______________________________________________
>> > AstroPy mailing list
>> > AstroPy at scipy.org
>> > http://mail.scipy.org/mailman/listinfo/astropy
>> >
>> > _______________________________________________
>> > AstroPy mailing list
>> > AstroPy at scipy.org
>> > http://mail.scipy.org/mailman/listinfo/astropy
>> 
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
>> 
>> 
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
>> 
>> 
>> 
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
>> 
>> 
>> 
>> 
>> _______________________________________________
>> AstroPy mailing list
>> 
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
> 
> 
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
> 
> 
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy



From beaumont at hawaii.edu  Wed Aug 13 16:48:27 2014
From: beaumont at hawaii.edu (Chris Beaumont)
Date: Wed, 13 Aug 2014 16:48:27 -0400
Subject: [AstroPy] [ANN] Glue v0.3, linked data visualization in Python
Message-ID: <CAFP9tKrSH9++zEFmD8FDc9rYxky8Nd9ty4juxw4RyXEkakK3bA@mail.gmail.com>

Hi Everyone,

I'm happy to announce the first formal release of Glue, a library to make
interactive, linked-view visualizations in Python and Matplotlib. You can
find more information about Glue, including demo videos and installation
instructions, at

http://glueviz.org

There is also a mailing list at

https://groups.google.com/forum/#!forum/glue-viz

Some of Glue's highlights include:

- A GUI for creating standard interactive visualizations of images,
spectral data cubes, and catalogs (images, scatterplots, histograms, etc)
- Support for brushing and linking to select subsets
- Deep python integration, making it easy to integrate python-based
workflows into Glue
- Saveable state

While this is the first versioned release for Glue, it has been steadily
developed for the past year. The purpose of this release is to create a
stable reference point, and standard installation option, for new users.
Glue is supported by the Space Telescope Science Institute, Harvard, and
NASA.

Cheers,
Chris Beaumont
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140813/3620aa83/attachment.html>

From ghang.naoc at gmail.com  Thu Aug 14 03:03:52 2014
From: ghang.naoc at gmail.com (gonghang.naoc)
Date: Thu, 14 Aug 2014 15:03:52 +0800
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <53EB8FFA.6020606@stsci.edu>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<53EB0B6C.6060703@gmail.com> <53EB7570.4020003@stsci.edu>
	<CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>
	<4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>
	<CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>
	<CAA-aB-b+pKD7V_1Z5odD3coij9MVV8Djj1mx6YPFrx1arCv5iQ@mail.gmail.com>
	<CABb23msY_otMkN7aMZeFukLVD1eQmZ4NR+Aj071Ti8pbugz3Fg@mail.gmail.com>
	<53EB88B6.2020500@stsci.edu>
	<CABb23mv2-XrAq-pcxn2O1BaRywgg72E5nuQVkmxW5jOQ+aRqng@mail.gmail.com>
	<53EB8FFA.6020606@stsci.edu>
Message-ID: <CABb23mtcfSMSEA4qZLPTLp-H4MJ3eATs35c6cWJ58CaFrRML9Q@mail.gmail.com>

oh....Ureka cost me 1.2G. It includes much less modules than Anaconda,
which only takes 300M.
I find another python distribution released by stsci, the stsci_python.  (
http://www.stsci.edu/institute/software_hardware/pyraf/stsci_python)
Should I drop Ureka and install stsci_python?

On Thu, Aug 14, 2014 at 12:19 AM, Chris Sontag <sontag at stsci.edu> wrote:

>  :-)
>
> Python is good stuff.
>
>
> On 8/13/14 12:07 PM, gonghang.naoc wrote:
>
> oh,two pythoners in one single post. Python should be very popular at
> STSCI.
>
>
> On Wed, Aug 13, 2014 at 11:48 PM, Chris Sontag <sontag at stsci.edu> wrote:
>
>>  PyRAF *can* technically work alone (without IRAF), but this would only
>> be useful in very limited situations.  This is probably not your use case.
>>
>> PyRAF is not a replacement for IRAF, it is a Python shell around it, and
>> a Python API to it.  It does not include IRAF.
>>
>> For nearly all such cases, you do actually want IRAF tasks in your
>> work-flow (you would know this, not I), and if so, then you do want to
>> install IRAF.  To install IRAF, simply use Ureka or go to iraf.net.  I
>> agree Ureka works very well for this (though I also work at STScI).
>>
>> Chris
>>
>>
>>
>> On 8/13/14 11:32 AM, gonghang.naoc wrote:
>>
>>  I installed both long time ago. I am sure a single pyraf without iraf
>> can work, although there is a something here
>>  http://www.stsci.edu/institute/software_hardware/pyraf
>>  'PyRAF can be installed along with an existing IRAF installation'
>> That means pyraf can work alone?
>>
>>
>>
>> On Wed, Aug 13, 2014 at 11:22 PM, Brandon Doyle <bjd2385 at rit.edu> wrote:
>>
>>>  I've been looking into PyRAF...so it requires that you have IRAF
>>> installed on your computer?
>>>
>>>
>>> On Wed, Aug 13, 2014 at 11:21 AM, gonghang.naoc <ghang.naoc at gmail.com>
>>> wrote:
>>>
>>>> Yes,I need it. I am thinking about which 'iraf' I should use, the
>>>> standalone version of NOAO, Ureka or pyraf?
>>>>
>>>>
>>>>  On Wed, Aug 13, 2014 at 11:15 PM, Perry Greenfield <
>>>> stsci.perry at gmail.com> wrote:
>>>>
>>>>> So you don't really need IRAF? Or are you installing that separately
>>>>> (and layering pyraf onto anaconda)?
>>>>>
>>>>> Perry
>>>>>
>>>>> On Aug 13, 2014, at 11:13 AM, gonghang.naoc wrote:
>>>>>
>>>>> > Hi Tom, Erik,
>>>>> > Thank you both. Glad to hear there is a simple choice. I will stick
>>>>> with Anaconda.
>>>>> > best
>>>>> > hang
>>>>> >
>>>>> >
>>>>> > On Wed, Aug 13, 2014 at 10:25 PM, Erik Bray <embray at stsci.edu>
>>>>> wrote:
>>>>> > On 08/13/2014 02:53 AM, Thomas Robitaille wrote:
>>>>> > > Hi Hang,
>>>>> > >
>>>>> > > I doubt you will get a single answer here, but I think Anaconda is
>>>>> now
>>>>> > > widely thought to be a good solution for a generic Scientific
>>>>> Python
>>>>> > > installation, but Ureka is probably what you want since you also
>>>>> want IRAF:
>>>>> > >
>>>>> > > http://ssb.stsci.edu/ureka/
>>>>> > >
>>>>> > > http://ssb.stsci.edu/ureka/1.4.1/docs/components.html
>>>>> >
>>>>> > As an aside, you also listed separately Numpy, SciPy, EPD, Ureka,
>>>>> and Anaconda.
>>>>> >
>>>>> > First of all EPD no longer exists as such and now is called Canopy.
>>>>>  All of
>>>>> > Canopy, Anaconda, and Ureka are standalone scientific Python
>>>>> *distributions*,
>>>>> > each with their own copies of Python itself, Numpy, SciPy, and many
>>>>> other
>>>>> > popular packages.  In principle they can all coexist on your system,
>>>>> though if
>>>>> > you have to ask I'd recommend deciding which one best suits your
>>>>> needs and
>>>>> > sticking with just the one.
>>>>> >
>>>>> > As Tom said, if you need IRAF you should use Ureka, as it's the only
>>>>> scientific
>>>>> > Python distribution developed specifically for the Astronomy
>>>>> community and that
>>>>> > includes IRAF and Pyraf.  Full disclosure: I work for STScI which is
>>>>> the primary
>>>>> > contributor to Ureka, but I don't personally have much connection to
>>>>> the project
>>>>> > and don't use it personally.  I hear it works pretty well though.
>>>>> >
>>>>> > Erik
>>>>> >
>>>>> > >
>>>>> > > gonghang.naoc wrote:
>>>>> > >> Hi,
>>>>> > >> I reinstalled my system just now. The previsous system had a mess
>>>>> of
>>>>> > >> python modules with chaotic dependency. Could somebody please
>>>>> give me a
>>>>> > >> simple list to instll? Potentially I need numpy,scipy,epd,
>>>>> > >> ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
>>>>> > >>
>>>>> > >> A simple and versatile combo is the best.
>>>>> > >>
>>>>> > >> Thanks.
>>>>> > >> best
>>>>> > >>
>>>>> > >> hang
>>>>> > >>
>>>>> > >>
>>>>> > >> _______________________________________________
>>>>> > >> AstroPy mailing list
>>>>> > >> AstroPy at scipy.org
>>>>> > >> http://mail.scipy.org/mailman/listinfo/astropy
>>>>> > > _______________________________________________
>>>>> > > AstroPy mailing list
>>>>> > > AstroPy at scipy.org
>>>>> > > http://mail.scipy.org/mailman/listinfo/astropy
>>>>> > >
>>>>> >
>>>>> > _______________________________________________
>>>>> > AstroPy mailing list
>>>>> > AstroPy at scipy.org
>>>>> > http://mail.scipy.org/mailman/listinfo/astropy
>>>>> >
>>>>> > _______________________________________________
>>>>> > AstroPy mailing list
>>>>> > AstroPy at scipy.org
>>>>> > http://mail.scipy.org/mailman/listinfo/astropy
>>>>>
>>>>> _______________________________________________
>>>>> AstroPy mailing list
>>>>> AstroPy at scipy.org
>>>>> http://mail.scipy.org/mailman/listinfo/astropy
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> AstroPy mailing list
>>>> AstroPy at scipy.org
>>>> http://mail.scipy.org/mailman/listinfo/astropy
>>>>
>>>>
>>>
>>> _______________________________________________
>>> AstroPy mailing list
>>> AstroPy at scipy.org
>>> http://mail.scipy.org/mailman/listinfo/astropy
>>>
>>>
>>
>>
>> _______________________________________________
>> AstroPy mailing listAstroPy at scipy.orghttp://mail.scipy.org/mailman/listinfo/astropy
>>
>>
>>
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
>>
>>
>
>
> _______________________________________________
> AstroPy mailing listAstroPy at scipy.orghttp://mail.scipy.org/mailman/listinfo/astropy
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140814/b3496725/attachment.html>

From embray at stsci.edu  Thu Aug 14 11:35:27 2014
From: embray at stsci.edu (Erik Bray)
Date: Thu, 14 Aug 2014 11:35:27 -0400
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <CABb23mtcfSMSEA4qZLPTLp-H4MJ3eATs35c6cWJ58CaFrRML9Q@mail.gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>	<53EB0B6C.6060703@gmail.com>
	<53EB7570.4020003@stsci.edu>	<CABb23mtAHFTjLTWrqppuLLTXsK2s+cSRPzTY=-0nknpSFbY1Xg@mail.gmail.com>	<4DD5D561-B910-4528-93E8-03DBAB5E81A9@gmail.com>	<CABb23mu6iQ+cRapJ5=BXfBjjPBG_YzfYx9ifb8a0WDNEnoDXhA@mail.gmail.com>	<CAA-aB-b+pKD7V_1Z5odD3coij9MVV8Djj1mx6YPFrx1arCv5iQ@mail.gmail.com>	<CABb23msY_otMkN7aMZeFukLVD1eQmZ4NR+Aj071Ti8pbugz3Fg@mail.gmail.com>	<53EB88B6.2020500@stsci.edu>	<CABb23mv2-XrAq-pcxn2O1BaRywgg72E5nuQVkmxW5jOQ+aRqng@mail.gmail.com>	<53EB8FFA.6020606@stsci.edu>
	<CABb23mtcfSMSEA4qZLPTLp-H4MJ3eATs35c6cWJ58CaFrRML9Q@mail.gmail.com>
Message-ID: <53ECD73F.8010006@stsci.edu>

On 08/14/2014 03:03 AM, gonghang.naoc wrote:
> oh....Ureka cost me 1.2G. It includes much less modules than Anaconda, which
> only takes 300M.
> I find another python distribution released by stsci, the stsci_python.
> (http://www.stsci.edu/institute/software_hardware/pyraf/stsci_python)
> Should I drop Ureka and install stsci_python?

stsci_python is not a Python distribution in the sense that it includes its own 
copy of Python.  stsci_python is just a collection of a handful of Python 
packages, most of which are used internally by STScI software.  It is included 
in Ureka among its other included Python modules:

http://ssb.stsci.edu/ureka/1.0beta5/docs/python_modules.html

You wrote that you need IRAF.  On the copy of Ureka I just downloaded IRAF 
accounts for about 958 MB of the installed files. So if you want IRAF that's a 
cost you have to pay.

Erik



> On Thu, Aug 14, 2014 at 12:19 AM, Chris Sontag <sontag at stsci.edu
> <mailto:sontag at stsci.edu>> wrote:
>
>     :-)
>
>     Python is good stuff.
>
>
>     On 8/13/14 12:07 PM, gonghang.naoc wrote:
>>     oh,two pythoners in one single post. Python should be very popular at STSCI.
>>
>>
>>     On Wed, Aug 13, 2014 at 11:48 PM, Chris Sontag <sontag at stsci.edu
>>     <mailto:sontag at stsci.edu>> wrote:
>>
>>         PyRAF *can* technically work alone (without IRAF), but this would only
>>         be useful in very limited situations.  This is probably not your use case.
>>
>>         PyRAF is not a replacement for IRAF, it is a Python shell around it,
>>         and a Python API to it.  It does not include IRAF.
>>
>>         For nearly all such cases, you do actually want IRAF tasks in your
>>         work-flow (you would know this, not I), and if so, then you do want to
>>         install IRAF.  To install IRAF, simply use Ureka or go to iraf.net
>>         <http://iraf.net>.  I agree Ureka works very well for this (though I
>>         also work at STScI).
>>
>>         Chris
>>
>>
>>
>>         On 8/13/14 11:32 AM, gonghang.naoc wrote:
>>>         I installed both long time ago. I am sure a single pyraf without iraf
>>>         can work, although there is a something here
>>>         http://www.stsci.edu/institute/software_hardware/pyraf
>>>         'PyRAF can be installed along with an existing IRAF installation'
>>>         That means pyraf can work alone?
>>>
>>>
>>>         On Wed, Aug 13, 2014 at 11:22 PM, Brandon Doyle <bjd2385 at rit.edu
>>>         <mailto:bjd2385 at rit.edu>> wrote:
>>>
>>>             I've been looking into PyRAF...so it requires that you have IRAF
>>>             installed on your computer?
>>>
>>>
>>>             On Wed, Aug 13, 2014 at 11:21 AM, gonghang.naoc
>>>             <ghang.naoc at gmail.com <mailto:ghang.naoc at gmail.com>> wrote:
>>>
>>>                 Yes,I need it. I am thinking about which 'iraf' I should use,
>>>                 the standalone version of NOAO, Ureka or pyraf?
>>>
>>>
>>>                 On Wed, Aug 13, 2014 at 11:15 PM, Perry Greenfield
>>>                 <stsci.perry at gmail.com <mailto:stsci.perry at gmail.com>> wrote:
>>>
>>>                     So you don't really need IRAF? Or are you installing that
>>>                     separately (and layering pyraf onto anaconda)?
>>>
>>>                     Perry
>>>
>>>                     On Aug 13, 2014, at 11:13 AM, gonghang.naoc wrote:
>>>
>>>                     > Hi Tom, Erik,
>>>                     > Thank you both. Glad to hear there is a simple choice.
>>>                     I will stick with Anaconda.
>>>                     > best
>>>                     > hang
>>>                     >
>>>                     >
>>>                     > On Wed, Aug 13, 2014 at 10:25 PM, Erik Bray
>>>                     <embray at stsci.edu <mailto:embray at stsci.edu>> wrote:
>>>                     > On 08/13/2014 02:53 AM, Thomas Robitaille wrote:
>>>                     > > Hi Hang,
>>>                     > >
>>>                     > > I doubt you will get a single answer here, but I
>>>                     think Anaconda is now
>>>                     > > widely thought to be a good solution for a generic
>>>                     Scientific Python
>>>                     > > installation, but Ureka is probably what you want
>>>                     since you also want IRAF:
>>>                     > >
>>>                     > > http://ssb.stsci.edu/ureka/
>>>                     > >
>>>                     > > http://ssb.stsci.edu/ureka/1.4.1/docs/components.html
>>>                     >
>>>                     > As an aside, you also listed separately Numpy, SciPy,
>>>                     EPD, Ureka, and Anaconda.
>>>                     >
>>>                     > First of all EPD no longer exists as such and now is
>>>                     called Canopy.  All of
>>>                     > Canopy, Anaconda, and Ureka are standalone scientific
>>>                     Python *distributions*,
>>>                     > each with their own copies of Python itself, Numpy,
>>>                     SciPy, and many other
>>>                     > popular packages.  In principle they can all coexist on
>>>                     your system, though if
>>>                     > you have to ask I'd recommend deciding which one best
>>>                     suits your needs and
>>>                     > sticking with just the one.
>>>                     >
>>>                     > As Tom said, if you need IRAF you should use Ureka, as
>>>                     it's the only scientific
>>>                     > Python distribution developed specifically for the
>>>                     Astronomy community and that
>>>                     > includes IRAF and Pyraf.  Full disclosure: I work for
>>>                     STScI which is the primary
>>>                     > contributor to Ureka, but I don't personally have much
>>>                     connection to the project
>>>                     > and don't use it personally.  I hear it works pretty
>>>                     well though.
>>>                     >
>>>                     > Erik
>>>                     >
>>>                     > >
>>>                     > > gonghang.naoc wrote:
>>>                     > >> Hi,
>>>                     > >> I reinstalled my system just now. The previsous
>>>                     system had a mess of
>>>                     > >> python modules with chaotic dependency. Could
>>>                     somebody please give me a
>>>                     > >> simple list to instll? Potentially I need
>>>                     numpy,scipy,epd,
>>>                     > >> ureka,iraf,pyraf, anaconda or somethig else which
>>>                     you can suggest.
>>>                     > >>
>>>                     > >> A simple and versatile combo is the best.
>>>                     > >>
>>>                     > >> Thanks.
>>>                     > >> best
>>>                     > >>
>>>                     > >> hang
>>>                     > >>
>>>                     > >>
>>>                     > >> _______________________________________________
>>>                     > >> AstroPy mailing list
>>>                     > >> AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>>>                     > >> http://mail.scipy.org/mailman/listinfo/astropy
>>>                     > > _______________________________________________
>>>                     > > AstroPy mailing list
>>>                     > > AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>>>                     > > http://mail.scipy.org/mailman/listinfo/astropy
>>>                     > >
>>>                     >
>>>                     > _______________________________________________
>>>                     > AstroPy mailing list
>>>                     > AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>>>                     > http://mail.scipy.org/mailman/listinfo/astropy
>>>                     >
>>>                     > _______________________________________________
>>>                     > AstroPy mailing list
>>>                     > AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>>>                     > http://mail.scipy.org/mailman/listinfo/astropy
>>>
>>>                     _______________________________________________
>>>                     AstroPy mailing list
>>>                     AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>>>                     http://mail.scipy.org/mailman/listinfo/astropy
>>>
>>>
>>>
>>>                 _______________________________________________
>>>                 AstroPy mailing list
>>>                 AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>>>                 http://mail.scipy.org/mailman/listinfo/astropy
>>>
>>>
>>>
>>>             _______________________________________________
>>>             AstroPy mailing list
>>>             AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>>>             http://mail.scipy.org/mailman/listinfo/astropy
>>>
>>>
>>>
>>>
>>>         _______________________________________________
>>>         AstroPy mailing list
>>>         AstroPy at scipy.org  <mailto:AstroPy at scipy.org>
>>>         http://mail.scipy.org/mailman/listinfo/astropy
>>
>>
>>         _______________________________________________
>>         AstroPy mailing list
>>         AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>>         http://mail.scipy.org/mailman/listinfo/astropy
>>
>>
>>
>>
>>     _______________________________________________
>>     AstroPy mailing list
>>     AstroPy at scipy.org  <mailto:AstroPy at scipy.org>
>>     http://mail.scipy.org/mailman/listinfo/astropy
>
>
>
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>



From astropy at liska.ath.cx  Thu Aug 14 14:12:10 2014
From: astropy at liska.ath.cx (=?utf-8?B?0J5s0LUg0IV0ctC10ZbRgWjQtXI=?=)
Date: Thu, 14 Aug 2014 20:12:10 +0200
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
Message-ID: <87bnrnos91.fsf@baikal.ole.ath.cx>

"gonghang.naoc" <ghang.naoc at gmail.com> writes:
> I reinstalled my system just now. The previsous system had a mess of
> python modules with chaotic dependency. Could somebody please give me
> a simple list to instll? Potentially I need numpy,scipy,epd,
> ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
> A simple and versatile combo is the best.

Since this was not mentioned yet: If you are using a Linux distribution
(Debian, Ubuntu, Fedora, Mageia etc.) it may be worth checking whether
the packages you need are already there. Then the simplest solution
would be a "apt-get install whatever-you-like" and be lucky. The nice
thing is that it then works (well, in theory) out of the box. And is
updated automatically (or not, if you manually put the package on hold).

If the package you need is still not there and you want to help us
completing the selection, you are very welcome. Even if you don't want
to do the packaging yourself, it is useful to know, which packages are
actually needed.

Best regards

Ole


From ghang.naoc at gmail.com  Thu Aug 14 22:45:00 2014
From: ghang.naoc at gmail.com (gonghang.naoc)
Date: Fri, 15 Aug 2014 10:45:00 +0800
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <87bnrnos91.fsf@baikal.ole.ath.cx>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<87bnrnos91.fsf@baikal.ole.ath.cx>
Message-ID: <CABb23mvh507V-kbRRZup3odANN43aYub28mnQJ6Sb0iLdtJ3MA@mail.gmail.com>

Thank you all. Now I realize Anaconda+NOAO's iraf+pyraf, this combo is
enough for me, temporarily.

hang


On Fri, Aug 15, 2014 at 2:12 AM, ?l? ?tr???h?r <astropy at liska.ath.cx> wrote:

> "gonghang.naoc" <ghang.naoc at gmail.com> writes:
> > I reinstalled my system just now. The previsous system had a mess of
> > python modules with chaotic dependency. Could somebody please give me
> > a simple list to instll? Potentially I need numpy,scipy,epd,
> > ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
> > A simple and versatile combo is the best.
>
> Since this was not mentioned yet: If you are using a Linux distribution
> (Debian, Ubuntu, Fedora, Mageia etc.) it may be worth checking whether
> the packages you need are already there. Then the simplest solution
> would be a "apt-get install whatever-you-like" and be lucky. The nice
> thing is that it then works (well, in theory) out of the box. And is
> updated automatically (or not, if you manually put the package on hold).
>
> If the package you need is still not there and you want to help us
> completing the selection, you are very welcome. Even if you don't want
> to do the packaging yourself, it is useful to know, which packages are
> actually needed.
>
> Best regards
>
> Ole
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140815/aaeac7c0/attachment.html>

From bjd2385 at rit.edu  Fri Aug 15 04:47:08 2014
From: bjd2385 at rit.edu (Brandon Doyle)
Date: Fri, 15 Aug 2014 04:47:08 -0400
Subject: [AstroPy] Buridan's ass-----what combo should I choose?
In-Reply-To: <CABb23mvh507V-kbRRZup3odANN43aYub28mnQJ6Sb0iLdtJ3MA@mail.gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<87bnrnos91.fsf@baikal.ole.ath.cx>
	<CABb23mvh507V-kbRRZup3odANN43aYub28mnQJ6Sb0iLdtJ3MA@mail.gmail.com>
Message-ID: <CAA-aB-bhb_SPHm7RT4wEEXtmE_L09weyrVBxbBwDSWdqZ5nDJw@mail.gmail.com>

Hi all,

Problem using Astropy this morning. Input code:

# Import Modules:
>
> import aplpy
>
> import pyfits
>
> from numpy import *
>
> import matplotlib as plt
>
> import montage as montage_wrapper
>
> import PIL
>
>
>> # Begin convert images w/header/pyfits
>
> r = pyfits.open('3c324IR.fits')
>
> b = pyfits.open('3c324UVIS.fits')
>
> g = pyfits.open('3c5GHZ.fits')
>
>
>> r.info()
>
> g.info()
>
> b.info()
>
>
>> print(r[1].header)
>
> print(g[1].header)
>
> print(b[1].header)
>
>
>> r1 = r[1].data
>
> g1 = g[0].data
>
> b1 = b[1].data
>
>
>> hdu = pyfits.PrimaryHDU(r1)
>
> hdulist = pyfits.HDUList([hdu])
>
> hdulist.writeto('r.fits')
>
>
>> hdu = pyfits.PrimaryHDU(g1)
>
> hdulist = pyfits.HDUList([hdu])
>
> hdulist.writeto('g.fits')
>
>
>> hdu = pyfits.PrimaryHDU(b1)
>
> hdulist = pyfits.HDUList([hdu])
>
> hdulist.writeto('b.fits')
>
>
>> # Begin Code:
>
>
>> aplpy.make_rgb_cube(['r.fits','g.fits','b.fits'], '3c_324_rgb.fits')
>
>
>> aplpy.make_rgb_image('3c_324_rgb.fits','3c_324_rgb.png')
>
>
>> f = aplpy.FITSFigure('3c_324_rgb.fits')
>
> f.show_rgb()
>
> f.save('3c_324_rgb2.png')
>
>
>> print 'END'
>
>
?output from server:

?

Traceback (most recent call last):

  File "test9.py", line 47, in <module>

    aplpy.make_rgb_cube(['r.fits','g.fits','b.fits'], '3c_324_rgb.fits')

  File "/usr/local/lib/python2.7/dist-packages/aplpy/rgb.py", line 309, in
> make_rgb_cube

    montage.mMakeHdr(images_raw_tbl, header_hdr, north_aligned=north,
> system=system, equinox=equinox)

  File
> "/usr/local/lib/python2.7/dist-packages/montage_wrapper/commands.py", line
> 1468, in mMakeHdr

    return status.parse_struct("mMakeHdr", p.stdout.read().strip())

  File "/usr/local/lib/python2.7/dist-packages/montage_wrapper/status.py",
> line 33, in parse_struct

    result = Struct(command, string)

  File "/usr/local/lib/python2.7/dist-packages/montage_wrapper/status.py",
> line 70, in __init__

    raise MontageError("%s: %s" % (command, self.msg))

montage_wrapper.status.MontageError: mMakeHdr: Invalid table file:
> /tmp/tmpmyYyN7/images_raw.tbl


?I'm not sure what to make of it...any ideas?

Brandon Doyle?



On Thu, Aug 14, 2014 at 10:45 PM, gonghang.naoc <ghang.naoc at gmail.com>
wrote:

> Thank you all. Now I realize Anaconda+NOAO's iraf+pyraf, this combo is
> enough for me, temporarily.
>
> hang
>
>
> On Fri, Aug 15, 2014 at 2:12 AM, ?l? ?tr???h?r <astropy at liska.ath.cx>
> wrote:
>
>> "gonghang.naoc" <ghang.naoc at gmail.com> writes:
>> > I reinstalled my system just now. The previsous system had a mess of
>> > python modules with chaotic dependency. Could somebody please give me
>> > a simple list to instll? Potentially I need numpy,scipy,epd,
>> > ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
>> > A simple and versatile combo is the best.
>>
>> Since this was not mentioned yet: If you are using a Linux distribution
>> (Debian, Ubuntu, Fedora, Mageia etc.) it may be worth checking whether
>> the packages you need are already there. Then the simplest solution
>> would be a "apt-get install whatever-you-like" and be lucky. The nice
>> thing is that it then works (well, in theory) out of the box. And is
>> updated automatically (or not, if you manually put the package on hold).
>>
>> If the package you need is still not there and you want to help us
>> completing the selection, you are very welcome. Even if you don't want
>> to do the packaging yourself, it is useful to know, which packages are
>> actually needed.
>>
>> Best regards
>>
>> Ole
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
>>
>
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140815/cc50ac44/attachment.html>

From thomas.robitaille at gmail.com  Fri Aug 15 05:51:11 2014
From: thomas.robitaille at gmail.com (Thomas Robitaille)
Date: Fri, 15 Aug 2014 11:51:11 +0200
Subject: [AstroPy] Montage issue
In-Reply-To: <CAA-aB-bhb_SPHm7RT4wEEXtmE_L09weyrVBxbBwDSWdqZ5nDJw@mail.gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<87bnrnos91.fsf@baikal.ole.ath.cx>
	<CABb23mvh507V-kbRRZup3odANN43aYub28mnQJ6Sb0iLdtJ3MA@mail.gmail.com>
	<CAA-aB-bhb_SPHm7RT4wEEXtmE_L09weyrVBxbBwDSWdqZ5nDJw@mail.gmail.com>
Message-ID: <53EDD80F.3060104@gmail.com>

Hi Brandon,

Would it be possible for you to send me the files off-list, so I can
take a look at the issue?

Note that I have renamed this thread since it is not related to the
thread to which it was posted to.

Cheers,
Tom

Brandon Doyle wrote:
> Hi all,
> 
> Problem using Astropy this morning. Input code:
> 
>         # Import Modules:
> 
>         import aplpy
> 
>         import pyfits
> 
>         from numpy import *
> 
>         import matplotlib as plt
> 
>         import montage as montage_wrapper
> 
>         import PIL
> 
> 
>         # Begin convert images w/header/pyfits
> 
>         r = pyfits.open('3c324IR.fits')
> 
>         b = pyfits.open('3c324UVIS.fits')
> 
>         g = pyfits.open('3c5GHZ.fits')
> 
> 
>         r.info <http://r.info>()
> 
>         g.info <http://g.info>()
> 
>         b.info <http://b.info>()
> 
> 
>         print(r[1].header)
> 
>         print(g[1].header)
> 
>         print(b[1].header)
> 
> 
>         r1 = r[1].data
> 
>         g1 = g[0].data
> 
>         b1 = b[1].data
> 
> 
>         hdu = pyfits.PrimaryHDU(r1)
> 
>         hdulist = pyfits.HDUList([hdu])
> 
>         hdulist.writeto('r.fits')
> 
> 
>         hdu = pyfits.PrimaryHDU(g1)
> 
>         hdulist = pyfits.HDUList([hdu])
> 
>         hdulist.writeto('g.fits')
> 
> 
>         hdu = pyfits.PrimaryHDU(b1)
> 
>         hdulist = pyfits.HDUList([hdu])
> 
>         hdulist.writeto('b.fits')
> 
> 
>         # Begin Code:
> 
> 
>         aplpy.make_rgb_cube(['r.fits','g.fits','b.fits'], '3c_324_rgb.fits')
> 
> 
>         aplpy.make_rgb_image('3c_324_rgb.fits','3c_324_rgb.png')
> 
> 
>         f = aplpy.FITSFigure('3c_324_rgb.fits')
> 
>         f.show_rgb()
> 
>         f.save('3c_324_rgb2.png')
> 
> 
>         print 'END'
> 
> 
> ?output from server:
> 
>     ?
> 
>     Traceback (most recent call last):
> 
>       File "test9.py", line 47, in <module>
> 
>         aplpy.make_rgb_cube(['r.fits','g.fits','b.fits'], '3c_324_rgb.fits')
> 
>       File "/usr/local/lib/python2.7/dist-packages/aplpy/rgb.py", line
>     309, in make_rgb_cube
> 
>         montage.mMakeHdr(images_raw_tbl, header_hdr,
>     north_aligned=north, system=system, equinox=equinox)
> 
>       File
>     "/usr/local/lib/python2.7/dist-packages/montage_wrapper/commands.py", line
>     1468, in mMakeHdr
> 
>         return status.parse_struct("mMakeHdr", p.stdout.read().strip())
> 
>       File
>     "/usr/local/lib/python2.7/dist-packages/montage_wrapper/status.py",
>     line 33, in parse_struct
> 
>         result = Struct(command, string)
> 
>       File
>     "/usr/local/lib/python2.7/dist-packages/montage_wrapper/status.py",
>     line 70, in __init__
> 
>         raise MontageError("%s: %s" % (command, self.msg))
> 
>     montage_wrapper.status.MontageError: mMakeHdr: Invalid table file:
>     /tmp/tmpmyYyN7/images_raw.tbl
> 
> 
> ?I'm not sure what to make of it...any ideas?
> 
> Brandon Doyle?
> 
> 
> 
> On Thu, Aug 14, 2014 at 10:45 PM, gonghang.naoc <ghang.naoc at gmail.com
> <mailto:ghang.naoc at gmail.com>> wrote:
> 
>     Thank you all. Now I realize Anaconda+NOAO's iraf+pyraf, this combo
>     is enough for me, temporarily.
>      
>     hang
> 
> 
>     On Fri, Aug 15, 2014 at 2:12 AM, ?l? ?tr???h?r <astropy at liska.ath.cx
>     <mailto:astropy at liska.ath.cx>> wrote:
> 
>         "gonghang.naoc" <ghang.naoc at gmail.com
>         <mailto:ghang.naoc at gmail.com>> writes:
>         > I reinstalled my system just now. The previsous system had a
>         mess of
>         > python modules with chaotic dependency. Could somebody please
>         give me
>         > a simple list to instll? Potentially I need numpy,scipy,epd,
>         > ureka,iraf,pyraf, anaconda or somethig else which you can suggest.
>         > A simple and versatile combo is the best.
> 
>         Since this was not mentioned yet: If you are using a Linux
>         distribution
>         (Debian, Ubuntu, Fedora, Mageia etc.) it may be worth checking
>         whether
>         the packages you need are already there. Then the simplest solution
>         would be a "apt-get install whatever-you-like" and be lucky. The
>         nice
>         thing is that it then works (well, in theory) out of the box. And is
>         updated automatically (or not, if you manually put the package
>         on hold).
> 
>         If the package you need is still not there and you want to help us
>         completing the selection, you are very welcome. Even if you
>         don't want
>         to do the packaging yourself, it is useful to know, which
>         packages are
>         actually needed.
> 
>         Best regards
> 
>         Ole
>         _______________________________________________
>         AstroPy mailing list
>         AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>         http://mail.scipy.org/mailman/listinfo/astropy
> 
> 
> 
>     _______________________________________________
>     AstroPy mailing list
>     AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>     http://mail.scipy.org/mailman/listinfo/astropy
> 
> 
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy


From c.w.finn2301 at gmail.com  Fri Aug 15 06:36:34 2014
From: c.w.finn2301 at gmail.com (Charles Finn)
Date: Fri, 15 Aug 2014 11:36:34 +0100
Subject: [AstroPy] astropy.modeling bug
Message-ID: <2EC5EF65-A308-4977-92AC-229A769FC5A7@gmail.com>

Hi all,

While using astropy.modeling I?ve noticed a bug. The keyword argument ?weights?, passed to a __call__ method in any of the astropy.modeling.fitting classes that use scipy.optimize.leastsq does not work as it should. This is because the args keyword in leastsq should be passed a tuple with items in the order (xdata, ydata, zdata, model, weights), whereas the _wrap_deriv method arranges that tuple in the order (model, weights, xdata, ydata, zdata).

I?ve made a quick fix to the astropy build on my machine, and making the change described above fixes the problem. However, I?m not a contributor to the code, so I thought I would flag the issue here for someone more experienced than me to fix!

Best regards,

Charles

--
Charles William Finn
Postgraduate Researcher in Astrophysics

Extragalactic Astronomy & Cosmology Group
Department of Physics
Durham University
South Road
Durham DH1 3LE
United Kingdom

Email: c.w.finn at durham.ac.uk
Website: http://www.dur.ac.uk/c.w.finn/
Tel: +44 (191) 33 43517



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140815/60b7ccd6/attachment.html>

From bjd2385 at rit.edu  Fri Aug 15 14:45:31 2014
From: bjd2385 at rit.edu (Brandon Doyle)
Date: Fri, 15 Aug 2014 14:45:31 -0400
Subject: [AstroPy] Montage issue
In-Reply-To: <53EDD80F.3060104@gmail.com>
References: <CABb23mvxmKk48EPadHbEhqJV6a=wtfF6Vx18YHroEqocHYq0ew@mail.gmail.com>
	<87bnrnos91.fsf@baikal.ole.ath.cx>
	<CABb23mvh507V-kbRRZup3odANN43aYub28mnQJ6Sb0iLdtJ3MA@mail.gmail.com>
	<CAA-aB-bhb_SPHm7RT4wEEXtmE_L09weyrVBxbBwDSWdqZ5nDJw@mail.gmail.com>
	<53EDD80F.3060104@gmail.com>
Message-ID: <CAA-aB-bGFfUdzM-a_8e0QyfP-a0NC2OjDpWf60CAH8EVhDKiTw@mail.gmail.com>

Hello,

Just a follow-up to my previous email containing all of the files -- it
happens that I finally got a reply on Stackexchange, and while helpful it
still leaves quite a few issues that are yet to be resolved on my end. You
can see it here
<http://stackoverflow.com/questions/25327586/montageerror-invalid-table-file/25330189?noredirect=1#comment39490373_25330189>
.

I did as they said, i.e. I went and looked at what the last line is saying:

Invalid table file: /tmp/tmpDuSJlr/images_raw.tbl

and the file images_raw.tbl is indeed just an empty file...I'm not sure why
this would be? It's producing the r.fits, g.fits and b.fits images
perfectly and I can open them in FitsLiberator and they look fine. Then
when I open those same images with aplpy.make_rgb_cube() it outputs the
errors that can be seen in my post on Stack Exchange.

Hopefully there is a quick fix to this problem.

Brandon Doyle


On Fri, Aug 15, 2014 at 5:51 AM, Thomas Robitaille <
thomas.robitaille at gmail.com> wrote:

> Hi Brandon,
>
> Would it be possible for you to send me the files off-list, so I can
> take a look at the issue?
>
> Note that I have renamed this thread since it is not related to the
> thread to which it was posted to.
>
> Cheers,
> Tom
>
> Brandon Doyle wrote:
> > Hi all,
> >
> > Problem using Astropy this morning. Input code:
> >
> >         # Import Modules:
> >
> >         import aplpy
> >
> >         import pyfits
> >
> >         from numpy import *
> >
> >         import matplotlib as plt
> >
> >         import montage as montage_wrapper
> >
> >         import PIL
> >
> >
> >         # Begin convert images w/header/pyfits
> >
> >         r = pyfits.open('3c324IR.fits')
> >
> >         b = pyfits.open('3c324UVIS.fits')
> >
> >         g = pyfits.open('3c5GHZ.fits')
> >
> >
> >         r.info <http://r.info>()
> >
> >         g.info <http://g.info>()
> >
> >         b.info <http://b.info>()
> >
> >
> >         print(r[1].header)
> >
> >         print(g[1].header)
> >
> >         print(b[1].header)
> >
> >
> >         r1 = r[1].data
> >
> >         g1 = g[0].data
> >
> >         b1 = b[1].data
> >
> >
> >         hdu = pyfits.PrimaryHDU(r1)
> >
> >         hdulist = pyfits.HDUList([hdu])
> >
> >         hdulist.writeto('r.fits')
> >
> >
> >         hdu = pyfits.PrimaryHDU(g1)
> >
> >         hdulist = pyfits.HDUList([hdu])
> >
> >         hdulist.writeto('g.fits')
> >
> >
> >         hdu = pyfits.PrimaryHDU(b1)
> >
> >         hdulist = pyfits.HDUList([hdu])
> >
> >         hdulist.writeto('b.fits')
> >
> >
> >         # Begin Code:
> >
> >
> >         aplpy.make_rgb_cube(['r.fits','g.fits','b.fits'],
> '3c_324_rgb.fits')
> >
> >
> >         aplpy.make_rgb_image('3c_324_rgb.fits','3c_324_rgb.png')
> >
> >
> >         f = aplpy.FITSFigure('3c_324_rgb.fits')
> >
> >         f.show_rgb()
> >
> >         f.save('3c_324_rgb2.png')
> >
> >
> >         print 'END'
> >
> >
> > ?output from server:
> >
> >     ?
> >
> >     Traceback (most recent call last):
> >
> >       File "test9.py", line 47, in <module>
> >
> >         aplpy.make_rgb_cube(['r.fits','g.fits','b.fits'],
> '3c_324_rgb.fits')
> >
> >       File "/usr/local/lib/python2.7/dist-packages/aplpy/rgb.py", line
> >     309, in make_rgb_cube
> >
> >         montage.mMakeHdr(images_raw_tbl, header_hdr,
> >     north_aligned=north, system=system, equinox=equinox)
> >
> >       File
> >
>  "/usr/local/lib/python2.7/dist-packages/montage_wrapper/commands.py", line
> >     1468, in mMakeHdr
> >
> >         return status.parse_struct("mMakeHdr", p.stdout.read().strip())
> >
> >       File
> >     "/usr/local/lib/python2.7/dist-packages/montage_wrapper/status.py",
> >     line 33, in parse_struct
> >
> >         result = Struct(command, string)
> >
> >       File
> >     "/usr/local/lib/python2.7/dist-packages/montage_wrapper/status.py",
> >     line 70, in __init__
> >
> >         raise MontageError("%s: %s" % (command, self.msg))
> >
> >     montage_wrapper.status.MontageError: mMakeHdr: Invalid table file:
> >     /tmp/tmpmyYyN7/images_raw.tbl
> >
> >
> > ?I'm not sure what to make of it...any ideas?
> >
> > Brandon Doyle?
> >
> >
> >
> > On Thu, Aug 14, 2014 at 10:45 PM, gonghang.naoc <ghang.naoc at gmail.com
> > <mailto:ghang.naoc at gmail.com>> wrote:
> >
> >     Thank you all. Now I realize Anaconda+NOAO's iraf+pyraf, this combo
> >     is enough for me, temporarily.
> >
> >     hang
> >
> >
> >     On Fri, Aug 15, 2014 at 2:12 AM, ?l? ?tr???h?r <astropy at liska.ath.cx
> >     <mailto:astropy at liska.ath.cx>> wrote:
> >
> >         "gonghang.naoc" <ghang.naoc at gmail.com
> >         <mailto:ghang.naoc at gmail.com>> writes:
> >         > I reinstalled my system just now. The previsous system had a
> >         mess of
> >         > python modules with chaotic dependency. Could somebody please
> >         give me
> >         > a simple list to instll? Potentially I need numpy,scipy,epd,
> >         > ureka,iraf,pyraf, anaconda or somethig else which you can
> suggest.
> >         > A simple and versatile combo is the best.
> >
> >         Since this was not mentioned yet: If you are using a Linux
> >         distribution
> >         (Debian, Ubuntu, Fedora, Mageia etc.) it may be worth checking
> >         whether
> >         the packages you need are already there. Then the simplest
> solution
> >         would be a "apt-get install whatever-you-like" and be lucky. The
> >         nice
> >         thing is that it then works (well, in theory) out of the box.
> And is
> >         updated automatically (or not, if you manually put the package
> >         on hold).
> >
> >         If the package you need is still not there and you want to help
> us
> >         completing the selection, you are very welcome. Even if you
> >         don't want
> >         to do the packaging yourself, it is useful to know, which
> >         packages are
> >         actually needed.
> >
> >         Best regards
> >
> >         Ole
> >         _______________________________________________
> >         AstroPy mailing list
> >         AstroPy at scipy.org <mailto:AstroPy at scipy.org>
> >         http://mail.scipy.org/mailman/listinfo/astropy
> >
> >
> >
> >     _______________________________________________
> >     AstroPy mailing list
> >     AstroPy at scipy.org <mailto:AstroPy at scipy.org>
> >     http://mail.scipy.org/mailman/listinfo/astropy
> >
> >
> > _______________________________________________
> > AstroPy mailing list
> > AstroPy at scipy.org
> > http://mail.scipy.org/mailman/listinfo/astropy
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140815/ffc0e194/attachment.html>

From thomas.robitaille at gmail.com  Wed Aug 20 17:53:27 2014
From: thomas.robitaille at gmail.com (Thomas Robitaille)
Date: Wed, 20 Aug 2014 23:53:27 +0200
Subject: [AstroPy] astropy.modeling bug
In-Reply-To: <2EC5EF65-A308-4977-92AC-229A769FC5A7@gmail.com>
References: <2EC5EF65-A308-4977-92AC-229A769FC5A7@gmail.com>
Message-ID: <53F518D7.50100@gmail.com>

Hi Charles,

(I replied over the weekend but the scipy servers were down, so emails
sent to the list in the last few days have been lost)

Charles Finn wrote:
> Hi all,
> 
> While using astropy.modeling I?ve noticed a bug. The keyword argument
> ?weights?, passed to a __call__ method in any of the
> astropy.modeling.fitting classes that use scipy.optimize.leastsq does
> not work as it should. This is because the args keyword in leastsq
> should be passed a tuple with items in the order (xdata, ydata, zdata,
> model, weights), whereas the _wrap_deriv method arranges that tuple in
> the order (model, weights, xdata, ydata, zdata).

Could you report this issue here so that we can keep track of it?

https://github.com/astropy/astropy/issues

> I?ve made a quick fix to the astropy build on my machine, and making the
> change described above fixes the problem. However, I?m not a contributor
> to the code, so I thought I would flag the issue here for someone more
> experienced than me to fix!

Anyone can submit code contributions to Astropy, so you can learn to
become a contributor if you would like!  We have instructions here:

http://docs.astropy.org/en/stable/development/workflow/development_workflow.html

on how to open a 'pull request' on GitHub to suggest changes. Feel free
to give it a try and try submitting a patch for this issue!

Cheers,
Tom

> 
> Best regards,
> 
> Charles
> 
> --
> Charles William Finn
> Postgraduate Researcher in Astrophysics
> 
> Extragalactic Astronomy & Cosmology Group
> Department of Physics
> Durham University
> South Road
> Durham DH1 3LE
> United Kingdom
> 
> Email: c.w.finn at durham.ac.uk <mailto:c.w.finn at durham.ac.uk>
> Website: http://www.dur.ac.uk/c.w.finn/
> Tel: +44 (191) 33 43517
> 
> 
> 
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy


From adam.g.ginsburg at gmail.com  Fri Aug 22 09:31:30 2014
From: adam.g.ginsburg at gmail.com (Adam Ginsburg)
Date: Fri, 22 Aug 2014 15:31:30 +0200
Subject: [AstroPy] Astroquery v0.2 release
Message-ID: <CAEBNSwYy=RkAOqPVy_+Ttcb7CxJ7WOx_kT=05htBDO-dymrnRA@mail.gmail.com>

Astroquery v0.2 has been released.  Astroquery is a suite of tools for querying
various astronomical web forms, including observation archives, source
catalogs, and spectral line lists.

You can access astroquery at
https://pypi.python.org/pypi/astroquery/0.2
or directly from github:
https://github.com/astropy/astroquery/releases/tag/v0.2

The documents are hosted at:
http://astroquery.readthedocs.org/en/v0.2/


v0.2 has a few new features and includes major internal improvements.

The new tools provide interfaces to the ESO Archive, the GAMA database, the CDS
Xmatch service, NASA's SkyView service, and the Open Exoplanet Catalogue.

Thanks to the many contributors this cycle:
Julien Woillez (@jwoillez)
Simon Liedtke (@derdon)
Lo?c S?guin-Charbonneau (@loicseguin)
Caden Armstrong (@CadenArmstrong)
Joseph Booker (@sargas)
Erik Tollerud (@eteq)
Madhura Parikh (@jdnc)
@fred3m
Ricky Egeland (@rickyegeland)
Michel Droettboom (@mdboom)
James Allen(@james-allen)
Brigita Sipocz (@bsipocz)
Gustavo Braganca (@gabraganca)
Adrian Price-Whelan (@adrn)
David Shiga (@dshiga)
Matt Craig (@mwcraig)
Kyle Willett (@willettk)
Erik Bray (@embray)
William Schoenell (@wschoenell)
Austen Groener (@agroener)

Astroquery has 30 contributors, about 1/3 that of astropy, making it the
largest affiliated package by contributor count.

This release also coincides with the completion of the GSoC program.  Simon
Liedtke was our student this summer.  He changed astroquery from using lxml to
BeautifulSoup, especially in the ESO package. He also added support for the
services xMatch, SkyView and Atomic Line List.  Documentation has been added
for the packages xmatch and atomic (though note that extensive documentation
exists in form of docstrings for all packages he added, inlcuding SkyView). All
new services have tests that can be run both off- and online.

As always, please report any issues on github:
https://github.com/astropy/astroquery/issues

-- 
Adam Ginsburg, Christoph Deil, and Thomas Robitaille


From stsci.perry at gmail.com  Fri Aug 29 11:20:31 2014
From: stsci.perry at gmail.com (Perry Greenfield)
Date: Fri, 29 Aug 2014 11:20:31 -0400
Subject: [AstroPy] [ANN] new astropy-affiliated package for spherical
	geometry
References: <AA4E9EF9-C742-46F4-BEDE-51C8B1CF0C95@gmail.com>
Message-ID: <DC333C89-34E8-4497-BEFC-1D432A8BF061@gmail.com>


We are pleased to announce the availability of a new astropy affiliated package.

spherical_geometry is a package for handling spherical polygons that represent arbitrary regions on the sky, and being able to manipulate such regions with operations such as computing the intersection or unions of such regions, testing to see if coordinates lie within a region, and computing region areas. It also allows computing distances between points, midpoints in such cases, angles and intersection points between great circles, and other related utilities.

All the coordinates in spherical_geometry are represented as unit vectors, thus avoiding the usual problems encountered near the poles when manipulating celestial coordinates.

The package provides means to convert to and from a celestial coordinate system. Which system is not important so long as consistency is used when converting back to the same coordinate system as was used initially.

This package has been developed by Mike Droettboom,  and ported to be astropy compatible by Bernie Simon, with significant testing and bug finding by Mihai Cara and Pey-Lian Lim

For more details, see the github repository and associated README: https://github.com/spacetelescope/sphere.

The documentation is located at: http://spacetelescope.github.io/sphere/spherical_geometry/

The current version is v1.0.4







From deil.christoph at googlemail.com  Sat Aug 30 07:34:58 2014
From: deil.christoph at googlemail.com (Christoph Deil)
Date: Sat, 30 Aug 2014 12:34:58 +0100
Subject: [AstroPy] [ANN] new astropy-affiliated package for spherical
	geometry
In-Reply-To: <DC333C89-34E8-4497-BEFC-1D432A8BF061@gmail.com>
References: <AA4E9EF9-C742-46F4-BEDE-51C8B1CF0C95@gmail.com>
	<DC333C89-34E8-4497-BEFC-1D432A8BF061@gmail.com>
Message-ID: <E2156213-E141-4814-AD6A-8322DB684648@gmail.com>


On 29 Aug 2014, at 16:20, Perry Greenfield <stsci.perry at gmail.com> wrote:

> 
> We are pleased to announce the availability of a new astropy affiliated package.
> 
> spherical_geometry is a package for handling spherical polygons that represent arbitrary regions on the sky, and being able to manipulate such regions with operations such as computing the intersection or unions of such regions, testing to see if coordinates lie within a region, and computing region areas. It also allows computing distances between points, midpoints in such cases, angles and intersection points between great circles, and other related utilities.
> 
> All the coordinates in spherical_geometry are represented as unit vectors, thus avoiding the usual problems encountered near the poles when manipulating celestial coordinates.
> 
> The package provides means to convert to and from a celestial coordinate system. Which system is not important so long as consistency is used when converting back to the same coordinate system as was used initially.
> 
> This package has been developed by Mike Droettboom,  and ported to be astropy compatible by Bernie Simon, with significant testing and bug finding by Mihai Cara and Pey-Lian Lim
> 
> For more details, see the github repository and associated README: https://github.com/spacetelescope/sphere.
> 
> The documentation is located at: http://spacetelescope.github.io/sphere/spherical_geometry/
> 
> The current version is v1.0.4
> 
> 
> 
> 
> 
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy


Thanks!

Are you considering moving this into the Astropy core or do you plan to keep this as a separate package?

Christoph

From stsci.perry at gmail.com  Sat Aug 30 08:13:07 2014
From: stsci.perry at gmail.com (Perry Greenfield)
Date: Sat, 30 Aug 2014 08:13:07 -0400
Subject: [AstroPy] [ANN] new astropy-affiliated package for spherical
	geometry
In-Reply-To: <E2156213-E141-4814-AD6A-8322DB684648@gmail.com>
References: <AA4E9EF9-C742-46F4-BEDE-51C8B1CF0C95@gmail.com>
	<DC333C89-34E8-4497-BEFC-1D432A8BF061@gmail.com>
	<E2156213-E141-4814-AD6A-8322DB684648@gmail.com>
Message-ID: <BB81A8A1-FC04-49EE-B901-24E1226C6765@gmail.com>


On Aug 30, 2014, at 7:34 AM, Christoph Deil wrote:

> 
> On 29 Aug 2014, at 16:20, Perry Greenfield <stsci.perry at gmail.com> wrote:
> 
> Thanks!
> 
> Are you considering moving this into the Astropy core or do you plan to keep this as a separate package?
> 
> Christoph

Yes, we think it would be very suitable for the core. Introducing it as an affiliated package means it is available more quickly than if we went straight to the core. 

Cheer, Perry



From deil.christoph at googlemail.com  Sat Aug 30 08:40:07 2014
From: deil.christoph at googlemail.com (Christoph Deil)
Date: Sat, 30 Aug 2014 13:40:07 +0100
Subject: [AstroPy] [ANN] new astropy-affiliated package for spherical
	geometry
In-Reply-To: <BB81A8A1-FC04-49EE-B901-24E1226C6765@gmail.com>
References: <AA4E9EF9-C742-46F4-BEDE-51C8B1CF0C95@gmail.com>
	<DC333C89-34E8-4497-BEFC-1D432A8BF061@gmail.com>
	<E2156213-E141-4814-AD6A-8322DB684648@gmail.com>
	<BB81A8A1-FC04-49EE-B901-24E1226C6765@gmail.com>
Message-ID: <303C14C6-FB95-45C4-BBCD-186AB64B9336@gmail.com>


On 30 Aug 2014, at 13:13, Perry Greenfield <stsci.perry at gmail.com> wrote:

> 
> On Aug 30, 2014, at 7:34 AM, Christoph Deil wrote:
> 
>> 
>> On 29 Aug 2014, at 16:20, Perry Greenfield <stsci.perry at gmail.com> wrote:
>> 
>> Thanks!
>> 
>> Are you considering moving this into the Astropy core or do you plan to keep this as a separate package?
>> 
>> Christoph
> 
> Yes, we think it would be very suitable for the core. Introducing it as an affiliated package means it is available more quickly than if we went straight to the core. 
> 
> Cheer, Perry

Great, thanks!

If it?s available in Astropy 1.0 in a few months it will be easy to use it in affiliated packages or scripts without having to explain about an extra dependency.

Christoph

From ghang.naoc at gmail.com  Sun Aug 31 23:09:53 2014
From: ghang.naoc at gmail.com (gonghang.naoc)
Date: Mon, 1 Sep 2014 11:09:53 +0800
Subject: [AstroPy] how to flatten an optical spectrum of a star
Message-ID: <CABb23mujtFJg39N8OV4MLkcbyJ+qUVfEzNpboVOyoa0pwLWGmA@mail.gmail.com>

Hi all,
Sometimes we can see a star's spectrum is flattened. That is because we
have already known its black body continuum well and a flattened spectrum
can save space, right?

A naive question is generally how to make that kind of spectrum?  Every
point is divided by its neighbours? values?
Is there any ready made python module to do that?

Thank you.
hang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20140901/c5ac8d84/attachment.html>