From mdroe at stsci.edu  Tue Jan  3 08:33:14 2012
From: mdroe at stsci.edu (Michael Droettboom)
Date: Tue, 3 Jan 2012 08:33:14 -0500
Subject: [AstroPy] pywcs 1.10-4.7 install failure on Microsoft Windows
In-Reply-To: <4EFB61B8.3030406@stsci.edu>
References: <CADb5CeivE8F8cMgc_5pH3zeay=eNifwCtcz6cMAe3HdNY=iCoQ@mail.gmail.com>
	<4EF456C4.5000308@astro.rug.nl>
	<CADb5CegT=pxDgQZAb1m+aK03z7yE+nwHv1u+uZNtjS7PkN6NAg@mail.gmail.com>
	<CAMe0V1bMDoP3r-pJQfP+kryka5C75XT5od5EZFpztypnDZHowQ@mail.gmail.com>
	<CA+G92RfW_y6WnF5qNbBiAiCM=A+6MEdb6SK5qouA5GYDoFcasQ@mail.gmail.com>
	<4EFB61B8.3030406@stsci.edu>
Message-ID: <4F03039A.5030709@stsci.edu>

My apologies that this isn't working for you -- I don't have access to 
Visual Studio 9.0 to test with, so these sorts of things can fall 
through the cracks.

Mark is right that the old solution involved patching wcslib before 
shipping it with pywcs.

However, as of version 1.10 (which you are using), the solution was to add:

    #define wcsset wcsset_

on Windows.  This works with the mingw32/cygwin compiler, but apparently 
failing on the Microsoft compiler.

There is an even newer solution in pywcs SVN which defines the following 
on Windows.  This I believe to work on the Microsoft compilers based on 
the report of another user:

if sys.platform == 'win32':
     define_macros.append(('YY_NO_UNISTD_H', None))
     define_macros.append(('_CRT_SECURE_NO_WARNINGS', None))
     define_macros.append(('_NO_OLDNAMES', None)) # for mingw32
     define_macros.append(('NO_OLDNAMES', None)) # for mingw64

You can either splice this into your current copy of setup.py, or build 
from SVN.  Note that building from SVN currently requires having parts 
of stsci_python installed (notable stsci.tools.stsci_distutils_hack).

Mike

On 12/28/2011 01:36 PM, Mark Sienkiewicz wrote:
> On 12/25/11 16:25, Tim Jenness wrote:
>> On Sun, Dec 25, 2011 at 6:29 AM, Rahul Patel<rahpatel at ic.sunysb.edu>   wrote:
>>> Ya.... I'm not really comfortable with commenting or changing that out.I
>>> really wish there were some way for this to work.
>>>
>> The real fix is for pywcs to be modified so that it does not use a
>> fucntion called wcsset() otherwise this clash is going to continue.
>>
>
> The problem is actually in the C code for wcslib, the library that pywcs is based on.  wcslib defines a function named wcsset (see pywcs/wcslib/C/wcs.c).  I seem to remember Mike Droettboom telling me that he has to patch wcslib every time he incorporates a new version into pywcs.
>
> If you are in a hurry to make pywcs work, I can suggest either a hack around the problem (as has been discussed) or use an earlier version of pywcs from before the integration of wcslib-4.8 began.
>
> I seem to remember that the pywcs that was include in STSCI_PYTHON 2.12 compiled on Windows.  You can download source code for stsci_python from http://www.stsci.edu/resources/software_hardware/stsci_python/current/download and then install only the pywcs package instead of the entire distribution.  Just "cd pywcs ; python setup.py install".
>
> If it is not urgent, Mike can probably give you a more satisfactory solution when he comes back from the holidays.
>
> Mark S.
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy



From jim.vickroy at noaa.gov  Tue Jan  3 09:21:14 2012
From: jim.vickroy at noaa.gov (Jim Vickroy)
Date: Tue, 03 Jan 2012 07:21:14 -0700
Subject: [AstroPy] pywcs 1.10-4.7 install failure on Microsoft Windows
In-Reply-To: <4F03039A.5030709@stsci.edu>
References: <CADb5CeivE8F8cMgc_5pH3zeay=eNifwCtcz6cMAe3HdNY=iCoQ@mail.gmail.com>
	<4EF456C4.5000308@astro.rug.nl>
	<CADb5CegT=pxDgQZAb1m+aK03z7yE+nwHv1u+uZNtjS7PkN6NAg@mail.gmail.com>
	<CAMe0V1bMDoP3r-pJQfP+kryka5C75XT5od5EZFpztypnDZHowQ@mail.gmail.com>
	<CA+G92RfW_y6WnF5qNbBiAiCM=A+6MEdb6SK5qouA5GYDoFcasQ@mail.gmail.com>
	<4EFB61B8.3030406@stsci.edu> <4F03039A.5030709@stsci.edu>
Message-ID: <4F030EDA.7090400@noaa.gov>

On 1/3/2012 6:33 AM, Michael Droettboom wrote:
> My apologies that this isn't working for you -- I don't have access to
> Visual Studio 9.0 to test with, so these sorts of things can fall
> through the cracks.
>
> Mark is right that the old solution involved patching wcslib before
> shipping it with pywcs.
>
> However, as of version 1.10 (which you are using), the solution was to add:
>
>      #define wcsset wcsset_
>
> on Windows.  This works with the mingw32/cygwin compiler, but apparently
> failing on the Microsoft compiler.
>
> There is an even newer solution in pywcs SVN which defines the following
> on Windows.  This I believe to work on the Microsoft compilers based on
> the report of another user:
>
> if sys.platform == 'win32':
>       define_macros.append(('YY_NO_UNISTD_H', None))
>       define_macros.append(('_CRT_SECURE_NO_WARNINGS', None))
>       define_macros.append(('_NO_OLDNAMES', None)) # for mingw32
>       define_macros.append(('NO_OLDNAMES', None)) # for mingw64
>
> You can either splice this into your current copy of setup.py, or build
> from SVN.  Note that building from SVN currently requires having parts
> of stsci_python installed (notable stsci.tools.stsci_distutils_hack).
>
> Mike

Thanks, Mike.

Could you elaborate on the above patch?  Do I need to import something 
other than sys?  Where is define_macros defined?

-- jv


> On 12/28/2011 01:36 PM, Mark Sienkiewicz wrote:
>> On 12/25/11 16:25, Tim Jenness wrote:
>>> On Sun, Dec 25, 2011 at 6:29 AM, Rahul Patel<rahpatel at ic.sunysb.edu>    wrote:
>>>> Ya.... I'm not really comfortable with commenting or changing that out.I
>>>> really wish there were some way for this to work.
>>>>
>>> The real fix is for pywcs to be modified so that it does not use a
>>> fucntion called wcsset() otherwise this clash is going to continue.
>>>
>> The problem is actually in the C code for wcslib, the library that pywcs is based on.  wcslib defines a function named wcsset (see pywcs/wcslib/C/wcs.c).  I seem to remember Mike Droettboom telling me that he has to patch wcslib every time he incorporates a new version into pywcs.
>>
>> If you are in a hurry to make pywcs work, I can suggest either a hack around the problem (as has been discussed) or use an earlier version of pywcs from before the integration of wcslib-4.8 began.
>>
>> I seem to remember that the pywcs that was include in STSCI_PYTHON 2.12 compiled on Windows.  You can download source code for stsci_python from http://www.stsci.edu/resources/software_hardware/stsci_python/current/download and then install only the pywcs package instead of the entire distribution.  Just "cd pywcs ; python setup.py install".
>>
>> If it is not urgent, Mike can probably give you a more satisfactory solution when he comes back from the holidays.
>>
>> Mark S.
>>
>> _______________________________________________
>> 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 mdroe at stsci.edu  Tue Jan  3 10:30:06 2012
From: mdroe at stsci.edu (Michael Droettboom)
Date: Tue, 3 Jan 2012 10:30:06 -0500
Subject: [AstroPy] pywcs 1.10-4.7 install failure on Microsoft Windows
In-Reply-To: <4F030EDA.7090400@noaa.gov>
References: <CADb5CeivE8F8cMgc_5pH3zeay=eNifwCtcz6cMAe3HdNY=iCoQ@mail.gmail.com>
	<4EF456C4.5000308@astro.rug.nl>
	<CADb5CegT=pxDgQZAb1m+aK03z7yE+nwHv1u+uZNtjS7PkN6NAg@mail.gmail.com>
	<CAMe0V1bMDoP3r-pJQfP+kryka5C75XT5od5EZFpztypnDZHowQ@mail.gmail.com>
	<CA+G92RfW_y6WnF5qNbBiAiCM=A+6MEdb6SK5qouA5GYDoFcasQ@mail.gmail.com>
	<4EFB61B8.3030406@stsci.edu> <4F03039A.5030709@stsci.edu>
	<4F030EDA.7090400@noaa.gov>
Message-ID: <4F031EFE.9010200@stsci.edu>

On 01/03/2012 09:21 AM, Jim Vickroy wrote:
> On 1/3/2012 6:33 AM, Michael Droettboom wrote:
>> My apologies that this isn't working for you -- I don't have access to
>> Visual Studio 9.0 to test with, so these sorts of things can fall
>> through the cracks.
>>
>> Mark is right that the old solution involved patching wcslib before
>> shipping it with pywcs.
>>
>> However, as of version 1.10 (which you are using), the solution was to add:
>>
>>       #define wcsset wcsset_
>>
>> on Windows.  This works with the mingw32/cygwin compiler, but apparently
>> failing on the Microsoft compiler.
>>
>> There is an even newer solution in pywcs SVN which defines the following
>> on Windows.  This I believe to work on the Microsoft compilers based on
>> the report of another user:
>>
>> if sys.platform == 'win32':
>>        define_macros.append(('YY_NO_UNISTD_H', None))
>>        define_macros.append(('_CRT_SECURE_NO_WARNINGS', None))
>>        define_macros.append(('_NO_OLDNAMES', None)) # for mingw32
>>        define_macros.append(('NO_OLDNAMES', None)) # for mingw64
>>
>> You can either splice this into your current copy of setup.py, or build
>> from SVN.  Note that building from SVN currently requires having parts
>> of stsci_python installed (notable stsci.tools.stsci_distutils_hack).
>>
>> Mike
> Thanks, Mike.
>
> Could you elaborate on the above patch?  Do I need to import something
> other than sys?  Where is define_macros defined?
Of course -- first day back and I'm whipping through e-mail too quickly ;)

This goes in defsetup.py -- there is already an "if sys.platform == 
'win32'" clause -- you would just need to add the "OLDNAMES" lines to it.

Mike


From jim.vickroy at noaa.gov  Tue Jan  3 11:32:46 2012
From: jim.vickroy at noaa.gov (Jim Vickroy)
Date: Tue, 03 Jan 2012 09:32:46 -0700
Subject: [AstroPy] pywcs 1.10-4.7 install failure on Microsoft Windows
In-Reply-To: <4F031EFE.9010200@stsci.edu>
References: <CADb5CeivE8F8cMgc_5pH3zeay=eNifwCtcz6cMAe3HdNY=iCoQ@mail.gmail.com>
	<4EF456C4.5000308@astro.rug.nl>
	<CADb5CegT=pxDgQZAb1m+aK03z7yE+nwHv1u+uZNtjS7PkN6NAg@mail.gmail.com>
	<CAMe0V1bMDoP3r-pJQfP+kryka5C75XT5od5EZFpztypnDZHowQ@mail.gmail.com>
	<CA+G92RfW_y6WnF5qNbBiAiCM=A+6MEdb6SK5qouA5GYDoFcasQ@mail.gmail.com>
	<4EFB61B8.3030406@stsci.edu> <4F03039A.5030709@stsci.edu>
	<4F030EDA.7090400@noaa.gov> <4F031EFE.9010200@stsci.edu>
Message-ID: <4F032DAE.10104@noaa.gov>

On 1/3/2012 8:30 AM, Michael Droettboom wrote:
> On 01/03/2012 09:21 AM, Jim Vickroy wrote:
>> On 1/3/2012 6:33 AM, Michael Droettboom wrote:
>>> My apologies that this isn't working for you -- I don't have access to
>>> Visual Studio 9.0 to test with, so these sorts of things can fall
>>> through the cracks.
>>>
>>> Mark is right that the old solution involved patching wcslib before
>>> shipping it with pywcs.
>>>
>>> However, as of version 1.10 (which you are using), the solution was to add:
>>>
>>>        #define wcsset wcsset_
>>>
>>> on Windows.  This works with the mingw32/cygwin compiler, but apparently
>>> failing on the Microsoft compiler.
>>>
>>> There is an even newer solution in pywcs SVN which defines the following
>>> on Windows.  This I believe to work on the Microsoft compilers based on
>>> the report of another user:
>>>
>>> if sys.platform == 'win32':
>>>         define_macros.append(('YY_NO_UNISTD_H', None))
>>>         define_macros.append(('_CRT_SECURE_NO_WARNINGS', None))
>>>         define_macros.append(('_NO_OLDNAMES', None)) # for mingw32
>>>         define_macros.append(('NO_OLDNAMES', None)) # for mingw64
>>>
>>> You can either splice this into your current copy of setup.py, or build
>>> from SVN.  Note that building from SVN currently requires having parts
>>> of stsci_python installed (notable stsci.tools.stsci_distutils_hack).
>>>
>>> Mike
>> Thanks, Mike.
>>
>> Could you elaborate on the above patch?  Do I need to import something
>> other than sys?  Where is define_macros defined?
> Of course -- first day back and I'm whipping through e-mail too quickly ;)
>
> This goes in defsetup.py -- there is already an "if sys.platform ==
> 'win32'" clause -- you would just need to add the "OLDNAMES" lines to it.
>
> Mike
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy

I added the OLDNAMES lines as above and here is the result:

C:\Projects\pywcs-1.10-4.7>setup.py install
running install
running build
running build_py
copying lib\svn_version.py -> build\lib.win32-2.6\pywcs
running build_ext
building 'pywcs._pywcs' extension
c:\Program Files\Microsoft Visual Studio 9.0\VC\BIN\cl.exe /c /nologo 
/Ox /MD /W3 /GS- /DNDEBUG -DECHO -DWCSTRIG_MACRO -DPYWCS_BUILD 
-D_GNU_SOURCE -DNDEBUG -DYY_NO_UNISTD_H -D_CRT_SECURE_NO_WARNINGS 
-D_NO_OLDNAMES -DNO_OLDNAMES -U
DEBUG -IC:\Python26\lib\site-packages\numpy\core\include -I.\wcslib\C 
-Iwcslib\C -I.\src -IC:\Python26\include -IC:\Python26\PC 
/Tcwcslib\C\flexed/wcsbth.c 
/Fobuild\temp.win32-2.6\Release\wcslib\C\flexed/wcsbth.obj
wcsbth.c
.\wcslib\C\wcs.h(1396) : warning C4030: first formal parameter list 
longer than the second list
.\wcslib\C\wcs.h(1396) : warning C4028: formal parameter 1 different 
from declaration
.\wcslib\C\wcs.h(1396) : error C2040: 'wcsset' : 'int (wcsprm *)' 
differs in levels of indirection from 'int (wcsprm *)'
error: command '"c:\Program Files\Microsoft Visual Studio 
9.0\VC\BIN\cl.exe"' failed with exit status 2

C:\Projects\pywcs-1.10-4.7>





From mdroe at stsci.edu  Tue Jan  3 12:22:39 2012
From: mdroe at stsci.edu (Michael Droettboom)
Date: Tue, 3 Jan 2012 12:22:39 -0500
Subject: [AstroPy] pywcs 1.10-4.7 install failure on Microsoft Windows
In-Reply-To: <4F032DAE.10104@noaa.gov>
References: <CADb5CeivE8F8cMgc_5pH3zeay=eNifwCtcz6cMAe3HdNY=iCoQ@mail.gmail.com>
	<4EF456C4.5000308@astro.rug.nl>
	<CADb5CegT=pxDgQZAb1m+aK03z7yE+nwHv1u+uZNtjS7PkN6NAg@mail.gmail.com>
	<CAMe0V1bMDoP3r-pJQfP+kryka5C75XT5od5EZFpztypnDZHowQ@mail.gmail.com>
	<CA+G92RfW_y6WnF5qNbBiAiCM=A+6MEdb6SK5qouA5GYDoFcasQ@mail.gmail.com>
	<4EFB61B8.3030406@stsci.edu> <4F03039A.5030709@stsci.edu>
	<4F030EDA.7090400@noaa.gov> <4F031EFE.9010200@stsci.edu>
	<4F032DAE.10104@noaa.gov>
Message-ID: <4F03395F.9050008@stsci.edu>

Hmm...  Do you have any luck if you remove this from defsetup.py?

if sys.platform in ('win32', 'cygwin'):
     h_file.write("""
#define wcsset wcsset_
""")

Mike

On 01/03/2012 11:32 AM, Jim Vickroy wrote:
> On 1/3/2012 8:30 AM, Michael Droettboom wrote:
>> On 01/03/2012 09:21 AM, Jim Vickroy wrote:
>>> On 1/3/2012 6:33 AM, Michael Droettboom wrote:
>>>> My apologies that this isn't working for you -- I don't have access to
>>>> Visual Studio 9.0 to test with, so these sorts of things can fall
>>>> through the cracks.
>>>>
>>>> Mark is right that the old solution involved patching wcslib before
>>>> shipping it with pywcs.
>>>>
>>>> However, as of version 1.10 (which you are using), the solution was to add:
>>>>
>>>>         #define wcsset wcsset_
>>>>
>>>> on Windows.  This works with the mingw32/cygwin compiler, but apparently
>>>> failing on the Microsoft compiler.
>>>>
>>>> There is an even newer solution in pywcs SVN which defines the following
>>>> on Windows.  This I believe to work on the Microsoft compilers based on
>>>> the report of another user:
>>>>
>>>> if sys.platform == 'win32':
>>>>          define_macros.append(('YY_NO_UNISTD_H', None))
>>>>          define_macros.append(('_CRT_SECURE_NO_WARNINGS', None))
>>>>          define_macros.append(('_NO_OLDNAMES', None)) # for mingw32
>>>>          define_macros.append(('NO_OLDNAMES', None)) # for mingw64
>>>>
>>>> You can either splice this into your current copy of setup.py, or build
>>>> from SVN.  Note that building from SVN currently requires having parts
>>>> of stsci_python installed (notable stsci.tools.stsci_distutils_hack).
>>>>
>>>> Mike
>>> Thanks, Mike.
>>>
>>> Could you elaborate on the above patch?  Do I need to import something
>>> other than sys?  Where is define_macros defined?
>> Of course -- first day back and I'm whipping through e-mail too quickly ;)
>>
>> This goes in defsetup.py -- there is already an "if sys.platform ==
>> 'win32'" clause -- you would just need to add the "OLDNAMES" lines to it.
>>
>> Mike
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
> I added the OLDNAMES lines as above and here is the result:
>
> C:\Projects\pywcs-1.10-4.7>setup.py install
> running install
> running build
> running build_py
> copying lib\svn_version.py ->  build\lib.win32-2.6\pywcs
> running build_ext
> building 'pywcs._pywcs' extension
> c:\Program Files\Microsoft Visual Studio 9.0\VC\BIN\cl.exe /c /nologo
> /Ox /MD /W3 /GS- /DNDEBUG -DECHO -DWCSTRIG_MACRO -DPYWCS_BUILD
> -D_GNU_SOURCE -DNDEBUG -DYY_NO_UNISTD_H -D_CRT_SECURE_NO_WARNINGS
> -D_NO_OLDNAMES -DNO_OLDNAMES -U
> DEBUG -IC:\Python26\lib\site-packages\numpy\core\include -I.\wcslib\C
> -Iwcslib\C -I.\src -IC:\Python26\include -IC:\Python26\PC
> /Tcwcslib\C\flexed/wcsbth.c
> /Fobuild\temp.win32-2.6\Release\wcslib\C\flexed/wcsbth.obj
> wcsbth.c
> .\wcslib\C\wcs.h(1396) : warning C4030: first formal parameter list
> longer than the second list
> .\wcslib\C\wcs.h(1396) : warning C4028: formal parameter 1 different
> from declaration
> .\wcslib\C\wcs.h(1396) : error C2040: 'wcsset' : 'int (wcsprm *)'
> differs in levels of indirection from 'int (wcsprm *)'
> error: command '"c:\Program Files\Microsoft Visual Studio
> 9.0\VC\BIN\cl.exe"' failed with exit status 2
>
> C:\Projects\pywcs-1.10-4.7>
>
>
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy



From jim.vickroy at noaa.gov  Tue Jan  3 12:54:44 2012
From: jim.vickroy at noaa.gov (Jim Vickroy)
Date: Tue, 03 Jan 2012 10:54:44 -0700
Subject: [AstroPy] pywcs 1.10-4.7 install failure on Microsoft Windows
In-Reply-To: <4F03395F.9050008@stsci.edu>
References: <CADb5CeivE8F8cMgc_5pH3zeay=eNifwCtcz6cMAe3HdNY=iCoQ@mail.gmail.com>
	<4EF456C4.5000308@astro.rug.nl>
	<CADb5CegT=pxDgQZAb1m+aK03z7yE+nwHv1u+uZNtjS7PkN6NAg@mail.gmail.com>
	<CAMe0V1bMDoP3r-pJQfP+kryka5C75XT5od5EZFpztypnDZHowQ@mail.gmail.com>
	<CA+G92RfW_y6WnF5qNbBiAiCM=A+6MEdb6SK5qouA5GYDoFcasQ@mail.gmail.com>
	<4EFB61B8.3030406@stsci.edu> <4F03039A.5030709@stsci.edu>
	<4F030EDA.7090400@noaa.gov> <4F031EFE.9010200@stsci.edu>
	<4F032DAE.10104@noaa.gov> <4F03395F.9050008@stsci.edu>
Message-ID: <4F0340E4.7090800@noaa.gov>

On 1/3/2012 10:22 AM, Michael Droettboom wrote:
> Hmm...  Do you have any luck if you remove this from defsetup.py?
>
> if sys.platform in ('win32', 'cygwin'):
>       h_file.write("""
> #define wcsset wcsset_
> """)
>
> Mike

Unfortunately, the same error trace occurs if the above line is 
removed.  -- jv


>
> On 01/03/2012 11:32 AM, Jim Vickroy wrote:
>> On 1/3/2012 8:30 AM, Michael Droettboom wrote:
>>> On 01/03/2012 09:21 AM, Jim Vickroy wrote:
>>>> On 1/3/2012 6:33 AM, Michael Droettboom wrote:
>>>>> My apologies that this isn't working for you -- I don't have access to
>>>>> Visual Studio 9.0 to test with, so these sorts of things can fall
>>>>> through the cracks.
>>>>>
>>>>> Mark is right that the old solution involved patching wcslib before
>>>>> shipping it with pywcs.
>>>>>
>>>>> However, as of version 1.10 (which you are using), the solution was to add:
>>>>>
>>>>>          #define wcsset wcsset_
>>>>>
>>>>> on Windows.  This works with the mingw32/cygwin compiler, but apparently
>>>>> failing on the Microsoft compiler.
>>>>>
>>>>> There is an even newer solution in pywcs SVN which defines the following
>>>>> on Windows.  This I believe to work on the Microsoft compilers based on
>>>>> the report of another user:
>>>>>
>>>>> if sys.platform == 'win32':
>>>>>           define_macros.append(('YY_NO_UNISTD_H', None))
>>>>>           define_macros.append(('_CRT_SECURE_NO_WARNINGS', None))
>>>>>           define_macros.append(('_NO_OLDNAMES', None)) # for mingw32
>>>>>           define_macros.append(('NO_OLDNAMES', None)) # for mingw64
>>>>>
>>>>> You can either splice this into your current copy of setup.py, or build
>>>>> from SVN.  Note that building from SVN currently requires having parts
>>>>> of stsci_python installed (notable stsci.tools.stsci_distutils_hack).
>>>>>
>>>>> Mike
>>>> Thanks, Mike.
>>>>
>>>> Could you elaborate on the above patch?  Do I need to import something
>>>> other than sys?  Where is define_macros defined?
>>> Of course -- first day back and I'm whipping through e-mail too quickly ;)
>>>
>>> This goes in defsetup.py -- there is already an "if sys.platform ==
>>> 'win32'" clause -- you would just need to add the "OLDNAMES" lines to it.
>>>
>>> Mike
>>> _______________________________________________
>>> AstroPy mailing list
>>> AstroPy at scipy.org
>>> http://mail.scipy.org/mailman/listinfo/astropy
>> I added the OLDNAMES lines as above and here is the result:
>>
>> C:\Projects\pywcs-1.10-4.7>setup.py install
>> running install
>> running build
>> running build_py
>> copying lib\svn_version.py ->   build\lib.win32-2.6\pywcs
>> running build_ext
>> building 'pywcs._pywcs' extension
>> c:\Program Files\Microsoft Visual Studio 9.0\VC\BIN\cl.exe /c /nologo
>> /Ox /MD /W3 /GS- /DNDEBUG -DECHO -DWCSTRIG_MACRO -DPYWCS_BUILD
>> -D_GNU_SOURCE -DNDEBUG -DYY_NO_UNISTD_H -D_CRT_SECURE_NO_WARNINGS
>> -D_NO_OLDNAMES -DNO_OLDNAMES -U
>> DEBUG -IC:\Python26\lib\site-packages\numpy\core\include -I.\wcslib\C
>> -Iwcslib\C -I.\src -IC:\Python26\include -IC:\Python26\PC
>> /Tcwcslib\C\flexed/wcsbth.c
>> /Fobuild\temp.win32-2.6\Release\wcslib\C\flexed/wcsbth.obj
>> wcsbth.c
>> .\wcslib\C\wcs.h(1396) : warning C4030: first formal parameter list
>> longer than the second list
>> .\wcslib\C\wcs.h(1396) : warning C4028: formal parameter 1 different
>> from declaration
>> .\wcslib\C\wcs.h(1396) : error C2040: 'wcsset' : 'int (wcsprm *)'
>> differs in levels of indirection from 'int (wcsprm *)'
>> error: command '"c:\Program Files\Microsoft Visual Studio
>> 9.0\VC\BIN\cl.exe"' failed with exit status 2
>>
>> C:\Projects\pywcs-1.10-4.7>
>>
>>
>>
>> _______________________________________________
>> 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 mdroe at stsci.edu  Tue Jan  3 14:15:43 2012
From: mdroe at stsci.edu (Michael Droettboom)
Date: Tue, 3 Jan 2012 14:15:43 -0500
Subject: [AstroPy] pywcs 1.10-4.7 install failure on Microsoft Windows
In-Reply-To: <4F0340E4.7090800@noaa.gov>
References: <CADb5CeivE8F8cMgc_5pH3zeay=eNifwCtcz6cMAe3HdNY=iCoQ@mail.gmail.com>
	<4EF456C4.5000308@astro.rug.nl>
	<CADb5CegT=pxDgQZAb1m+aK03z7yE+nwHv1u+uZNtjS7PkN6NAg@mail.gmail.com>
	<CAMe0V1bMDoP3r-pJQfP+kryka5C75XT5od5EZFpztypnDZHowQ@mail.gmail.com>
	<CA+G92RfW_y6WnF5qNbBiAiCM=A+6MEdb6SK5qouA5GYDoFcasQ@mail.gmail.com>
	<4EFB61B8.3030406@stsci.edu> <4F03039A.5030709@stsci.edu>
	<4F030EDA.7090400@noaa.gov> <4F031EFE.9010200@stsci.edu>
	<4F032DAE.10104@noaa.gov> <4F03395F.9050008@stsci.edu>
	<4F0340E4.7090800@noaa.gov>
Message-ID: <4F0353DF.9040306@stsci.edu>

Ok.  I'm in the process of getting a Visual Studio environment set up 
here and will let you know what I discover.

Mike

On 01/03/2012 12:54 PM, Jim Vickroy wrote:
> On 1/3/2012 10:22 AM, Michael Droettboom wrote:
>> Hmm...  Do you have any luck if you remove this from defsetup.py?
>>
>> if sys.platform in ('win32', 'cygwin'):
>>        h_file.write("""
>> #define wcsset wcsset_
>> """)
>>
>> Mike
> Unfortunately, the same error trace occurs if the above line is
> removed.  -- jv
>
>
>> On 01/03/2012 11:32 AM, Jim Vickroy wrote:
>>> On 1/3/2012 8:30 AM, Michael Droettboom wrote:
>>>> On 01/03/2012 09:21 AM, Jim Vickroy wrote:
>>>>> On 1/3/2012 6:33 AM, Michael Droettboom wrote:
>>>>>> My apologies that this isn't working for you -- I don't have access to
>>>>>> Visual Studio 9.0 to test with, so these sorts of things can fall
>>>>>> through the cracks.
>>>>>>
>>>>>> Mark is right that the old solution involved patching wcslib before
>>>>>> shipping it with pywcs.
>>>>>>
>>>>>> However, as of version 1.10 (which you are using), the solution was to add:
>>>>>>
>>>>>>           #define wcsset wcsset_
>>>>>>
>>>>>> on Windows.  This works with the mingw32/cygwin compiler, but apparently
>>>>>> failing on the Microsoft compiler.
>>>>>>
>>>>>> There is an even newer solution in pywcs SVN which defines the following
>>>>>> on Windows.  This I believe to work on the Microsoft compilers based on
>>>>>> the report of another user:
>>>>>>
>>>>>> if sys.platform == 'win32':
>>>>>>            define_macros.append(('YY_NO_UNISTD_H', None))
>>>>>>            define_macros.append(('_CRT_SECURE_NO_WARNINGS', None))
>>>>>>            define_macros.append(('_NO_OLDNAMES', None)) # for mingw32
>>>>>>            define_macros.append(('NO_OLDNAMES', None)) # for mingw64
>>>>>>
>>>>>> You can either splice this into your current copy of setup.py, or build
>>>>>> from SVN.  Note that building from SVN currently requires having parts
>>>>>> of stsci_python installed (notable stsci.tools.stsci_distutils_hack).
>>>>>>
>>>>>> Mike
>>>>> Thanks, Mike.
>>>>>
>>>>> Could you elaborate on the above patch?  Do I need to import something
>>>>> other than sys?  Where is define_macros defined?
>>>> Of course -- first day back and I'm whipping through e-mail too quickly ;)
>>>>
>>>> This goes in defsetup.py -- there is already an "if sys.platform ==
>>>> 'win32'" clause -- you would just need to add the "OLDNAMES" lines to it.
>>>>
>>>> Mike
>>>> _______________________________________________
>>>> AstroPy mailing list
>>>> AstroPy at scipy.org
>>>> http://mail.scipy.org/mailman/listinfo/astropy
>>> I added the OLDNAMES lines as above and here is the result:
>>>
>>> C:\Projects\pywcs-1.10-4.7>setup.py install
>>> running install
>>> running build
>>> running build_py
>>> copying lib\svn_version.py ->    build\lib.win32-2.6\pywcs
>>> running build_ext
>>> building 'pywcs._pywcs' extension
>>> c:\Program Files\Microsoft Visual Studio 9.0\VC\BIN\cl.exe /c /nologo
>>> /Ox /MD /W3 /GS- /DNDEBUG -DECHO -DWCSTRIG_MACRO -DPYWCS_BUILD
>>> -D_GNU_SOURCE -DNDEBUG -DYY_NO_UNISTD_H -D_CRT_SECURE_NO_WARNINGS
>>> -D_NO_OLDNAMES -DNO_OLDNAMES -U
>>> DEBUG -IC:\Python26\lib\site-packages\numpy\core\include -I.\wcslib\C
>>> -Iwcslib\C -I.\src -IC:\Python26\include -IC:\Python26\PC
>>> /Tcwcslib\C\flexed/wcsbth.c
>>> /Fobuild\temp.win32-2.6\Release\wcslib\C\flexed/wcsbth.obj
>>> wcsbth.c
>>> .\wcslib\C\wcs.h(1396) : warning C4030: first formal parameter list
>>> longer than the second list
>>> .\wcslib\C\wcs.h(1396) : warning C4028: formal parameter 1 different
>>> from declaration
>>> .\wcslib\C\wcs.h(1396) : error C2040: 'wcsset' : 'int (wcsprm *)'
>>> differs in levels of indirection from 'int (wcsprm *)'
>>> error: command '"c:\Program Files\Microsoft Visual Studio
>>> 9.0\VC\BIN\cl.exe"' failed with exit status 2
>>>
>>> C:\Projects\pywcs-1.10-4.7>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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 erik.tollerud at gmail.com  Wed Jan  4 18:22:59 2012
From: erik.tollerud at gmail.com (Erik Tollerud)
Date: Wed, 4 Jan 2012 15:22:59 -0800
Subject: [AstroPy] Astropy at AAS?
Message-ID: <CAARXUwUwGJQDdtFjuNp_5v2s5Zq5q2nRM-nZHzn=hW+e2oVJOQ@mail.gmail.com>

Hello all,

We ended up not scheduling anything official for this AAS, but I'm
curious if there's anyone who would like to meet to ask
questions/comments about Astropy at next week's AAS meeting?  If
there's enough interest we could try to have an informal meeting over
a lunch or something.

-- 
Erik Tollerud


From rahpatel at ic.sunysb.edu  Wed Jan  4 20:20:41 2012
From: rahpatel at ic.sunysb.edu (Rahul Patel)
Date: Wed, 4 Jan 2012 20:20:41 -0500
Subject: [AstroPy] pywcs 1.10-4.7 install failure on Microsoft Windows
In-Reply-To: <4F0353DF.9040306@stsci.edu>
References: <CADb5CeivE8F8cMgc_5pH3zeay=eNifwCtcz6cMAe3HdNY=iCoQ@mail.gmail.com>
	<4EF456C4.5000308@astro.rug.nl>
	<CADb5CegT=pxDgQZAb1m+aK03z7yE+nwHv1u+uZNtjS7PkN6NAg@mail.gmail.com>
	<CAMe0V1bMDoP3r-pJQfP+kryka5C75XT5od5EZFpztypnDZHowQ@mail.gmail.com>
	<CA+G92RfW_y6WnF5qNbBiAiCM=A+6MEdb6SK5qouA5GYDoFcasQ@mail.gmail.com>
	<4EFB61B8.3030406@stsci.edu> <4F03039A.5030709@stsci.edu>
	<4F030EDA.7090400@noaa.gov>
	<4F031EFE.9010200@stsci.edu> <4F032DAE.10104@noaa.gov>
	<4F03395F.9050008@stsci.edu>
	<4F0340E4.7090800@noaa.gov> <4F0353DF.9040306@stsci.edu>
Message-ID: <CAMe0V1Z5E=cLHS8y9_ZtmQZ2FhR-ezKg4i++yOh3jJYMkr0P7g@mail.gmail.com>

So, I added the last two "oldnames" lines to the defsetup.py module, just
as you said Mike. There is a "win32" check for sys so I added that under
there. After it finished, I was able to import pywcs without any errors. I
haven't tested it or anything as I'm still learning all this, but I imagine
a successful import into Ipython indicates that it installed correctly.

-----------------------------------------------------------------
Rahul I. Patel

Rahul.Patel.1 at StonyBrook.edu <Rahul.Patel.1 at stonybrook.edu>
Department of Physics and Astronomy
State University of New York at Stony Brook
-----------------------------------------------------------------



On Tue, Jan 3, 2012 at 2:15 PM, Michael Droettboom <mdroe at stsci.edu> wrote:

> Ok.  I'm in the process of getting a Visual Studio environment set up
> here and will let you know what I discover.
>
> Mike
>
> On 01/03/2012 12:54 PM, Jim Vickroy wrote:
> > On 1/3/2012 10:22 AM, Michael Droettboom wrote:
> >> Hmm...  Do you have any luck if you remove this from defsetup.py?
> >>
> >> if sys.platform in ('win32', 'cygwin'):
> >>        h_file.write("""
> >> #define wcsset wcsset_
> >> """)
> >>
> >> Mike
> > Unfortunately, the same error trace occurs if the above line is
> > removed.  -- jv
> >
> >
> >> On 01/03/2012 11:32 AM, Jim Vickroy wrote:
> >>> On 1/3/2012 8:30 AM, Michael Droettboom wrote:
> >>>> On 01/03/2012 09:21 AM, Jim Vickroy wrote:
> >>>>> On 1/3/2012 6:33 AM, Michael Droettboom wrote:
> >>>>>> My apologies that this isn't working for you -- I don't have access
> to
> >>>>>> Visual Studio 9.0 to test with, so these sorts of things can fall
> >>>>>> through the cracks.
> >>>>>>
> >>>>>> Mark is right that the old solution involved patching wcslib before
> >>>>>> shipping it with pywcs.
> >>>>>>
> >>>>>> However, as of version 1.10 (which you are using), the solution was
> to add:
> >>>>>>
> >>>>>>           #define wcsset wcsset_
> >>>>>>
> >>>>>> on Windows.  This works with the mingw32/cygwin compiler, but
> apparently
> >>>>>> failing on the Microsoft compiler.
> >>>>>>
> >>>>>> There is an even newer solution in pywcs SVN which defines the
> following
> >>>>>> on Windows.  This I believe to work on the Microsoft compilers
> based on
> >>>>>> the report of another user:
> >>>>>>
> >>>>>> if sys.platform == 'win32':
> >>>>>>            define_macros.append(('YY_NO_UNISTD_H', None))
> >>>>>>            define_macros.append(('_CRT_SECURE_NO_WARNINGS', None))
> >>>>>>            define_macros.append(('_NO_OLDNAMES', None)) # for
> mingw32
> >>>>>>            define_macros.append(('NO_OLDNAMES', None)) # for mingw64
> >>>>>>
> >>>>>> You can either splice this into your current copy of setup.py, or
> build
> >>>>>> from SVN.  Note that building from SVN currently requires having
> parts
> >>>>>> of stsci_python installed (notable
> stsci.tools.stsci_distutils_hack).
> >>>>>>
> >>>>>> Mike
> >>>>> Thanks, Mike.
> >>>>>
> >>>>> Could you elaborate on the above patch?  Do I need to import
> something
> >>>>> other than sys?  Where is define_macros defined?
> >>>> Of course -- first day back and I'm whipping through e-mail too
> quickly ;)
> >>>>
> >>>> This goes in defsetup.py -- there is already an "if sys.platform ==
> >>>> 'win32'" clause -- you would just need to add the "OLDNAMES" lines to
> it.
> >>>>
> >>>> Mike
> >>>> _______________________________________________
> >>>> AstroPy mailing list
> >>>> AstroPy at scipy.org
> >>>> http://mail.scipy.org/mailman/listinfo/astropy
> >>> I added the OLDNAMES lines as above and here is the result:
> >>>
> >>> C:\Projects\pywcs-1.10-4.7>setup.py install
> >>> running install
> >>> running build
> >>> running build_py
> >>> copying lib\svn_version.py ->    build\lib.win32-2.6\pywcs
> >>> running build_ext
> >>> building 'pywcs._pywcs' extension
> >>> c:\Program Files\Microsoft Visual Studio 9.0\VC\BIN\cl.exe /c /nologo
> >>> /Ox /MD /W3 /GS- /DNDEBUG -DECHO -DWCSTRIG_MACRO -DPYWCS_BUILD
> >>> -D_GNU_SOURCE -DNDEBUG -DYY_NO_UNISTD_H -D_CRT_SECURE_NO_WARNINGS
> >>> -D_NO_OLDNAMES -DNO_OLDNAMES -U
> >>> DEBUG -IC:\Python26\lib\site-packages\numpy\core\include -I.\wcslib\C
> >>> -Iwcslib\C -I.\src -IC:\Python26\include -IC:\Python26\PC
> >>> /Tcwcslib\C\flexed/wcsbth.c
> >>> /Fobuild\temp.win32-2.6\Release\wcslib\C\flexed/wcsbth.obj
> >>> wcsbth.c
> >>> .\wcslib\C\wcs.h(1396) : warning C4030: first formal parameter list
> >>> longer than the second list
> >>> .\wcslib\C\wcs.h(1396) : warning C4028: formal parameter 1 different
> >>> from declaration
> >>> .\wcslib\C\wcs.h(1396) : error C2040: 'wcsset' : 'int (wcsprm *)'
> >>> differs in levels of indirection from 'int (wcsprm *)'
> >>> error: command '"c:\Program Files\Microsoft Visual Studio
> >>> 9.0\VC\BIN\cl.exe"' failed with exit status 2
> >>>
> >>> C:\Projects\pywcs-1.10-4.7>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> 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/20120104/ccb6428e/attachment.html>

From andrew.f.ptak at nasa.gov  Wed Jan  4 22:21:23 2012
From: andrew.f.ptak at nasa.gov (Andrew Ptak)
Date: Wed, 4 Jan 2012 22:21:23 -0500
Subject: [AstroPy] Astropy at AAS?
In-Reply-To: <CAARXUwUwGJQDdtFjuNp_5v2s5Zq5q2nRM-nZHzn=hW+e2oVJOQ@mail.gmail.com>
References: <CAARXUwUwGJQDdtFjuNp_5v2s5Zq5q2nRM-nZHzn=hW+e2oVJOQ@mail.gmail.com>
Message-ID: <FEF7522E-1E3F-4767-8E92-5BA05EB1ADCB@nasa.gov>

Hello Erik,
I will be at the AAS meeting and would be very interested in chatting about astropy over lunch.

Andy Ptak

On Jan 4, 2012, at 6:22 PM, Erik Tollerud wrote:

> Hello all,
> 
> We ended up not scheduling anything official for this AAS, but I'm
> curious if there's anyone who would like to meet to ask
> questions/comments about Astropy at next week's AAS meeting?  If
> there's enough interest we could try to have an informal meeting over
> a lunch or something.
> 
> -- 
> Erik Tollerud
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy

Andrew Ptak
Research Astrophysicist
NASA/GSFC
X-ray Astrophysics Lab Code 662
Building 34 room S289
andrew.f.ptak at nasa.gov
office: 301-286-1154
cell: 443-415-1495




From crawford at saao.ac.za  Wed Jan  4 22:35:24 2012
From: crawford at saao.ac.za (Steve Crawford)
Date: Thu, 05 Jan 2012 05:35:24 +0200 (SAST)
Subject: [AstroPy] Astropy at AAS?
In-Reply-To: <CAARXUwUwGJQDdtFjuNp_5v2s5Zq5q2nRM-nZHzn=hW+e2oVJOQ@mail.gmail.com>
Message-ID: <067e9b72-53fd-40ca-9604-063c0d55fdb8@mailcape>


I'll be there at the AAS and happy to meet up with anyone else there.  

----- Original Message -----
> From: "Erik Tollerud" <erik.tollerud at gmail.com>
> To: astropy at scipy.org
> Sent: Wednesday, 4 January, 2012 6:22:59 PM
> Subject: [AstroPy] Astropy at AAS?
> 
> Hello all,
> 
> We ended up not scheduling anything official for this AAS, but I'm
> curious if there's anyone who would like to meet to ask
> questions/comments about Astropy at next week's AAS meeting?  If
> there's enough interest we could try to have an informal meeting over
> a lunch or something.
> 
> --
> Erik Tollerud
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
> 


From mdroe at stsci.edu  Thu Jan  5 13:06:18 2012
From: mdroe at stsci.edu (Michael Droettboom)
Date: Thu, 5 Jan 2012 13:06:18 -0500
Subject: [AstroPy] pywcs 1.10-4.7 install failure on Microsoft Windows
In-Reply-To: <CAMe0V1Z5E=cLHS8y9_ZtmQZ2FhR-ezKg4i++yOh3jJYMkr0P7g@mail.gmail.com>
References: <CADb5CeivE8F8cMgc_5pH3zeay=eNifwCtcz6cMAe3HdNY=iCoQ@mail.gmail.com>
	<4EF456C4.5000308@astro.rug.nl>
	<CADb5CegT=pxDgQZAb1m+aK03z7yE+nwHv1u+uZNtjS7PkN6NAg@mail.gmail.com>
	<CAMe0V1bMDoP3r-pJQfP+kryka5C75XT5od5EZFpztypnDZHowQ@mail.gmail.com>
	<CA+G92RfW_y6WnF5qNbBiAiCM=A+6MEdb6SK5qouA5GYDoFcasQ@mail.gmail.com>
	<4EFB61B8.3030406@stsci.edu> <4F03039A.5030709@stsci.edu>
	<4F030EDA.7090400@noaa.gov> <4F031EFE.9010200@stsci.edu>
	<4F032DAE.10104@noaa.gov> <4F03395F.9050008@stsci.edu>
	<4F0340E4.7090800@noaa.gov> <4F0353DF.9040306@stsci.edu>
	<CAMe0V1Z5E=cLHS8y9_ZtmQZ2FhR-ezKg4i++yOh3jJYMkr0P7g@mail.gmail.com>
Message-ID: <4F05E69A.3080501@stsci.edu>

Ok.  I've made a new pywcs release with these changes (among many 
others).  You may want to update to it if possible.

Mike

On 01/04/2012 08:20 PM, Rahul Patel wrote:
> So, I added the last two "oldnames" lines to the defsetup.py module, 
> just as you said Mike. There is a "win32" check for sys so I added 
> that under there. After it finished, I was able to import pywcs 
> without any errors. I haven't tested it or anything as I'm still 
> learning all this, but I imagine a successful import into Ipython 
> indicates that it installed correctly.
>
> -----------------------------------------------------------------
> Rahul I. Patel
>
> Rahul.Patel.1 at StonyBrook.edu <mailto:Rahul.Patel.1 at stonybrook.edu>
> Department of Physics and Astronomy
> State University of New York at Stony Brook
> -----------------------------------------------------------------
>
>
>
> On Tue, Jan 3, 2012 at 2:15 PM, Michael Droettboom <mdroe at stsci.edu 
> <mailto:mdroe at stsci.edu>> wrote:
>
>     Ok.  I'm in the process of getting a Visual Studio environment set up
>     here and will let you know what I discover.
>
>     Mike
>
>     On 01/03/2012 12:54 PM, Jim Vickroy wrote:
>     > On 1/3/2012 10:22 AM, Michael Droettboom wrote:
>     >> Hmm...  Do you have any luck if you remove this from defsetup.py?
>     >>
>     >> if sys.platform in ('win32', 'cygwin'):
>     >>        h_file.write("""
>     >> #define wcsset wcsset_
>     >> """)
>     >>
>     >> Mike
>     > Unfortunately, the same error trace occurs if the above line is
>     > removed.  -- jv
>     >
>     >
>     >> On 01/03/2012 11:32 AM, Jim Vickroy wrote:
>     >>> On 1/3/2012 8:30 AM, Michael Droettboom wrote:
>     >>>> On 01/03/2012 09:21 AM, Jim Vickroy wrote:
>     >>>>> On 1/3/2012 6:33 AM, Michael Droettboom wrote:
>     >>>>>> My apologies that this isn't working for you -- I don't
>     have access to
>     >>>>>> Visual Studio 9.0 to test with, so these sorts of things
>     can fall
>     >>>>>> through the cracks.
>     >>>>>>
>     >>>>>> Mark is right that the old solution involved patching
>     wcslib before
>     >>>>>> shipping it with pywcs.
>     >>>>>>
>     >>>>>> However, as of version 1.10 (which you are using), the
>     solution was to add:
>     >>>>>>
>     >>>>>>           #define wcsset wcsset_
>     >>>>>>
>     >>>>>> on Windows.  This works with the mingw32/cygwin compiler,
>     but apparently
>     >>>>>> failing on the Microsoft compiler.
>     >>>>>>
>     >>>>>> There is an even newer solution in pywcs SVN which defines
>     the following
>     >>>>>> on Windows.  This I believe to work on the Microsoft
>     compilers based on
>     >>>>>> the report of another user:
>     >>>>>>
>     >>>>>> if sys.platform == 'win32':
>     >>>>>>            define_macros.append(('YY_NO_UNISTD_H', None))
>     >>>>>>            define_macros.append(('_CRT_SECURE_NO_WARNINGS',
>     None))
>     >>>>>>            define_macros.append(('_NO_OLDNAMES', None)) #
>     for mingw32
>     >>>>>>            define_macros.append(('NO_OLDNAMES', None)) #
>     for mingw64
>     >>>>>>
>     >>>>>> You can either splice this into your current copy of
>     setup.py, or build
>     >>>>>> from SVN.  Note that building from SVN currently requires
>     having parts
>     >>>>>> of stsci_python installed (notable
>     stsci.tools.stsci_distutils_hack).
>     >>>>>>
>     >>>>>> Mike
>     >>>>> Thanks, Mike.
>     >>>>>
>     >>>>> Could you elaborate on the above patch?  Do I need to import
>     something
>     >>>>> other than sys?  Where is define_macros defined?
>     >>>> Of course -- first day back and I'm whipping through e-mail
>     too quickly ;)
>     >>>>
>     >>>> This goes in defsetup.py -- there is already an "if
>     sys.platform ==
>     >>>> 'win32'" clause -- you would just need to add the "OLDNAMES"
>     lines to it.
>     >>>>
>     >>>> Mike
>     >>>> _______________________________________________
>     >>>> AstroPy mailing list
>     >>>> AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>     >>>> http://mail.scipy.org/mailman/listinfo/astropy
>     >>> I added the OLDNAMES lines as above and here is the result:
>     >>>
>     >>> C:\Projects\pywcs-1.10-4.7>setup.py install
>     >>> running install
>     >>> running build
>     >>> running build_py
>     >>> copying lib\svn_version.py ->    build\lib.win32-2.6\pywcs
>     >>> running build_ext
>     >>> building 'pywcs._pywcs' extension
>     >>> c:\Program Files\Microsoft Visual Studio 9.0\VC\BIN\cl.exe /c
>     /nologo
>     >>> /Ox /MD /W3 /GS- /DNDEBUG -DECHO -DWCSTRIG_MACRO -DPYWCS_BUILD
>     >>> -D_GNU_SOURCE -DNDEBUG -DYY_NO_UNISTD_H -D_CRT_SECURE_NO_WARNINGS
>     >>> -D_NO_OLDNAMES -DNO_OLDNAMES -U
>     >>> DEBUG -IC:\Python26\lib\site-packages\numpy\core\include
>     -I.\wcslib\C
>     >>> -Iwcslib\C -I.\src -IC:\Python26\include -IC:\Python26\PC
>     >>> /Tcwcslib\C\flexed/wcsbth.c
>     >>> /Fobuild\temp.win32-2.6\Release\wcslib\C\flexed/wcsbth.obj
>     >>> wcsbth.c
>     >>> .\wcslib\C\wcs.h(1396) : warning C4030: first formal parameter
>     list
>     >>> longer than the second list
>     >>> .\wcslib\C\wcs.h(1396) : warning C4028: formal parameter 1
>     different
>     >>> from declaration
>     >>> .\wcslib\C\wcs.h(1396) : error C2040: 'wcsset' : 'int (wcsprm *)'
>     >>> differs in levels of indirection from 'int (wcsprm *)'
>     >>> error: command '"c:\Program Files\Microsoft Visual Studio
>     >>> 9.0\VC\BIN\cl.exe"' failed with exit status 2
>     >>>
>     >>> C:\Projects\pywcs-1.10-4.7>
>     >>>
>     >>>
>     >>>
>     >>> _______________________________________________
>     >>> 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
>
>

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

From mdroe at stsci.edu  Thu Jan  5 13:08:29 2012
From: mdroe at stsci.edu (Michael Droettboom)
Date: Thu, 5 Jan 2012 13:08:29 -0500
Subject: [AstroPy] ANN: pywcs 1.11 released
Message-ID: <4F05E71D.8020904@stsci.edu>

A new version of standalone pywcs has been released.  It is available 
from here:

https://trac.assembla.com/astrolib/wiki/WikiStart

Version 1.11
============

NEW FEATURES:

- Updated to wcslib version 4.8.2, which gives much more detailed
   error messages.  Exceptions raised due to invalid WCS keywords
   should now be more informative.

- Undefined values that are the result of p2s and s2p are now set to
   NaN.  Previously, one had to examine the stat result vector to
   determine which results were invalid.

- Added functions get_pc() and get_cdelt().  These provide a way to
   always get the canonical representation of the linear transformation
   matrix, whether the header specified it in PC, CD or CROTA form.

BROADER COMPATIBILITY:

- Supports Python 3.x

- Long-running process will now release the Python GIL to better
   support Python multithreading.

- Builds on Microsoft Windows using mingw32, mingw64 and Visual Studio
   9.0 and 10.0 without severely patching wcslib.

- pywcs will now run without pyfits, though the SIP and distortion
   lookup table functionality is unavailable.

BUG FIXES:

- The dimensions of the cd and pc matrices were formerly always returned
   as 2x2.  They now are sized according to naxis.

MISCELLANEOUS:

- Lots of new unit tests

- Setting wcs.wcs.cunit will now verify that the values are valid unit
   strings.

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

From ebressert at cfa.harvard.edu  Thu Jan  5 14:09:17 2012
From: ebressert at cfa.harvard.edu (Eli Bressert)
Date: Thu, 5 Jan 2012 20:09:17 +0100
Subject: [AstroPy] AstroPy Digest, Vol 65, Issue 3
In-Reply-To: <mailman.1.1325786402.3966.astropy@scipy.org>
References: <mailman.1.1325786402.3966.astropy@scipy.org>
Message-ID: <CA+3+fTbmSHHkVj6531HBS7NW5o4GbHpwnFRUMzSqOQ_OP7ZTWA@mail.gmail.com>

Hi Erik,

I'll be at AAS as well, so I would be interested in meeting up over
lunch time as well.

Cheers,
Eli


On Thu, Jan 5, 2012 at 7:00 PM,  <astropy-request at scipy.org> wrote:
> Send AstroPy mailing list submissions to
> ? ? ? ?astropy at scipy.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> ? ? ? ?http://mail.scipy.org/mailman/listinfo/astropy
> or, via email, send a message with subject or body 'help' to
> ? ? ? ?astropy-request at scipy.org
>
> You can reach the person managing the list at
> ? ? ? ?astropy-owner at scipy.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of AstroPy digest..."
>
>
> Today's Topics:
>
> ? 1. Astropy at AAS? (Erik Tollerud)
> ? 2. Re: pywcs 1.10-4.7 install failure on Microsoft Windows
> ? ? ?(Rahul Patel)
> ? 3. Re: Astropy at AAS? (Andrew Ptak)
> ? 4. Re: Astropy at AAS? (Steve Crawford)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 4 Jan 2012 15:22:59 -0800
> From: Erik Tollerud <erik.tollerud at gmail.com>
> Subject: [AstroPy] Astropy at AAS?
> To: astropy at scipy.org
> Message-ID:
> ? ? ? ?<CAARXUwUwGJQDdtFjuNp_5v2s5Zq5q2nRM-nZHzn=hW+e2oVJOQ at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hello all,
>
> We ended up not scheduling anything official for this AAS, but I'm
> curious if there's anyone who would like to meet to ask
> questions/comments about Astropy at next week's AAS meeting? ?If
> there's enough interest we could try to have an informal meeting over
> a lunch or something.
>
> --
> Erik Tollerud
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 4 Jan 2012 20:20:41 -0500
> From: Rahul Patel <rahpatel at ic.sunysb.edu>
> Subject: Re: [AstroPy] pywcs 1.10-4.7 install failure on Microsoft
> ? ? ? ?Windows
> To: Michael Droettboom <mdroe at stsci.edu>
> Cc: astropy at scipy.org
> Message-ID:
> ? ? ? ?<CAMe0V1Z5E=cLHS8y9_ZtmQZ2FhR-ezKg4i++yOh3jJYMkr0P7g at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> So, I added the last two "oldnames" lines to the defsetup.py module, just
> as you said Mike. There is a "win32" check for sys so I added that under
> there. After it finished, I was able to import pywcs without any errors. I
> haven't tested it or anything as I'm still learning all this, but I imagine
> a successful import into Ipython indicates that it installed correctly.
>
> -----------------------------------------------------------------
> Rahul I. Patel
>
> Rahul.Patel.1 at StonyBrook.edu <Rahul.Patel.1 at stonybrook.edu>
> Department of Physics and Astronomy
> State University of New York at Stony Brook
> -----------------------------------------------------------------
>
>
>
> On Tue, Jan 3, 2012 at 2:15 PM, Michael Droettboom <mdroe at stsci.edu> wrote:
>
>> Ok. ?I'm in the process of getting a Visual Studio environment set up
>> here and will let you know what I discover.
>>
>> Mike
>>
>> On 01/03/2012 12:54 PM, Jim Vickroy wrote:
>> > On 1/3/2012 10:22 AM, Michael Droettboom wrote:
>> >> Hmm... ?Do you have any luck if you remove this from defsetup.py?
>> >>
>> >> if sys.platform in ('win32', 'cygwin'):
>> >> ? ? ? ?h_file.write("""
>> >> #define wcsset wcsset_
>> >> """)
>> >>
>> >> Mike
>> > Unfortunately, the same error trace occurs if the above line is
>> > removed. ?-- jv
>> >
>> >
>> >> On 01/03/2012 11:32 AM, Jim Vickroy wrote:
>> >>> On 1/3/2012 8:30 AM, Michael Droettboom wrote:
>> >>>> On 01/03/2012 09:21 AM, Jim Vickroy wrote:
>> >>>>> On 1/3/2012 6:33 AM, Michael Droettboom wrote:
>> >>>>>> My apologies that this isn't working for you -- I don't have access
>> to
>> >>>>>> Visual Studio 9.0 to test with, so these sorts of things can fall
>> >>>>>> through the cracks.
>> >>>>>>
>> >>>>>> Mark is right that the old solution involved patching wcslib before
>> >>>>>> shipping it with pywcs.
>> >>>>>>
>> >>>>>> However, as of version 1.10 (which you are using), the solution was
>> to add:
>> >>>>>>
>> >>>>>> ? ? ? ? ? #define wcsset wcsset_
>> >>>>>>
>> >>>>>> on Windows. ?This works with the mingw32/cygwin compiler, but
>> apparently
>> >>>>>> failing on the Microsoft compiler.
>> >>>>>>
>> >>>>>> There is an even newer solution in pywcs SVN which defines the
>> following
>> >>>>>> on Windows. ?This I believe to work on the Microsoft compilers
>> based on
>> >>>>>> the report of another user:
>> >>>>>>
>> >>>>>> if sys.platform == 'win32':
>> >>>>>> ? ? ? ? ? ?define_macros.append(('YY_NO_UNISTD_H', None))
>> >>>>>> ? ? ? ? ? ?define_macros.append(('_CRT_SECURE_NO_WARNINGS', None))
>> >>>>>> ? ? ? ? ? ?define_macros.append(('_NO_OLDNAMES', None)) # for
>> mingw32
>> >>>>>> ? ? ? ? ? ?define_macros.append(('NO_OLDNAMES', None)) # for mingw64
>> >>>>>>
>> >>>>>> You can either splice this into your current copy of setup.py, or
>> build
>> >>>>>> from SVN. ?Note that building from SVN currently requires having
>> parts
>> >>>>>> of stsci_python installed (notable
>> stsci.tools.stsci_distutils_hack).
>> >>>>>>
>> >>>>>> Mike
>> >>>>> Thanks, Mike.
>> >>>>>
>> >>>>> Could you elaborate on the above patch? ?Do I need to import
>> something
>> >>>>> other than sys? ?Where is define_macros defined?
>> >>>> Of course -- first day back and I'm whipping through e-mail too
>> quickly ;)
>> >>>>
>> >>>> This goes in defsetup.py -- there is already an "if sys.platform ==
>> >>>> 'win32'" clause -- you would just need to add the "OLDNAMES" lines to
>> it.
>> >>>>
>> >>>> Mike
>> >>>> _______________________________________________
>> >>>> AstroPy mailing list
>> >>>> AstroPy at scipy.org
>> >>>> http://mail.scipy.org/mailman/listinfo/astropy
>> >>> I added the OLDNAMES lines as above and here is the result:
>> >>>
>> >>> C:\Projects\pywcs-1.10-4.7>setup.py install
>> >>> running install
>> >>> running build
>> >>> running build_py
>> >>> copying lib\svn_version.py -> ? ?build\lib.win32-2.6\pywcs
>> >>> running build_ext
>> >>> building 'pywcs._pywcs' extension
>> >>> c:\Program Files\Microsoft Visual Studio 9.0\VC\BIN\cl.exe /c /nologo
>> >>> /Ox /MD /W3 /GS- /DNDEBUG -DECHO -DWCSTRIG_MACRO -DPYWCS_BUILD
>> >>> -D_GNU_SOURCE -DNDEBUG -DYY_NO_UNISTD_H -D_CRT_SECURE_NO_WARNINGS
>> >>> -D_NO_OLDNAMES -DNO_OLDNAMES -U
>> >>> DEBUG -IC:\Python26\lib\site-packages\numpy\core\include -I.\wcslib\C
>> >>> -Iwcslib\C -I.\src -IC:\Python26\include -IC:\Python26\PC
>> >>> /Tcwcslib\C\flexed/wcsbth.c
>> >>> /Fobuild\temp.win32-2.6\Release\wcslib\C\flexed/wcsbth.obj
>> >>> wcsbth.c
>> >>> .\wcslib\C\wcs.h(1396) : warning C4030: first formal parameter list
>> >>> longer than the second list
>> >>> .\wcslib\C\wcs.h(1396) : warning C4028: formal parameter 1 different
>> >>> from declaration
>> >>> .\wcslib\C\wcs.h(1396) : error C2040: 'wcsset' : 'int (wcsprm *)'
>> >>> differs in levels of indirection from 'int (wcsprm *)'
>> >>> error: command '"c:\Program Files\Microsoft Visual Studio
>> >>> 9.0\VC\BIN\cl.exe"' failed with exit status 2
>> >>>
>> >>> C:\Projects\pywcs-1.10-4.7>
>> >>>
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> 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.scipy.org/pipermail/astropy/attachments/20120104/ccb6428e/attachment-0001.html
>
> ------------------------------
>
> Message: 3
> Date: Wed, 4 Jan 2012 22:21:23 -0500
> From: Andrew Ptak <andrew.f.ptak at nasa.gov>
> Subject: Re: [AstroPy] Astropy at AAS?
> To: Erik Tollerud <erik.tollerud at gmail.com>
> Cc: "astropy at scipy.org" <astropy at scipy.org>
> Message-ID: <FEF7522E-1E3F-4767-8E92-5BA05EB1ADCB at nasa.gov>
> Content-Type: text/plain; charset=us-ascii
>
> Hello Erik,
> I will be at the AAS meeting and would be very interested in chatting about astropy over lunch.
>
> Andy Ptak
>
> On Jan 4, 2012, at 6:22 PM, Erik Tollerud wrote:
>
>> Hello all,
>>
>> We ended up not scheduling anything official for this AAS, but I'm
>> curious if there's anyone who would like to meet to ask
>> questions/comments about Astropy at next week's AAS meeting? ?If
>> there's enough interest we could try to have an informal meeting over
>> a lunch or something.
>>
>> --
>> Erik Tollerud
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
>
> Andrew Ptak
> Research Astrophysicist
> NASA/GSFC
> X-ray Astrophysics Lab Code 662
> Building 34 room S289
> andrew.f.ptak at nasa.gov
> office: 301-286-1154
> cell: 443-415-1495
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 05 Jan 2012 05:35:24 +0200 (SAST)
> From: Steve Crawford <crawford at saao.ac.za>
> Subject: Re: [AstroPy] Astropy at AAS?
> To: Erik Tollerud <erik.tollerud at gmail.com>
> Cc: astropy at scipy.org
> Message-ID: <067e9b72-53fd-40ca-9604-063c0d55fdb8 at mailcape>
> Content-Type: text/plain; charset=utf-8
>
>
> I'll be there at the AAS and happy to meet up with anyone else there.
>
> ----- Original Message -----
>> From: "Erik Tollerud" <erik.tollerud at gmail.com>
>> To: astropy at scipy.org
>> Sent: Wednesday, 4 January, 2012 6:22:59 PM
>> Subject: [AstroPy] Astropy at AAS?
>>
>> Hello all,
>>
>> We ended up not scheduling anything official for this AAS, but I'm
>> curious if there's anyone who would like to meet to ask
>> questions/comments about Astropy at next week's AAS meeting? ?If
>> there's enough interest we could try to have an informal meeting over
>> a lunch or something.
>>
>> --
>> Erik Tollerud
>> _______________________________________________
>> 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
>
>
> End of AstroPy Digest, Vol 65, Issue 3
> **************************************
>


From astropy at liska.ath.cx  Thu Jan  5 17:30:13 2012
From: astropy at liska.ath.cx (=?utf-8?Q?Ol=D0=B5?= Streicher)
Date: Thu, 05 Jan 2012 23:30:13 +0100
Subject: [AstroPy] ANN: pywcs 1.11 released
References: <4F05E71D.8020904@stsci.edu>
Message-ID: <87vcoppytm.fsf@news.ole.ath.cx>

Hi Michael,

Michael Droettboom <mdroe at stsci.edu> writes:
> A new version of standalone pywcs has been released.? Version 1.11
> MISCELLANEOUS:
> - Lots of new unit tests

Could you tag the version in the Subversion VCS like you did for the
version 1.10? I am building the Debian package, and I'd like to download
the unit tests that correspond to the release.

Best regards

Ole


From jslavin at cfa.harvard.edu  Fri Jan  6 15:58:16 2012
From: jslavin at cfa.harvard.edu (Jonathan Slavin)
Date: Fri, 06 Jan 2012 15:58:16 -0500
Subject: [AstroPy] Astropy at AAS?
Message-ID: <1325883496.827.31.camel@shevek>

Erik,

I will also be at the AAS and would like to know about any plans for a
get-together.  I will be meeting with collaborators as well, so
depending on when it happens, I may not be able to attend, but I am
interested.

Jon

> Message: 1
> Date: Wed, 4 Jan 2012 15:22:59 -0800
> From: Erik Tollerud <erik.tollerud at gmail.com>
> Subject: [AstroPy] Astropy at AAS?
> To: astropy at scipy.org
> Message-ID:
>         <CAARXUwUwGJQDdtFjuNp_5v2s5Zq5q2nRM-nZHzn=hW
> +e2oVJOQ at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Hello all,
> 
> We ended up not scheduling anything official for this AAS, but I'm
> curious if there's anyone who would like to meet to ask
> questions/comments about Astropy at next week's AAS meeting?  If
> there's enough interest we could try to have an informal meeting over
> a lunch or something.
> 
> -- 
> Erik Tollerud
> 
> 
-- 
______________________________________________________________
Jonathan D. Slavin              Harvard-Smithsonian CfA
jslavin at cfa.harvard.edu         60 Garden Street, MS 83
phone: (617) 496-7981           Cambridge, MA 02138-1516
 cell: (781) 363-0035           USA
______________________________________________________________



From indiajoe at gmail.com  Sat Jan  7 02:23:37 2012
From: indiajoe at gmail.com (Joe Philip Ninan)
Date: Sat, 7 Jan 2012 12:53:37 +0530
Subject: [AstroPy] photometry in pyraf
In-Reply-To: <CAJ_T+b6cpaD9Va9O6GP_C2ViNt=Yw+F3kuSnHFLpGEu7Q5HzBg@mail.gmail.com>
References: <CAJ_T+b6cpaD9Va9O6GP_C2ViNt=Yw+F3kuSnHFLpGEu7Q5HzBg@mail.gmail.com>
Message-ID: <CAJ_T+b4Qz=cuAq07-iNZY30TyL_WS64UWHr=4tK7icXr28bAYQ@mail.gmail.com>

Hi,
I have been recently rewriting to pyraf all my photometry iraf scripts.
For using the daofind and then phot task in noan.digiphot.daophot we
first have to set the parameter files.
Following is that section from my code.
#--------------------(all the variables fwhm psfradi sigma datamin
aperture etc. have been defined before in code)---------
??? iraf.daopar(matchra=fwhm, psfrad=psfradi, fitrad=fwhm)
??? iraf.datapar(fwhmpsf=fwhm, sigma=sigma, datamin=datamin,
datamax=65000 , readnoi=4.8 , epadu=1.22 ,itime=intime,
ifilter=filterr)
??? iraf.fitskypar(annulus=270, dannulu=12 )
??? iraf.photpar(apertur=aperture)
??? iraf.daofind(image=img)
??? #Going forward to do phot
??? iraf.phot(image=img)
#----------------------------------------------------
Now , when I run this code. It does displays the epar daopar, datapar
etc in the GUI epar window of the pyraf with all correct values set.
But when I press "Save & Quit" button and reaches the daofind or phot
task. It is executing without all the seted parameters.
It looks like inspite of me clicking on "Save & Quit" button. It is
not getting saved. and the phot and daofind task are using some
default setting in my uparm/
In iraf, I had the same problem if i gave :wq in epar. But if I gave
:w and then :q separately it used to work.
There is no :w equivalent button in pyraf's GUI epar window.

Can somebody point out some workaround for this problem? Is it
possible in pyraf to get the non GUI epar window of iraf?
Thanking you
Joe

--
/---------------------------------------------------------------
"GNU/Linux: because a PC is a terrible thing to waste" -? GNU Generation


From taro at ap.smu.ca  Sat Jan  7 10:39:00 2012
From: taro at ap.smu.ca (Taro Sato)
Date: Sat, 7 Jan 2012 11:39:00 -0400
Subject: [AstroPy] photometry in pyraf
In-Reply-To: <CAJ_T+b4Qz=cuAq07-iNZY30TyL_WS64UWHr=4tK7icXr28bAYQ@mail.gmail.com>
References: <CAJ_T+b6cpaD9Va9O6GP_C2ViNt=Yw+F3kuSnHFLpGEu7Q5HzBg@mail.gmail.com>
	<CAJ_T+b4Qz=cuAq07-iNZY30TyL_WS64UWHr=4tK7icXr28bAYQ@mail.gmail.com>
Message-ID: <CA+ABecwjd8NQKd+89TtBJF7J_nMHLpA2uHrsk4+xrin+h6JH8w@mail.gmail.com>

On Sat, Jan 7, 2012 at 3:23 AM, Joe Philip Ninan <indiajoe at gmail.com> wrote:
> Hi,
> I have been recently rewriting to pyraf all my photometry iraf scripts.
> For using the daofind and then phot task in noan.digiphot.daophot we
> first have to set the parameter files.
> Following is that section from my code.
> #--------------------(all the variables fwhm psfradi sigma datamin
> aperture etc. have been defined before in code)---------
> ??? iraf.daopar(matchra=fwhm, psfrad=psfradi, fitrad=fwhm)
> ??? iraf.datapar(fwhmpsf=fwhm, sigma=sigma, datamin=datamin,
> datamax=65000 , readnoi=4.8 , epadu=1.22 ,itime=intime,
> ifilter=filterr)
> ??? iraf.fitskypar(annulus=270, dannulu=12 )
> ??? iraf.photpar(apertur=aperture)
> ??? iraf.daofind(image=img)
> ??? #Going forward to do phot
> ??? iraf.phot(image=img)
> #----------------------------------------------------
> Now , when I run this code. It does displays the epar daopar, datapar
> etc in the GUI epar window of the pyraf with all correct values set.
> But when I press "Save & Quit" button and reaches the daofind or phot
> task. It is executing without all the seted parameters.
> It looks like inspite of me clicking on "Save & Quit" button. It is
> not getting saved. and the phot and daofind task are using some
> default setting in my uparm/
> In iraf, I had the same problem if i gave :wq in epar. But if I gave
> :w and then :q separately it used to work.
> There is no :w equivalent button in pyraf's GUI epar window.
>
> Can somebody point out some workaround for this problem? Is it
> possible in pyraf to get the non GUI epar window of iraf?
> Thanking you
> Joe
>
> --
> /---------------------------------------------------------------
> "GNU/Linux: because a PC is a terrible thing to waste" -? GNU Generation
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy


Not sure if this is the type of thing you wish to do, but since I
don't trust (or remember) the exact behavior of which set of
parameters gets actually used, my approach is to reset all parameters
to default and override those I need to change.  The following is my
template for using an IRAF task with PyRAF.  This won't prompt you to
edit parameters on GUI though, if that's what you need to do...

Hope this helps a tiny bit.



####### BEGIN ##########

#!/usr/bin/env python
from pyraf import iraf
from pyraf.irafpar import IrafParList

def default_irafpar(task):
   # Return the IrafParList object for default parameters.
   return IrafParList(task.getName(), parlist=task.getDefaultParList())

def main():
   # Load IRAF packages.
   iraf.gemini(_doprint=0)
   iraf.gmos(_doprint=0)

   # Get default parameters and override some.
   yes, no = 'yes', 'no'
   plist = default_irafpar(iraf.gprepare)
   plist.setParList(inimages = 'someimage.fits',
                    rawpath = '/astro/data/',
                    fl_addmdf = yes,
                    mdfdir = '../mdf/',
                    logfile = '',
                    verbose = yes)

   # Run the task.
   iraf.gsprepare(ParList=plist)

   return

if __name__ == '__main__':
   main()

######### END ###############




--
Taro Sato
Department of Astronomy & Physics
Saint Mary's University             email: taro at ap.smu.ca
Halifax, NS B3H 3C3                 phone: (902)420-5018
Canada                                web: http://ap.smu.ca/~taro


From taro at ap.smu.ca  Sat Jan  7 17:59:27 2012
From: taro at ap.smu.ca (Taro Sato)
Date: Sat, 7 Jan 2012 18:59:27 -0400
Subject: [AstroPy] Including kcorrect as a astropy affiliated package?
Message-ID: <CA+ABecxZr4bE_aou8A3wHDKrWx2QdHeFXX_PyQXZVKYz76WG-w@mail.gmail.com>

Hi there.  I have not been diligently following the astropy discussion
lately, so I may sound totally ignorant but please bear with me.

I've written a Python wrapper for kcorrect by Michael Blanton, a
popular IDL/C tool for k-correction, photo-z, and all that cool stuff
people love to do with spectral-energy distribution fitting for high-z
galaxies these days.  I needed it for research recently and updated
the Python version to work with the most recent version/data available
(@ http://howdy.physics.nyu.edu/index.php/Kcorrect).

I just got a permission from Michael to distribute the package
(conditions of use being to cite his tool paper), and was going to
make it available somewhere (likely github) and announce it here.
That handy IDL tool now available on Python, only that you pay $19.99
USD to me upon each instantiation of KCorrect object!   (...just
kidding)

But I actually wondered if this sort of thing can be considered for
inclusion in astropy.

I had no intention of forking Michael's work, just wrote a
SWIG-extension for the core library and translated just a few of the
most useful IDL routines in (hopefully) Pythonic ways.  For inclusion
into astropy, however, I presume that there are some styles,
interfaces and such to follow, which I'm willing to make changes now
but wish to make sure it is going to be worth it, not to mention an
additional permission from the original library writer would be
necessary.

So my question is, will an independently developed tool like kcorrect
be considered at all for an astropy module eventually?  If so, how
should I go about this?

Thank you for your time.


-- 
Taro Sato
Department of Astronomy & Physics
Saint Mary's University? ? ? ? ? ?? email: taro at ap.smu.ca
Halifax, NS B3H 3C3? ? ? ? ? ? ? ?? phone: (902)420-5018
Canada? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? web: http://ap.smu.ca/~taro


From erik.tollerud at gmail.com  Sat Jan  7 19:24:50 2012
From: erik.tollerud at gmail.com (Erik Tollerud)
Date: Sat, 7 Jan 2012 16:24:50 -0800
Subject: [AstroPy] Including kcorrect as a astropy affiliated package?
In-Reply-To: <CA+ABecxZr4bE_aou8A3wHDKrWx2QdHeFXX_PyQXZVKYz76WG-w@mail.gmail.com>
References: <CA+ABecxZr4bE_aou8A3wHDKrWx2QdHeFXX_PyQXZVKYz76WG-w@mail.gmail.com>
Message-ID: <CAARXUwV+w5Ujn335A6wVn9n4knhGCAo1XSCQfd6bzdUH3F-9QA@mail.gmail.com>

This sounds like a perfect candidate for an affiliated package - we
probably wouldn't want it in the core right away because it's a
somewhat specific tool (and we would want it to interact more tightly
with some of the in-the-work astropy packages), but I could easily see
it getting merged down the road.

I know the documentation is a bit confusing about what affiliated
packages are - that will be updated as soon as we've gotten all the
automatic documentation tools working... but in a nutshell affiliated
packages are wholly external packages (although we encourage you to
host them in the astropy github organization, if you're willing), but
there will be a registry of affiliated packages and a tool to easily
install them once astropy is installed.  They're also a good way to
get something eventually included in the astropy core that isn't quite
"done cooking" yet.

And just so I understand, the package you've written does nothing with
the IDL layer of kcorrect, right?  It interfaces directly with the
C-level kcorrect? (I ask because I wrote a function
astropysics.phot.kcorrect that just wraps the IDL functionality using
pidly, but that requires that IDL already be installed, so this would
be much better)

On Sat, Jan 7, 2012 at 2:59 PM, Taro Sato <taro at ap.smu.ca> wrote:
> Hi there. ?I have not been diligently following the astropy discussion
> lately, so I may sound totally ignorant but please bear with me.
>
> I've written a Python wrapper for kcorrect by Michael Blanton, a
> popular IDL/C tool for k-correction, photo-z, and all that cool stuff
> people love to do with spectral-energy distribution fitting for high-z
> galaxies these days. ?I needed it for research recently and updated
> the Python version to work with the most recent version/data available
> (@ http://howdy.physics.nyu.edu/index.php/Kcorrect).
>
> I just got a permission from Michael to distribute the package
> (conditions of use being to cite his tool paper), and was going to
> make it available somewhere (likely github) and announce it here.
> That handy IDL tool now available on Python, only that you pay $19.99
> USD to me upon each instantiation of KCorrect object! ? (...just
> kidding)
>
> But I actually wondered if this sort of thing can be considered for
> inclusion in astropy.
>
> I had no intention of forking Michael's work, just wrote a
> SWIG-extension for the core library and translated just a few of the
> most useful IDL routines in (hopefully) Pythonic ways. ?For inclusion
> into astropy, however, I presume that there are some styles,
> interfaces and such to follow, which I'm willing to make changes now
> but wish to make sure it is going to be worth it, not to mention an
> additional permission from the original library writer would be
> necessary.
>
> So my question is, will an independently developed tool like kcorrect
> be considered at all for an astropy module eventually? ?If so, how
> should I go about this?
>
> Thank you for your time.
>
>
> --
> Taro Sato
> Department of Astronomy & Physics
> Saint Mary's University? ? ? ? ? ?? email: taro at ap.smu.ca
> Halifax, NS B3H 3C3? ? ? ? ? ? ? ?? phone: (902)420-5018
> Canada? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? web: http://ap.smu.ca/~taro
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy



-- 
Erik Tollerud


From taro at ap.smu.ca  Sat Jan  7 19:47:27 2012
From: taro at ap.smu.ca (Taro Sato)
Date: Sat, 7 Jan 2012 20:47:27 -0400
Subject: [AstroPy] Including kcorrect as a astropy affiliated package?
In-Reply-To: <CAARXUwV+w5Ujn335A6wVn9n4knhGCAo1XSCQfd6bzdUH3F-9QA@mail.gmail.com>
References: <CA+ABecxZr4bE_aou8A3wHDKrWx2QdHeFXX_PyQXZVKYz76WG-w@mail.gmail.com>
	<CAARXUwV+w5Ujn335A6wVn9n4knhGCAo1XSCQfd6bzdUH3F-9QA@mail.gmail.com>
Message-ID: <CA+ABecyHLXME14TKyBa0iq6XhbGXWyDOkKeGQwuTPtQDMb9qoQ@mail.gmail.com>

On Sat, Jan 7, 2012 at 8:24 PM, Erik Tollerud <erik.tollerud at gmail.com> wrote:
> This sounds like a perfect candidate for an affiliated package - we
> probably wouldn't want it in the core right away because it's a
> somewhat specific tool (and we would want it to interact more tightly
> with some of the in-the-work astropy packages), but I could easily see
> it getting merged down the road.
>
> I know the documentation is a bit confusing about what affiliated
> packages are - that will be updated as soon as we've gotten all the
> automatic documentation tools working... but in a nutshell affiliated
> packages are wholly external packages (although we encourage you to
> host them in the astropy github organization, if you're willing), but
> there will be a registry of affiliated packages and a tool to easily
> install them once astropy is installed. ?They're also a good way to
> get something eventually included in the astropy core that isn't quite
> "done cooking" yet.
>
> And just so I understand, the package you've written does nothing with
> the IDL layer of kcorrect, right? ?It interfaces directly with the
> C-level kcorrect? (I ask because I wrote a function
> astropysics.phot.kcorrect that just wraps the IDL functionality using
> pidly, but that requires that IDL already be installed, so this would
> be much better)



Oh, you've written a wrapper already...  how come I didn't know that!

Right, IDL isn't necessary at all to run the Python version, and
that's the reason for working on the port.  The original kcorrect
isn't a very thin wrapper around its C library, so in order to have
the full functionality that the IDL version currently has, all the
.pro scripts still need to be translated (I've only done what I have
needed for myself so far).  But that isn't so bad. (it's just that IDL
codes are not very fun to read.............)

I browsed through the astropy website and the affiliate thing, hence
my inquiry.  So I'd happy to contribute the whole thing, according to
whatever suggestion that astropy community makes.  I'm looking for a
repository anyways.... it's about 185 MB right now, most auxiliary
data included.

One thing I'd like to make sure, since a lot of effort must have been
put into collecting all the auxiliary data (like throughput curves,
templates, etc.) by Michael and his colleagues, is that if we end up
distributing those things along with the Python package, there needs
to be a way to ensure that the credit for the library goes to him
(which according to the kcorrect website is to cite Blanton et al.
2007 paper).

So before going ahead with the transition, I'd like to make sure that
sort of thing can be worked out well with everyone affected.

Cheers,
Taro


From adrianmpw at gmail.com  Sat Jan  7 19:59:53 2012
From: adrianmpw at gmail.com (Adrian Price-Whelan)
Date: Sat, 7 Jan 2012 19:59:53 -0500
Subject: [AstroPy] Including kcorrect as a astropy affiliated package?
In-Reply-To: <CA+ABecyHLXME14TKyBa0iq6XhbGXWyDOkKeGQwuTPtQDMb9qoQ@mail.gmail.com>
References: <CA+ABecxZr4bE_aou8A3wHDKrWx2QdHeFXX_PyQXZVKYz76WG-w@mail.gmail.com>
	<CAARXUwV+w5Ujn335A6wVn9n4knhGCAo1XSCQfd6bzdUH3F-9QA@mail.gmail.com>
	<CA+ABecyHLXME14TKyBa0iq6XhbGXWyDOkKeGQwuTPtQDMb9qoQ@mail.gmail.com>
Message-ID: <2214AAA5-9BF8-4273-A3C1-4FFCACD54B61@gmail.com>

Taro --

We should just email Mike and ask what level of credit he would expect (e.g. a line 
in the README, or some recognition on the github page?). But I certainly agree that
this is a great idea for an affiliated package!

- apw

On Jan 7, 2012, at 7:47 PM, Taro Sato wrote:

> On Sat, Jan 7, 2012 at 8:24 PM, Erik Tollerud <erik.tollerud at gmail.com> wrote:
>> This sounds like a perfect candidate for an affiliated package - we
>> probably wouldn't want it in the core right away because it's a
>> somewhat specific tool (and we would want it to interact more tightly
>> with some of the in-the-work astropy packages), but I could easily see
>> it getting merged down the road.
>> 
>> I know the documentation is a bit confusing about what affiliated
>> packages are - that will be updated as soon as we've gotten all the
>> automatic documentation tools working... but in a nutshell affiliated
>> packages are wholly external packages (although we encourage you to
>> host them in the astropy github organization, if you're willing), but
>> there will be a registry of affiliated packages and a tool to easily
>> install them once astropy is installed.  They're also a good way to
>> get something eventually included in the astropy core that isn't quite
>> "done cooking" yet.
>> 
>> And just so I understand, the package you've written does nothing with
>> the IDL layer of kcorrect, right?  It interfaces directly with the
>> C-level kcorrect? (I ask because I wrote a function
>> astropysics.phot.kcorrect that just wraps the IDL functionality using
>> pidly, but that requires that IDL already be installed, so this would
>> be much better)
> 
> 
> 
> Oh, you've written a wrapper already...  how come I didn't know that!
> 
> Right, IDL isn't necessary at all to run the Python version, and
> that's the reason for working on the port.  The original kcorrect
> isn't a very thin wrapper around its C library, so in order to have
> the full functionality that the IDL version currently has, all the
> .pro scripts still need to be translated (I've only done what I have
> needed for myself so far).  But that isn't so bad. (it's just that IDL
> codes are not very fun to read.............)
> 
> I browsed through the astropy website and the affiliate thing, hence
> my inquiry.  So I'd happy to contribute the whole thing, according to
> whatever suggestion that astropy community makes.  I'm looking for a
> repository anyways.... it's about 185 MB right now, most auxiliary
> data included.
> 
> One thing I'd like to make sure, since a lot of effort must have been
> put into collecting all the auxiliary data (like throughput curves,
> templates, etc.) by Michael and his colleagues, is that if we end up
> distributing those things along with the Python package, there needs
> to be a way to ensure that the credit for the library goes to him
> (which according to the kcorrect website is to cite Blanton et al.
> 2007 paper).
> 
> So before going ahead with the transition, I'd like to make sure that
> sort of thing can be worked out well with everyone affected.
> 
> Cheers,
> Taro
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy

--
Adrian Price-Whelan
Department of Astronomy
Columbia University
http://www.adrianpricewhelan.com




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

From erik.tollerud at gmail.com  Mon Jan  9 09:22:48 2012
From: erik.tollerud at gmail.com (Erik Tollerud)
Date: Mon, 9 Jan 2012 08:22:48 -0600
Subject: [AstroPy] Astropy at AAS?
In-Reply-To: <CAARXUwUwGJQDdtFjuNp_5v2s5Zq5q2nRM-nZHzn=hW+e2oVJOQ@mail.gmail.com>
References: <CAARXUwUwGJQDdtFjuNp_5v2s5Zq5q2nRM-nZHzn=hW+e2oVJOQ@mail.gmail.com>
Message-ID: <CAARXUwWw=-BsX0sSQ_16+y_t29+=pqE4AV1VmdaTk8NBaL9yEA@mail.gmail.com>

If anyone else is interested, we are planning on meeting at the SALT
booth (#135) in the exhibit hall at 12:30pm on *Wednesday* for a lunch
meeting.

On Wed, Jan 4, 2012 at 3:22 PM, Erik Tollerud <erik.tollerud at gmail.com> wrote:
> Hello all,
>
> We ended up not scheduling anything official for this AAS, but I'm
> curious if there's anyone who would like to meet to ask
> questions/comments about Astropy at next week's AAS meeting? ?If
> there's enough interest we could try to have an informal meeting over
> a lunch or something.
>
> --
> Erik Tollerud



-- 
Erik Tollerud


From gz323 at pha.jhu.edu  Mon Jan  9 15:41:49 2012
From: gz323 at pha.jhu.edu (Guangtun Ben Zhu)
Date: Mon, 9 Jan 2012 15:41:49 -0500
Subject: [AstroPy] Including kcorrect as a astropy affiliated package?
In-Reply-To: <CA+ABecxZr4bE_aou8A3wHDKrWx2QdHeFXX_PyQXZVKYz76WG-w@mail.gmail.com>
References: <CA+ABecxZr4bE_aou8A3wHDKrWx2QdHeFXX_PyQXZVKYz76WG-w@mail.gmail.com>
Message-ID: <CAMQmD5BjBi_46bA4wF_nAZTQX0z4MPck3FNkp2F8E8xpW+Kkcg@mail.gmail.com>

Dear all,

Just want to say this is a terrific idea
and it will be of great value to people who
are stuck in IDL, like me :-)

Thank you
Guangtun

On Sat, Jan 7, 2012 at 5:59 PM, Taro Sato <taro at ap.smu.ca> wrote:

> Hi there.  I have not been diligently following the astropy discussion
> lately, so I may sound totally ignorant but please bear with me.
>
> I've written a Python wrapper for kcorrect by Michael Blanton, a
> popular IDL/C tool for k-correction, photo-z, and all that cool stuff
> people love to do with spectral-energy distribution fitting for high-z
> galaxies these days.  I needed it for research recently and updated
> the Python version to work with the most recent version/data available
> (@ http://howdy.physics.nyu.edu/index.php/Kcorrect).
>
> I just got a permission from Michael to distribute the package
> (conditions of use being to cite his tool paper), and was going to
> make it available somewhere (likely github) and announce it here.
> That handy IDL tool now available on Python, only that you pay $19.99
> USD to me upon each instantiation of KCorrect object!   (...just
> kidding)
>
> But I actually wondered if this sort of thing can be considered for
> inclusion in astropy.
>
> I had no intention of forking Michael's work, just wrote a
> SWIG-extension for the core library and translated just a few of the
> most useful IDL routines in (hopefully) Pythonic ways.  For inclusion
> into astropy, however, I presume that there are some styles,
> interfaces and such to follow, which I'm willing to make changes now
> but wish to make sure it is going to be worth it, not to mention an
> additional permission from the original library writer would be
> necessary.
>
> So my question is, will an independently developed tool like kcorrect
> be considered at all for an astropy module eventually?  If so, how
> should I go about this?
>
> Thank you for your time.
>
>
> --
> Taro Sato
> Department of Astronomy & Physics
> Saint Mary's University             email: taro at ap.smu.ca
> Halifax, NS B3H 3C3                 phone: (902)420-5018
> Canada                                web: http://ap.smu.ca/~taro
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>



-- 
Guangtun Benjamin Zhu, PhD
Postdoc Fellow, Physics and Astronomy Department
Johns Hopkins University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20120109/c24d8e29/attachment.html>

From sontag at stsci.edu  Mon Jan  9 16:07:23 2012
From: sontag at stsci.edu (Chris Sontag)
Date: Mon, 9 Jan 2012 16:07:23 -0500
Subject: [AstroPy] photometry in pyraf
In-Reply-To: <CAJ_T+b4Qz=cuAq07-iNZY30TyL_WS64UWHr=4tK7icXr28bAYQ@mail.gmail.com>
References: <CAJ_T+b6cpaD9Va9O6GP_C2ViNt=Yw+F3kuSnHFLpGEu7Q5HzBg@mail.gmail.com>
	<CAJ_T+b4Qz=cuAq07-iNZY30TyL_WS64UWHr=4tK7icXr28bAYQ@mail.gmail.com>
Message-ID: <4F0B570B.20808@stsci.edu>

Hi Joe,

If Taro's suggestion isn't working for you, let me know off list.  There are a few different options to get this to work the way you need.

And if there is a bug (or "unexpected feature"), we'd like to fix it.

Finally, I believe we can get EPAR to do what you want, but to answer your question about a non-GUI version, yes, you can try "tpar" in PyRAF, for a terminal version (it requires the "urwid" package).

Chris

On 1/7/12 2:23 AM, Joe Philip Ninan wrote:
> Hi,
> I have been recently rewriting to pyraf all my photometry iraf scripts.
> For using the daofind and then phot task in noan.digiphot.daophot we
> first have to set the parameter files.
> Following is that section from my code.
> #--------------------(all the variables fwhm psfradi sigma datamin
> aperture etc. have been defined before in code)---------
>      iraf.daopar(matchra=fwhm, psfrad=psfradi, fitrad=fwhm)
>      iraf.datapar(fwhmpsf=fwhm, sigma=sigma, datamin=datamin,
> datamax=65000 , readnoi=4.8 , epadu=1.22 ,itime=intime,
> ifilter=filterr)
>      iraf.fitskypar(annulus=270, dannulu=12 )
>      iraf.photpar(apertur=aperture)
>      iraf.daofind(image=img)
>      #Going forward to do phot
>      iraf.phot(image=img)
> #----------------------------------------------------
> Now , when I run this code. It does displays the epar daopar, datapar
> etc in the GUI epar window of the pyraf with all correct values set.
> But when I press "Save&  Quit" button and reaches the daofind or phot
> task. It is executing without all the seted parameters.
> It looks like inspite of me clicking on "Save&  Quit" button. It is
> not getting saved. and the phot and daofind task are using some
> default setting in my uparm/
> In iraf, I had the same problem if i gave :wq in epar. But if I gave
> :w and then :q separately it used to work.
> There is no :w equivalent button in pyraf's GUI epar window.
>
> Can somebody point out some workaround for this problem? Is it
> possible in pyraf to get the non GUI epar window of iraf?
> Thanking you
> Joe
>
> --
> /---------------------------------------------------------------
> "GNU/Linux: because a PC is a terrible thing to waste" -  GNU Generation
> _______________________________________________
> 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/20120109/309f922a/attachment.html>

From erik.tollerud at gmail.com  Mon Jan  9 19:53:43 2012
From: erik.tollerud at gmail.com (Erik Tollerud)
Date: Mon, 9 Jan 2012 18:53:43 -0600
Subject: [AstroPy] Astropy at AAS?
In-Reply-To: <CAARXUwWw=-BsX0sSQ_16+y_t29+=pqE4AV1VmdaTk8NBaL9yEA@mail.gmail.com>
References: <CAARXUwUwGJQDdtFjuNp_5v2s5Zq5q2nRM-nZHzn=hW+e2oVJOQ@mail.gmail.com>
	<CAARXUwWw=-BsX0sSQ_16+y_t29+=pqE4AV1VmdaTk8NBaL9yEA@mail.gmail.com>
Message-ID: <CAARXUwVXOLgGO_fkCrGqR8BecqgwTS55Z0FUReV4gRXF8n8dTw@mail.gmail.com>

Correction: The SALT booth is #137 (there is no 135), and we've moved
to noon so as to try to avoid conflict with the NASA/NOAO town halls.

On Mon, Jan 9, 2012 at 8:22 AM, Erik Tollerud <erik.tollerud at gmail.com> wrote:
> If anyone else is interested, we are planning on meeting at the SALT
> booth (#135) in the exhibit hall at 12:30pm on *Wednesday* for a lunch
> meeting.
>
> On Wed, Jan 4, 2012 at 3:22 PM, Erik Tollerud <erik.tollerud at gmail.com> wrote:
>> Hello all,
>>
>> We ended up not scheduling anything official for this AAS, but I'm
>> curious if there's anyone who would like to meet to ask
>> questions/comments about Astropy at next week's AAS meeting? ?If
>> there's enough interest we could try to have an informal meeting over
>> a lunch or something.
>>
>> --
>> Erik Tollerud
>
>
>
> --
> Erik Tollerud



-- 
Erik Tollerud


From indiajoe at gmail.com  Tue Jan 10 01:56:38 2012
From: indiajoe at gmail.com (Joe Philip Ninan)
Date: Tue, 10 Jan 2012 12:26:38 +0530
Subject: [AstroPy] photometry in pyraf
In-Reply-To: <CA+ABecwjd8NQKd+89TtBJF7J_nMHLpA2uHrsk4+xrin+h6JH8w@mail.gmail.com>
References: <CAJ_T+b6cpaD9Va9O6GP_C2ViNt=Yw+F3kuSnHFLpGEu7Q5HzBg@mail.gmail.com>
	<CAJ_T+b4Qz=cuAq07-iNZY30TyL_WS64UWHr=4tK7icXr28bAYQ@mail.gmail.com>
	<CA+ABecwjd8NQKd+89TtBJF7J_nMHLpA2uHrsk4+xrin+h6JH8w@mail.gmail.com>
Message-ID: <CAJ_T+b5-XYaycdYeuBbgDnutG3tfskocy8mMitS8ig93Tw+fqA@mail.gmail.com>

Hi Sato,
I apologize for this long delay in replying to your help. (got stuck in
some technical issues)
Thanks a lot for your suggestion. My scripts are working by the setPar
tasks you suggested.
Loading defaults and then changing the required parameters was a good
suggestion to make script more robust.
Thanking you,
Joe


On 7 January 2012 21:09, Taro Sato <taro at ap.smu.ca> wrote:

> On Sat, Jan 7, 2012 at 3:23 AM, Joe Philip Ninan <indiajoe at gmail.com>
> wrote:
> > Hi,
> > I have been recently rewriting to pyraf all my photometry iraf scripts.
> > For using the daofind and then phot task in noan.digiphot.daophot we
> > first have to set the parameter files.
> > Following is that section from my code.
> > #--------------------(all the variables fwhm psfradi sigma datamin
> > aperture etc. have been defined before in code)---------
> >     iraf.daopar(matchra=fwhm, psfrad=psfradi, fitrad=fwhm)
> >     iraf.datapar(fwhmpsf=fwhm, sigma=sigma, datamin=datamin,
> > datamax=65000 , readnoi=4.8 , epadu=1.22 ,itime=intime,
> > ifilter=filterr)
> >     iraf.fitskypar(annulus=270, dannulu=12 )
> >     iraf.photpar(apertur=aperture)
> >     iraf.daofind(image=img)
> >     #Going forward to do phot
> >     iraf.phot(image=img)
> > #----------------------------------------------------
> > Now , when I run this code. It does displays the epar daopar, datapar
> > etc in the GUI epar window of the pyraf with all correct values set.
> > But when I press "Save & Quit" button and reaches the daofind or phot
> > task. It is executing without all the seted parameters.
> > It looks like inspite of me clicking on "Save & Quit" button. It is
> > not getting saved. and the phot and daofind task are using some
> > default setting in my uparm/
> > In iraf, I had the same problem if i gave :wq in epar. But if I gave
> > :w and then :q separately it used to work.
> > There is no :w equivalent button in pyraf's GUI epar window.
> >
> > Can somebody point out some workaround for this problem? Is it
> > possible in pyraf to get the non GUI epar window of iraf?
> > Thanking you
> > Joe
> >
> > --
> > /---------------------------------------------------------------
> > "GNU/Linux: because a PC is a terrible thing to waste" -  GNU Generation
> > _______________________________________________
> > AstroPy mailing list
> > AstroPy at scipy.org
> > http://mail.scipy.org/mailman/listinfo/astropy
>
>
> Not sure if this is the type of thing you wish to do, but since I
> don't trust (or remember) the exact behavior of which set of
> parameters gets actually used, my approach is to reset all parameters
> to default and override those I need to change.  The following is my
> template for using an IRAF task with PyRAF.  This won't prompt you to
> edit parameters on GUI though, if that's what you need to do...
>
> Hope this helps a tiny bit.
>
>
>
> ####### BEGIN ##########
>
> #!/usr/bin/env python
> from pyraf import iraf
> from pyraf.irafpar import IrafParList
>
> def default_irafpar(task):
>   # Return the IrafParList object for default parameters.
>   return IrafParList(task.getName(), parlist=task.getDefaultParList())
>
> def main():
>   # Load IRAF packages.
>   iraf.gemini(_doprint=0)
>   iraf.gmos(_doprint=0)
>
>   # Get default parameters and override some.
>   yes, no = 'yes', 'no'
>   plist = default_irafpar(iraf.gprepare)
>   plist.setParList(inimages = 'someimage.fits',
>                    rawpath = '/astro/data/',
>                    fl_addmdf = yes,
>                    mdfdir = '../mdf/',
>                    logfile = '',
>                    verbose = yes)
>
>   # Run the task.
>   iraf.gsprepare(ParList=plist)
>
>   return
>
> if __name__ == '__main__':
>   main()
>
> ######### END ###############
>
>
>
>
> --
> Taro Sato
> Department of Astronomy & Physics
> Saint Mary's University             email: taro at ap.smu.ca
> Halifax, NS B3H 3C3                 phone: (902)420-5018
> Canada                                web: http://ap.smu.ca/~taro
>



-- 
/---------------------------------------------------------------
"GNU/Linux: because a PC is a terrible thing to waste" -  GNU Generation

************************************************
Joe Philip Ninan    http://sites.google.com/site/jpninan/
Research Scholar        /________________\
DAA,                            | Vadakeparambil |
TIFR,                           | Pullad P.O.         |
Mumbai-05, India.      | Kerala, India      |
Ph: +917738438212   | PIN:689548       |
------------------------------\_______________/--------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20120110/fc507a20/attachment.html>

From indiajoe at gmail.com  Tue Jan 10 01:59:05 2012
From: indiajoe at gmail.com (Joe Philip Ninan)
Date: Tue, 10 Jan 2012 12:29:05 +0530
Subject: [AstroPy] photometry in pyraf
In-Reply-To: <4F0B570B.20808@stsci.edu>
References: <CAJ_T+b6cpaD9Va9O6GP_C2ViNt=Yw+F3kuSnHFLpGEu7Q5HzBg@mail.gmail.com>
	<CAJ_T+b4Qz=cuAq07-iNZY30TyL_WS64UWHr=4tK7icXr28bAYQ@mail.gmail.com>
	<4F0B570B.20808@stsci.edu>
Message-ID: <CAJ_T+b6sTGvt2ijrfkKKS8hEfYfiJCpuy1LjNqko=B1Vjoa2hg@mail.gmail.com>

Hi Chris,
Taro's suggestion worked for me.
I anyway required a terminal version of epar. So tpar will be quite useful
for me.
Thanks a lot.
Joe

On 10 January 2012 02:37, Chris Sontag <sontag at stsci.edu> wrote:

>  Hi Joe,
>
> If Taro's suggestion isn't working for you, let me know off list.  There
> are a few different options to get this to work the way you need.
>
> And if there is a bug (or "unexpected feature"), we'd like to fix it.
>
> Finally, I believe we can get EPAR to do what you want, but to answer your
> question about a non-GUI version, yes, you can try "tpar" in PyRAF, for a
> terminal version (it requires the "urwid" package).
>
> Chris
>
>
> On 1/7/12 2:23 AM, Joe Philip Ninan wrote:
>
> Hi,
> I have been recently rewriting to pyraf all my photometry iraf scripts.
> For using the daofind and then phot task in noan.digiphot.daophot we
> first have to set the parameter files.
> Following is that section from my code.
> #--------------------(all the variables fwhm psfradi sigma datamin
> aperture etc. have been defined before in code)---------
>     iraf.daopar(matchra=fwhm, psfrad=psfradi, fitrad=fwhm)
>     iraf.datapar(fwhmpsf=fwhm, sigma=sigma, datamin=datamin,
> datamax=65000 , readnoi=4.8 , epadu=1.22 ,itime=intime,
> ifilter=filterr)
>     iraf.fitskypar(annulus=270, dannulu=12 )
>     iraf.photpar(apertur=aperture)
>     iraf.daofind(image=img)
>     #Going forward to do phot
>     iraf.phot(image=img)
> #----------------------------------------------------
> Now , when I run this code. It does displays the epar daopar, datapar
> etc in the GUI epar window of the pyraf with all correct values set.
> But when I press "Save & Quit" button and reaches the daofind or phot
> task. It is executing without all the seted parameters.
> It looks like inspite of me clicking on "Save & Quit" button. It is
> not getting saved. and the phot and daofind task are using some
> default setting in my uparm/
> In iraf, I had the same problem if i gave :wq in epar. But if I gave
> :w and then :q separately it used to work.
> There is no :w equivalent button in pyraf's GUI epar window.
>
> Can somebody point out some workaround for this problem? Is it
> possible in pyraf to get the non GUI epar window of iraf?
> Thanking you
> Joe
>
> --
> /-----------------------------------------------------------
> ----
> "GNU/Linux: because a PC is a terrible thing to waste" -  GNU Generation
> _______________________________________________
> AstroPy mailing listAstroPy at scipy.orghttp://mail.scipy.org/mailman/listinfo/astropy
>
>


-- 
/---------------------------------------------------------------
"GNU/Linux: because a PC is a terrible thing to waste" -  GNU Generation

************************************************
Joe Philip Ninan    http://sites.google.com/site/jpninan/
Research Scholar        /________________\
DAA,                            | Vadakeparambil |
TIFR,                           | Pullad P.O.         |
Mumbai-05, India.      | Kerala, India      |
Ph: +917738438212   | PIN:689548       |
------------------------------\_______________/--------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20120110/0aba46b0/attachment.html>

From indiajoe at gmail.com  Tue Jan 10 10:40:28 2012
From: indiajoe at gmail.com (Joe Philip Ninan)
Date: Tue, 10 Jan 2012 21:10:28 +0530
Subject: [AstroPy] photometry in pyraf
In-Reply-To: <CAJ_T+b6sTGvt2ijrfkKKS8hEfYfiJCpuy1LjNqko=B1Vjoa2hg@mail.gmail.com>
References: <CAJ_T+b6cpaD9Va9O6GP_C2ViNt=Yw+F3kuSnHFLpGEu7Q5HzBg@mail.gmail.com>
	<CAJ_T+b4Qz=cuAq07-iNZY30TyL_WS64UWHr=4tK7icXr28bAYQ@mail.gmail.com>
	<4F0B570B.20808@stsci.edu>
	<CAJ_T+b6sTGvt2ijrfkKKS8hEfYfiJCpuy1LjNqko=B1Vjoa2hg@mail.gmail.com>
Message-ID: <CAJ_T+b4xWjYiev6MOu_tYCpSJ7q5kwQ7ZRSURjoor+DKFYzVPw@mail.gmail.com>

Hi Chris,
I am facing a weird problem with tpar
I have installed urwid-1.0.1
When I run tpar for first time in pyraf interface. it works properly.
After that when I open tpar again and presses q after :, I get two qq 'es
i.e.    :qq
Pressing enter after that exists tpar. But the terminal will not show
anything i type after that.
Inspite of that, if I type any command blindly and press enter, it does
execute it.
For example if i type .exit , it does exit from pyraf and terminal shows my
bash prompt.
But still nothing shows up when i type any command in terminal. (yet it
executes everything if i press enter!!)
Interesting part is this problem persists (till I close the terminal), even
after exiting from pyraf.

I don't know whether this is related, but I shall point out that I am also
getting a Deprecation Warning when I call the tpar first time.
------------
*/usr/lib/python2.6/site-packages/urwid-1.0.1-py2.6-linux-i686.egg/urwid/listbox.py:54:
DeprecationWarning: PollingListWalker is deprecated, use SimpleListWalker
instead.
  "use SimpleListWalker instead.", DeprecationWarning)
*-------------------------

Thanking you,
Joe


On 10 January 2012 12:29, Joe Philip Ninan <indiajoe at gmail.com> wrote:

> Hi Chris,
> Taro's suggestion worked for me.
> I anyway required a terminal version of epar. So tpar will be quite useful
> for me.
> Thanks a lot.
> Joe
>
>
> On 10 January 2012 02:37, Chris Sontag <sontag at stsci.edu> wrote:
>
>>  Hi Joe,
>>
>> If Taro's suggestion isn't working for you, let me know off list.  There
>> are a few different options to get this to work the way you need.
>>
>> And if there is a bug (or "unexpected feature"), we'd like to fix it.
>>
>> Finally, I believe we can get EPAR to do what you want, but to answer
>> your question about a non-GUI version, yes, you can try "tpar" in PyRAF,
>> for a terminal version (it requires the "urwid" package).
>>
>> Chris
>>
>>
>> On 1/7/12 2:23 AM, Joe Philip Ninan wrote:
>>
>> Hi,
>> I have been recently rewriting to pyraf all my photometry iraf scripts.
>> For using the daofind and then phot task in noan.digiphot.daophot we
>> first have to set the parameter files.
>> Following is that section from my code.
>> #--------------------(all the variables fwhm psfradi sigma datamin
>> aperture etc. have been defined before in code)---------
>>     iraf.daopar(matchra=fwhm, psfrad=psfradi, fitrad=fwhm)
>>     iraf.datapar(fwhmpsf=fwhm, sigma=sigma, datamin=datamin,
>> datamax=65000 , readnoi=4.8 , epadu=1.22 ,itime=intime,
>> ifilter=filterr)
>>     iraf.fitskypar(annulus=270, dannulu=12 )
>>     iraf.photpar(apertur=aperture)
>>     iraf.daofind(image=img)
>>     #Going forward to do phot
>>     iraf.phot(image=img)
>> #----------------------------------------------------
>> Now , when I run this code. It does displays the epar daopar, datapar
>> etc in the GUI epar window of the pyraf with all correct values set.
>> But when I press "Save & Quit" button and reaches the daofind or phot
>> task. It is executing without all the seted parameters.
>> It looks like inspite of me clicking on "Save & Quit" button. It is
>> not getting saved. and the phot and daofind task are using some
>> default setting in my uparm/
>> In iraf, I had the same problem if i gave :wq in epar. But if I gave
>> :w and then :q separately it used to work.
>> There is no :w equivalent button in pyraf's GUI epar window.
>>
>> Can somebody point out some workaround for this problem? Is it
>> possible in pyraf to get the non GUI epar window of iraf?
>> Thanking you
>> Joe
>>
>> --
>> /-----------------------------------------------------------
>> ----
>> "GNU/Linux: because a PC is a terrible thing to waste" -  GNU Generation
>> _______________________________________________
>> AstroPy mailing listAstroPy at scipy.orghttp://mail.scipy.org/mailman/listinfo/astropy
>>
>>
>
>
> --
> /---------------------------------------------------------------
> "GNU/Linux: because a PC is a terrible thing to waste" -  GNU Generation
>
> ************************************************
> Joe Philip Ninan    http://sites.google.com/site/jpninan/
> Research Scholar        /________________\
> DAA,                            | Vadakeparambil |
> TIFR,                           | Pullad P.O.         |
> Mumbai-05, India.      | Kerala, India      |
> Ph: +917738438212   | PIN:689548       |
> ------------------------------\_______________/--------------
>
>


-- 
/---------------------------------------------------------------
"GNU/Linux: because a PC is a terrible thing to waste" -  GNU Generation

************************************************
Joe Philip Ninan    http://sites.google.com/site/jpninan/
Research Scholar        /________________\
DAA,                            | Vadakeparambil |
TIFR,                           | Pullad P.O.         |
Mumbai-05, India.      | Kerala, India      |
Ph: +917738438212   | PIN:689548       |
------------------------------\_______________/--------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20120110/45fc3ea9/attachment.html>

From miguel.deval at gmail.com  Tue Jan 10 10:41:58 2012
From: miguel.deval at gmail.com (Miguel de Val-Borro)
Date: Tue, 10 Jan 2012 16:41:58 +0100
Subject: [AstroPy] satellite-centered ephemeris
Message-ID: <20120110154158.GA15694@poincare.pc.linmpi.mpg.de>

Hello,

I would like to calculate RA and Dec of solar system objects at the
position of the Herschel satellite. This can be done in the on-line JPL
Horizons system setting the observer to @herschel, however I would like
to calculate the coordinates from the orbital elements of Herschel and
the object at different times. I have checked that pyEphem Observer
object supports positions on Earth's surface; is there any available
package where I can use the orbital elements of a satellite to define
the observer frame? 

Thanks,
Miguel


From miguel.deval at gmail.com  Thu Jan 12 10:44:53 2012
From: miguel.deval at gmail.com (Miguel de Val-Borro)
Date: Thu, 12 Jan 2012 16:44:53 +0100
Subject: [AstroPy] satellite-centered ephemeris
Message-ID: <20120112154453.GA29124@poincare.pc.linmpi.mpg.de>

Hi Jonathan,

I have looked at the SPICE tutorials on the ephemeris subsystem and it
looks that it does what I want. However I need the SPK kernel for the
Herschel satellite that I could not find in the NAIF server or at the
ESA SPICE webpage. Do you know if this kernel is publicly available
somewhere?

Regards,
Miguel

On Tue, Jan 10, 2012 at 09:37:17AM -0700, Jonathan T. Niehof wrote:
> On 01/10/2012 08:41 AM, Miguel de Val-Borro wrote:
> > Hello,
> >
> > I would like to calculate RA and Dec of solar system objects at the
> > position of the Herschel satellite. This can be done in the on-line JPL
> > Horizons system setting the observer to @herschel, however I would like
> > to calculate the coordinates from the orbital elements of Herschel and
> > the object at different times. I have checked that pyEphem Observer
> > object supports positions on Earth's surface; is there any available
> > package where I can use the orbital elements of a satellite to define
> > the observer frame?
> 
> Miguel--
> Are you familiar with JPL's NAIF/SPICE library? It's C-based and would 
> probably have something that would work for this. We've been (slowly) 
> wrapping it in Python here, but don't have distribution permission yet. 
> I can probably knock loose "share with collaborators" permission if you 
> find a function in there that seems useful.
> 
> -- 
> Jonathan Niehof
> ISR-3 Space Data Systems
> Los Alamos National Laboratory
> MS-D466
> Los Alamos, NM 87545
> 
> Phone: 505-667-9595
> email: jniehof at lanl.gov
> 
> Correspondence /
> Technical data or Software Publicly Available


From erik.tollerud at gmail.com  Fri Jan 13 21:14:09 2012
From: erik.tollerud at gmail.com (Erik Tollerud)
Date: Sat, 14 Jan 2012 02:14:09 +0000
Subject: [AstroPy] Including kcorrect as a astropy affiliated package?
In-Reply-To: <CA+ABecyHLXME14TKyBa0iq6XhbGXWyDOkKeGQwuTPtQDMb9qoQ@mail.gmail.com>
References: <CA+ABecxZr4bE_aou8A3wHDKrWx2QdHeFXX_PyQXZVKYz76WG-w@mail.gmail.com>
	<CAARXUwV+w5Ujn335A6wVn9n4knhGCAo1XSCQfd6bzdUH3F-9QA@mail.gmail.com>
	<CA+ABecyHLXME14TKyBa0iq6XhbGXWyDOkKeGQwuTPtQDMb9qoQ@mail.gmail.com>
Message-ID: <CAARXUwU=RdvR81-Ks-jceb3-a=Z7=LHQD+3MVDMJP6PGk7dCrw@mail.gmail.com>

(Sorry for the delay in responding - AAS was rather hectic...)

> Oh, you've written a wrapper already... ?how come I didn't know that!

Probably because I didn't try to advertise it too much given that it
calls IDL via python - that just feels wrong somehow :)


> Right, IDL isn't necessary at all to run the Python version, and
> that's the reason for working on the port. ?The original kcorrect
> isn't a very thin wrapper around its C library, so in order to have
> the full functionality that the IDL version currently has, all the
> .pro scripts still need to be translated (I've only done what I have
> needed for myself so far). ?But that isn't so bad. (it's just that IDL
> codes are not very fun to read.............)

It's not clear to me that we even want/need to translate many of the
IDL pieces (e.g. all the various survey-specific helper procedures) -
probably just a few functions that do the relatively standard things
is good enough for most purposes.  Eventually it'd be good to include
some an interface that accepts astropy photometry objects or
something.  But given the requisite astropy objects are not
implemented yet, that's probably a ways down the road.


> I browsed through the astropy website and the affiliate thing, hence
> my inquiry. ?So I'd happy to contribute the whole thing, according to
> whatever suggestion that astropy community makes. ?I'm looking for a
> repository anyways.... it's about 185 MB right now, most auxiliary
> data included.

This is a perfect candidate for the data framework (see the
astropy.config.data package and associated documentation) - you could
include just the code itself in a github repo, and the auxiliary data
can be downloaded directly via URL, and the data package then caches
the download for you and uses the local version on later accesses.
Once we have a data server up and running, I'm sure we could host the
auxiliary data there, as well.



-- 
Erik Tollerud


From taro at ap.smu.ca  Tue Jan 17 11:48:55 2012
From: taro at ap.smu.ca (Taro Sato)
Date: Tue, 17 Jan 2012 12:48:55 -0400
Subject: [AstroPy] Including kcorrect as a astropy affiliated package?
In-Reply-To: <CAARXUwU=RdvR81-Ks-jceb3-a=Z7=LHQD+3MVDMJP6PGk7dCrw@mail.gmail.com>
References: <CA+ABecxZr4bE_aou8A3wHDKrWx2QdHeFXX_PyQXZVKYz76WG-w@mail.gmail.com>
	<CAARXUwV+w5Ujn335A6wVn9n4knhGCAo1XSCQfd6bzdUH3F-9QA@mail.gmail.com>
	<CA+ABecyHLXME14TKyBa0iq6XhbGXWyDOkKeGQwuTPtQDMb9qoQ@mail.gmail.com>
	<CAARXUwU=RdvR81-Ks-jceb3-a=Z7=LHQD+3MVDMJP6PGk7dCrw@mail.gmail.com>
Message-ID: <CA+ABecwArxy7XQ1wjrknOeemiJdaQAbwS_hqeiddneMPSiooEA@mail.gmail.com>

Inline...


On Fri, Jan 13, 2012 at 10:14 PM, Erik Tollerud <erik.tollerud at gmail.com> wrote:
> (Sorry for the delay in responding - AAS was rather hectic...)

I'm sorry for the delay in response... something came up and got tied
up, and I wasn't even in the AAS meeting...


>> Right, IDL isn't necessary at all to run the Python version, and
>> that's the reason for working on the port.  The original kcorrect
>> isn't a very thin wrapper around its C library, so in order to have
>> the full functionality that the IDL version currently has, all the
>> .pro scripts still need to be translated (I've only done what I have
>> needed for myself so far).  But that isn't so bad. (it's just that IDL
>> codes are not very fun to read.............)
>
> It's not clear to me that we even want/need to translate many of the
> IDL pieces (e.g. all the various survey-specific helper procedures) -
> probably just a few functions that do the relatively standard things
> is good enough for most purposes.  Eventually it'd be good to include
> some an interface that accepts astropy photometry objects or
> something.  But given the requisite astropy objects are not
> implemented yet, that's probably a ways down the road.

No, we don't really need to translate the survey specific routines.
Mostly all they are doing is to define a filter set specific to the
survey, and convert whatever photometry it uses into AB maggies with
which all the internal computations are done.  I believe this two-step
process needs to be manually done (i.e., call a survey specific
converter routine, and then call a fitting routine, etc.).

One of my motivations for porting kcorrect, however, was that I wanted
to hide the conversion process (honestly, who want to learn another
obscure photometric system....).  I'm not sure if it should eventually
be done that way, but the way I'm implementing right now is to define
KCorrect (base) class, which does all the internal work in AB maggies,
which you subclass to override the photometry conversion method,
filter set property, etc., for a specific survey.

I'm not sure that particular design is solid (I'm not a software
engineer), but at least it allows me to do the same thing you can do
with the IDL version with much less typing.

In any case, how we go about those issues, we should just try to come
up with whatever that makes sense as a sub-package of the whole thing.
 At least the boring extension wrapping part has been done mostly...
(though I'm actually not sure including a SWIG interface is something
desired for distribution).


>> I browsed through the astropy website and the affiliate thing, hence
>> my inquiry.  So I'd happy to contribute the whole thing, according to
>> whatever suggestion that astropy community makes.  I'm looking for a
>> repository anyways.... it's about 185 MB right now, most auxiliary
>> data included.
>
> This is a perfect candidate for the data framework (see the
> astropy.config.data package and associated documentation) - you could
> include just the code itself in a github repo, and the auxiliary data
> can be downloaded directly via URL, and the data package then caches
> the download for you and uses the local version on later accesses.
> Once we have a data server up and running, I'm sure we could host the
> auxiliary data there, as well.


I'll respond to your message about this.

Cheers

Taro




--
Taro Sato
Department of Astronomy & Physics
Saint Mary's University             email: taro at ap.smu.ca
Halifax, NS B3H 3C3                 phone: (902)420-5018
Canada                                web: http://ap.smu.ca/~taro


From omar.vpa at gmail.com  Thu Jan 19 15:27:04 2012
From: omar.vpa at gmail.com (=?ISO-8859-1?Q?Omar_Trinidad_Guti=E9rrez_M=E9ndez?=)
Date: Thu, 19 Jan 2012 14:27:04 -0600
Subject: [AstroPy] About PyFITS
Message-ID: <CALjXLTVedmN_xd9efpgwar79MFxY9BjcabMoJZhb6sA+0=bvAw@mail.gmail.com>

Hello guys:

I am working with PyFITS, I translated the data section to RGB, then with
OpenCV I count the number of stars. Is there a field indicating the number
of stars? I would like check my results.

Greetings
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20120119/5104b0f8/attachment.html>

From sierra_mtnview at sbcglobal.net  Tue Jan 24 23:29:29 2012
From: sierra_mtnview at sbcglobal.net (Wayne Watson)
Date: Tue, 24 Jan 2012 20:29:29 -0800
Subject: [AstroPy] Back to Python. Precession and PhysConst code.
Message-ID: <4F1F8529.4010303@sbcglobal.net>

It's been quite awhile since I used python, but I was digging around on 
PC for something on precession, and discovered some code for it, 
prec.py.   Here are the first few lines.

#!/usr/bin/env python
"""
History:
P.T.Wallace   Starlink   10 July 1994
2002-07-08 ROwen    Converted to Python.
2007-04-24 ROwen    Converted from Numeric to numpy (in test code).
"""
import RO.PhysConst
from euler import *
...
...

It dies on RO.PhysConst when I run it.  Probably a further difficulty is 
the euler reference.
I have the code for RO.PhysConst.py

What needs to be done to successfully execute prec.py?

-- 
            Wayne Watson (Watson Adventures, Prop., Nevada City, CA)

              (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
               Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet

                      In 2904 there will be 5 solar eclipses.
                      On July 16, 2185 the longest solar
                      eclipse inf 5k years will occur, 7 min.

                     Web Page:<www.speckledwithstars.net/>




From sierra_mtnview at sbcglobal.net  Wed Jan 25 07:50:49 2012
From: sierra_mtnview at sbcglobal.net (Wayne Watson)
Date: Wed, 25 Jan 2012 04:50:49 -0800
Subject: [AstroPy] Back to Python. Precession and PhysConst code.
In-Reply-To: <4F1F8682.2010206@gmail.com>
References: <4F1F8529.4010303@sbcglobal.net> <4F1F8682.2010206@gmail.com>
Message-ID: <4F1FFAA9.8030201@sbcglobal.net>

Traceback (most recent call last):
   File 
"C:\Users\Wayne\Download_Programs\Python\astro-math_RO-2.3.0\RO-2.3.0\python\RO\Astro\llv\prec.py", 
line 8, in <module>
     import RO.PhysConst
ImportError: No module named RO.PhysConst

I tried removing the RO, but then couldn't save the file.

Python 2.7.2 (default, Jun 12 2011, 14:24:46) [MSC v.1500 64 bit 
(AMD64)] on win32

On 1/24/2012 8:35 PM, Alexander Wagner wrote:
> I am not familiar with any of the code, but just to make sure, does 
> your python path contain the path to the RO module?
>
> If you post the error message and backtrace others may be able to help 
> further.
>
> Best wishes,
> Alex
>
> On 25/01/12 1:29 PM, Wayne Watson wrote:
>> It's been quite awhile since I used python, but I was digging around on
>> PC for something on precession, and discovered some code for it,
>> prec.py.   Here are the first few lines.
>>
>> #!/usr/bin/env python
>> """
>> History:
>> P.T.Wallace   Starlink   10 July 1994
>> 2002-07-08 ROwen    Converted to Python.
>> 2007-04-24 ROwen    Converted from Numeric to numpy (in test code).
>> """
>> import RO.PhysConst
>> from euler import *
>> ...
>> ...
>>
>> It dies on RO.PhysConst when I run it.  Probably a further difficulty is
>> the euler reference.
>> I have the code for RO.PhysConst.py
>>
>> What needs to be done to successfully execute prec.py?
>>
>
>

-- 
            Wayne Watson (Watson Adventures, Prop., Nevada City, CA)

              (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
               Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet

                      In 2904 there will be 5 solar eclipses.
                      On July 16, 2185 the longest solar
                      eclipse inf 5k years will occur, 7 min.

                     Web Page:<www.speckledwithstars.net/>




From rowen at uw.edu  Wed Jan 25 12:34:18 2012
From: rowen at uw.edu (Russell Owen)
Date: Wed, 25 Jan 2012 09:34:18 -0800
Subject: [AstroPy] Back to Python. Precession and PhysConst code.
In-Reply-To: <4F1F8529.4010303@sbcglobal.net>
References: <4F1F8529.4010303@sbcglobal.net>
Message-ID: <E95B220B-5CF3-45DF-A298-769FF1D55B9B@uw.edu>

You have an incomplete package. Download RO from PyPI. The stuff you are looking for is in RO.Astro. euler is included in the package.

-- Russell

On Jan 24, 2012, at 8:29 PM, Wayne Watson wrote:

> It's been quite awhile since I used python, but I was digging around on 
> PC for something on precession, and discovered some code for it, 
> prec.py.   Here are the first few lines.
> 
> #!/usr/bin/env python
> """
> History:
> P.T.Wallace   Starlink   10 July 1994
> 2002-07-08 ROwen    Converted to Python.
> 2007-04-24 ROwen    Converted from Numeric to numpy (in test code).
> """
> import RO.PhysConst
> from euler import *
> ...
> ...
> 
> It dies on RO.PhysConst when I run it.  Probably a further difficulty is 
> the euler reference.
> I have the code for RO.PhysConst.py
> 
> What needs to be done to successfully execute prec.py?
> 
> -- 
>            Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
> 
>              (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>               Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
> 
>                      In 2904 there will be 5 solar eclipses.
>                      On July 16, 2185 the longest solar
>                      eclipse inf 5k years will occur, 7 min.
> 
>                     Web Page:<www.speckledwithstars.net/>
> 
> 
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy



From sierra_mtnview at sbcglobal.net  Wed Jan 25 14:45:38 2012
From: sierra_mtnview at sbcglobal.net (Wayne Watson)
Date: Wed, 25 Jan 2012 11:45:38 -0800
Subject: [AstroPy] Back to Python. Precession and PhysConst code.
In-Reply-To: <E95B220B-5CF3-45DF-A298-769FF1D55B9B@uw.edu>
References: <4F1F8529.4010303@sbcglobal.net>
	<E95B220B-5CF3-45DF-A298-769FF1D55B9B@uw.edu>
Message-ID: <4F205BE2.4090608@sbcglobal.net>

Thanks, but it looks like your PyPI is in a tar file. I'm using Win7.  
RO 2.9.3 is a download.  I see some refs to Win, but I'm not sure what 
to make of them.

On 1/25/2012 9:34 AM, Russell Owen wrote:
> You have an incomplete package. Download RO from PyPI. The stuff you are looking for is in RO.Astro. euler is included in the package.
>
> -- Russell
>
> On Jan 24, 2012, at 8:29 PM, Wayne Watson wrote:
>
>> It's been quite awhile since I used python, but I was digging around on
>> PC for something on precession, and discovered some code for it,
>> prec.py.   Here are the first few lines.
>>
>> #!/usr/bin/env python
>> """
>> History:
>> P.T.Wallace   Starlink   10 July 1994
>> 2002-07-08 ROwen    Converted to Python.
>> 2007-04-24 ROwen    Converted from Numeric to numpy (in test code).
>> """
>> import RO.PhysConst
>> from euler import *
>> ...
>> ...
>>
>> It dies on RO.PhysConst when I run it.  Probably a further difficulty is
>> the euler reference.
>> I have the code for RO.PhysConst.py
>>
>> What needs to be done to successfully execute prec.py?
>>
>> -- 
>>             Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>
>>               (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>>                Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
>>
>>                       In 2904 there will be 5 solar eclipses.
>>                       On July 16, 2185 the longest solar
>>                       eclipse inf 5k years will occur, 7 min.
>>
>>                      Web Page:<www.speckledwithstars.net/>
>>
>>
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
>

-- 
            Wayne Watson (Watson Adventures, Prop., Nevada City, CA)

              (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
               Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet

                      In 2904 there will be 5 solar eclipses.
                      On July 16, 2185 the longest solar
                      eclipse inf 5k years will occur, 7 min.

                     Web Page:<www.speckledwithstars.net/>




From rowen at uw.edu  Wed Jan 25 15:22:46 2012
From: rowen at uw.edu (Russell Owen)
Date: Wed, 25 Jan 2012 12:22:46 -0800
Subject: [AstroPy] Back to Python. Precession and PhysConst code.
In-Reply-To: <4F205BE2.4090608@sbcglobal.net>
References: <4F1F8529.4010303@sbcglobal.net>
	<E95B220B-5CF3-45DF-A298-769FF1D55B9B@uw.edu>
	<4F205BE2.4090608@sbcglobal.net>
Message-ID: <771C9C40-25EC-4567-992F-63B054304694@uw.edu>

Yes to all that. It is pure python. Install it using distutils as usual.

-- Russell

On Jan 25, 2012, at 11:45 AM, Wayne Watson wrote:

> Thanks, but it looks like your PyPI is in a tar file. I'm using Win7.  RO 2.9.3 is a download.  I see some refs to Win, but I'm not sure what to make of them.
> 
> On 1/25/2012 9:34 AM, Russell Owen wrote:
>> You have an incomplete package. Download RO from PyPI. The stuff you are looking for is in RO.Astro. euler is included in the package.
>> 
>> -- Russell
>> 
>> On Jan 24, 2012, at 8:29 PM, Wayne Watson wrote:
>> 
>>> It's been quite awhile since I used python, but I was digging around on
>>> PC for something on precession, and discovered some code for it,
>>> prec.py.   Here are the first few lines.
>>> 
>>> #!/usr/bin/env python
>>> """
>>> History:
>>> P.T.Wallace   Starlink   10 July 1994
>>> 2002-07-08 ROwen    Converted to Python.
>>> 2007-04-24 ROwen    Converted from Numeric to numpy (in test code).
>>> """
>>> import RO.PhysConst
>>> from euler import *
>>> ...
>>> ...
>>> 
>>> It dies on RO.PhysConst when I run it.  Probably a further difficulty is
>>> the euler reference.
>>> I have the code for RO.PhysConst.py
>>> 
>>> What needs to be done to successfully execute prec.py?
>>> 
>>> -- 
>>>            Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>> 
>>>              (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>>>               Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
>>> 
>>>                      In 2904 there will be 5 solar eclipses.
>>>                      On July 16, 2185 the longest solar
>>>                      eclipse inf 5k years will occur, 7 min.
>>> 
>>>                     Web Page:<www.speckledwithstars.net/>
>>> 
>>> 
>>> _______________________________________________
>>> AstroPy mailing list
>>> AstroPy at scipy.org
>>> http://mail.scipy.org/mailman/listinfo/astropy
>> 
> 
> -- 
>           Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
> 
>             (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>              Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
> 
>                     In 2904 there will be 5 solar eclipses.
>                     On July 16, 2185 the longest solar
>                     eclipse inf 5k years will occur, 7 min.
> 
>                    Web Page:<www.speckledwithstars.net/>
> 
> 



From sierra_mtnview at sbcglobal.net  Wed Jan 25 15:59:15 2012
From: sierra_mtnview at sbcglobal.net (Wayne Watson)
Date: Wed, 25 Jan 2012 12:59:15 -0800
Subject: [AstroPy] Back to Python. Precession and PhysConst code.
In-Reply-To: <771C9C40-25EC-4567-992F-63B054304694@uw.edu>
References: <4F1F8529.4010303@sbcglobal.net>
	<E95B220B-5CF3-45DF-A298-769FF1D55B9B@uw.edu>
	<4F205BE2.4090608@sbcglobal.net>
	<771C9C40-25EC-4567-992F-63B054304694@uw.edu>
Message-ID: <4F206D23.4080803@sbcglobal.net>

So it's a Linux application?  No msi or zip?  Never used distutils.  
Sounds hairy.

I have the fortran version, so maybe I'll try that.  What I liked about 
the py program is that it had a test inside it.

On 1/25/2012 12:22 PM, Russell Owen wrote:
> Yes to all that. It is pure python. Install it using distutils as usual.
>
> -- Russell
>
> On Jan 25, 2012, at 11:45 AM, Wayne Watson wrote:
>
>> Thanks, but it looks like your PyPI is in a tar file. I'm using Win7.  RO 2.9.3 is a download.  I see some refs to Win, but I'm not sure what to make of them.
>>
>> On 1/25/2012 9:34 AM, Russell Owen wrote:
>>> You have an incomplete package. Download RO from PyPI. The stuff you are looking for is in RO.Astro. euler is included in the package.
>>>
>>> -- Russell
>>>
>>> On Jan 24, 2012, at 8:29 PM, Wayne Watson wrote:
>>>
>>>> It's been quite awhile since I used python, but I was digging around on
>>>> PC for something on precession, and discovered some code for it,
>>>> prec.py.   Here are the first few lines.
>>>>
>>>> #!/usr/bin/env python
>>>> """
>>>> History:
>>>> P.T.Wallace   Starlink   10 July 1994
>>>> 2002-07-08 ROwen    Converted to Python.
>>>> 2007-04-24 ROwen    Converted from Numeric to numpy (in test code).
>>>> """
>>>> import RO.PhysConst
>>>> from euler import *
>>>> ...
>>>> ...
>>>>
>>>> It dies on RO.PhysConst when I run it.  Probably a further difficulty is
>>>> the euler reference.
>>>> I have the code for RO.PhysConst.py
>>>>
>>>> What needs to be done to successfully execute prec.py?
>>>>
>>>> -- 
>>>>             Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>>>
>>>>               (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>>>>                Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
>>>>
>>>>                       In 2904 there will be 5 solar eclipses.
>>>>                       On July 16, 2185 the longest solar
>>>>                       eclipse inf 5k years will occur, 7 min.
>>>>
>>>>                      Web Page:<www.speckledwithstars.net/>
>>>>
>>>>
>>>> _______________________________________________
>>>> AstroPy mailing list
>>>> AstroPy at scipy.org
>>>> http://mail.scipy.org/mailman/listinfo/astropy
>> -- 
>>            Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>
>>              (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>>               Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
>>
>>                      In 2904 there will be 5 solar eclipses.
>>                      On July 16, 2185 the longest solar
>>                      eclipse inf 5k years will occur, 7 min.
>>
>>                     Web Page:<www.speckledwithstars.net/>
>>
>>
>

-- 
            Wayne Watson (Watson Adventures, Prop., Nevada City, CA)

              (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
               Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet

                      In 2904 there will be 5 solar eclipses.
                      On July 16, 2185 the longest solar
                      eclipse inf 5k years will occur, 7 min.

                     Web Page:<www.speckledwithstars.net/>




From rowen at uw.edu  Wed Jan 25 16:41:20 2012
From: rowen at uw.edu (Russell Owen)
Date: Wed, 25 Jan 2012 13:41:20 -0800
Subject: [AstroPy] Back to Python. Precession and PhysConst code.
In-Reply-To: <4F206D23.4080803@sbcglobal.net>
References: <4F1F8529.4010303@sbcglobal.net>
	<E95B220B-5CF3-45DF-A298-769FF1D55B9B@uw.edu>
	<4F205BE2.4090608@sbcglobal.net>
	<771C9C40-25EC-4567-992F-63B054304694@uw.edu>
	<4F206D23.4080803@sbcglobal.net>
Message-ID: <45CA1369-23A0-425A-AD62-083058AADF9A@uw.edu>

No, it's a cross-platform unix/mac/windows package. It uses Python's older standard installation system (one that precedes easy_install).

In windows I believe you go to the command line, cd to the package directory and type "setup.py install". On any other system you type "python setup.py install".

-- Russell

On Jan 25, 2012, at 12:59 PM, Wayne Watson wrote:

> So it's a Linux application?  No msi or zip?  Never used distutils.  Sounds hairy.
> 
> I have the fortran version, so maybe I'll try that.  What I liked about the py program is that it had a test inside it.
> 
> On 1/25/2012 12:22 PM, Russell Owen wrote:
>> Yes to all that. It is pure python. Install it using distutils as usual.
>> 
>> -- Russell
>> 
>> On Jan 25, 2012, at 11:45 AM, Wayne Watson wrote:
>> 
>>> Thanks, but it looks like your PyPI is in a tar file. I'm using Win7.  RO 2.9.3 is a download.  I see some refs to Win, but I'm not sure what to make of them.
>>> 
>>> On 1/25/2012 9:34 AM, Russell Owen wrote:
>>>> You have an incomplete package. Download RO from PyPI. The stuff you are looking for is in RO.Astro. euler is included in the package.
>>>> 
>>>> -- Russell
>>>> 
>>>> On Jan 24, 2012, at 8:29 PM, Wayne Watson wrote:
>>>> 
>>>>> It's been quite awhile since I used python, but I was digging around on
>>>>> PC for something on precession, and discovered some code for it,
>>>>> prec.py.   Here are the first few lines.
>>>>> 
>>>>> #!/usr/bin/env python
>>>>> """
>>>>> History:
>>>>> P.T.Wallace   Starlink   10 July 1994
>>>>> 2002-07-08 ROwen    Converted to Python.
>>>>> 2007-04-24 ROwen    Converted from Numeric to numpy (in test code).
>>>>> """
>>>>> import RO.PhysConst
>>>>> from euler import *
>>>>> ...
>>>>> ...
>>>>> 
>>>>> It dies on RO.PhysConst when I run it.  Probably a further difficulty is
>>>>> the euler reference.
>>>>> I have the code for RO.PhysConst.py
>>>>> 
>>>>> What needs to be done to successfully execute prec.py?
>>>>> 
>>>>> -- 
>>>>>            Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>>>> 
>>>>>              (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>>>>>               Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
>>>>> 
>>>>>                      In 2904 there will be 5 solar eclipses.
>>>>>                      On July 16, 2185 the longest solar
>>>>>                      eclipse inf 5k years will occur, 7 min.
>>>>> 
>>>>>                     Web Page:<www.speckledwithstars.net/>
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> AstroPy mailing list
>>>>> AstroPy at scipy.org
>>>>> http://mail.scipy.org/mailman/listinfo/astropy
>>> -- 
>>>           Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>> 
>>>             (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>>>              Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
>>> 
>>>                     In 2904 there will be 5 solar eclipses.
>>>                     On July 16, 2185 the longest solar
>>>                     eclipse inf 5k years will occur, 7 min.
>>> 
>>>                    Web Page:<www.speckledwithstars.net/>
>>> 
>>> 
>> 
> 
> -- 
>           Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
> 
>             (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>              Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
> 
>                     In 2904 there will be 5 solar eclipses.
>                     On July 16, 2185 the longest solar
>                     eclipse inf 5k years will occur, 7 min.
> 
>                    Web Page:<www.speckledwithstars.net/>
> 
> 



From sierra_mtnview at sbcglobal.net  Wed Jan 25 17:02:18 2012
From: sierra_mtnview at sbcglobal.net (Wayne Watson)
Date: Wed, 25 Jan 2012 14:02:18 -0800
Subject: [AstroPy] Back to Python. Precession and PhysConst code.
In-Reply-To: <45CA1369-23A0-425A-AD62-083058AADF9A@uw.edu>
References: <4F1F8529.4010303@sbcglobal.net>
	<E95B220B-5CF3-45DF-A298-769FF1D55B9B@uw.edu>
	<4F205BE2.4090608@sbcglobal.net>
	<771C9C40-25EC-4567-992F-63B054304694@uw.edu>
	<4F206D23.4080803@sbcglobal.net>
	<45CA1369-23A0-425A-AD62-083058AADF9A@uw.edu>
Message-ID: <4F207BEA.4040502@sbcglobal.net>

OK, how do I untar it Win7? Ah, good fortune. I have MinGW (gfortran) 
that has a linux-like shell, and has tar.

Is there a description of the module's contents?

On 1/25/2012 1:41 PM, Russell Owen wrote:
> No, it's a cross-platform unix/mac/windows package. It uses Python's older standard installation system (one that precedes easy_install).
>
> In windows I believe you go to the command line, cd to the package directory and type "setup.py install". On any other system you type "python setup.py install".
>
> -- Russell
>
> On Jan 25, 2012, at 12:59 PM, Wayne Watson wrote:
>
>> So it's a Linux application?  No msi or zip?  Never used distutils.  Sounds hairy.
>>
>> I have the fortran version, so maybe I'll try that.  What I liked about the py program is that it had a test inside it.
>>
>> On 1/25/2012 12:22 PM, Russell Owen wrote:
>>> Yes to all that. It is pure python. Install it using distutils as usual.
>>>
>>> -- Russell
>>>
>>> On Jan 25, 2012, at 11:45 AM, Wayne Watson wrote:
>>>
>>>> Thanks, but it looks like your PyPI is in a tar file. I'm using Win7.  RO 2.9.3 is a download.  I see some refs to Win, but I'm not sure what to make of them.
>>>>
>>>> On 1/25/2012 9:34 AM, Russell Owen wrote:
>>>>> You have an incomplete package. Download RO from PyPI. The stuff you are looking for is in RO.Astro. euler is included in the package.
>>>>>
>>>>> -- Russell
>>>>>
>>>>> On Jan 24, 2012, at 8:29 PM, Wayne Watson wrote:
>>>>>
>>>>>> It's been quite awhile since I used python, but I was digging around on
>>>>>> PC for something on precession, and discovered some code for it,
>>>>>> prec.py.   Here are the first few lines.
>>>>>>
>>>>>> #!/usr/bin/env python
>>>>>> """
>>>>>> History:
>>>>>> P.T.Wallace   Starlink   10 July 1994
>>>>>> 2002-07-08 ROwen    Converted to Python.
>>>>>> 2007-04-24 ROwen    Converted from Numeric to numpy (in test code).
>>>>>> """
>>>>>> import RO.PhysConst
>>>>>> from euler import *
>>>>>> ...
>>>>>> ...
>>>>>>
>>>>>> It dies on RO.PhysConst when I run it.  Probably a further difficulty is
>>>>>> the euler reference.
>>>>>> I have the code for RO.PhysConst.py
>>>>>>
>>>>>> What needs to be done to successfully execute prec.py?
>>>>>>
>>>>>> -- 
>>>>>>             Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>>>>>
>>>>>>               (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>>>>>>                Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
>>>>>>
>>>>>>                       In 2904 there will be 5 solar eclipses.
>>>>>>                       On July 16, 2185 the longest solar
>>>>>>                       eclipse inf 5k years will occur, 7 min.
>>>>>>
>>>>>>                      Web Page:<www.speckledwithstars.net/>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> AstroPy mailing list
>>>>>> AstroPy at scipy.org
>>>>>> http://mail.scipy.org/mailman/listinfo/astropy
>>>> -- 
>>>>            Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>>>
>>>>              (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>>>>               Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
>>>>
>>>>                      In 2904 there will be 5 solar eclipses.
>>>>                      On July 16, 2185 the longest solar
>>>>                      eclipse inf 5k years will occur, 7 min.
>>>>
>>>>                     Web Page:<www.speckledwithstars.net/>
>>>>
>>>>
>> -- 
>>            Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>
>>              (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>>               Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
>>
>>                      In 2904 there will be 5 solar eclipses.
>>                      On July 16, 2185 the longest solar
>>                      eclipse inf 5k years will occur, 7 min.
>>
>>                     Web Page:<www.speckledwithstars.net/>
>>
>>
>

-- 
            Wayne Watson (Watson Adventures, Prop., Nevada City, CA)

              (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
               Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet

                      In 2904 there will be 5 solar eclipses.
                      On July 16, 2185 the longest solar
                      eclipse inf 5k years will occur, 7 min.

                     Web Page:<www.speckledwithstars.net/>




From embray at stsci.edu  Wed Jan 25 19:31:57 2012
From: embray at stsci.edu (Erik Bray)
Date: Wed, 25 Jan 2012 19:31:57 -0500
Subject: [AstroPy] Back to Python. Precession and PhysConst code.
In-Reply-To: <4F207BEA.4040502@sbcglobal.net>
References: <4F1F8529.4010303@sbcglobal.net>
	<E95B220B-5CF3-45DF-A298-769FF1D55B9B@uw.edu>
	<4F205BE2.4090608@sbcglobal.net>
	<771C9C40-25EC-4567-992F-63B054304694@uw.edu>
	<4F206D23.4080803@sbcglobal.net>
	<45CA1369-23A0-425A-AD62-083058AADF9A@uw.edu>
	<4F207BEA.4040502@sbcglobal.net>
Message-ID: <4F209EFD.7010707@stsci.edu>

Hi Wayne,

     Your best bet is to install packages into a standard location that 
Python is aware of.  On Windows that would be 
C:\PythonX.Y\site-packages.  As Russel wrote, one way to do that is to 
download the tar.gz file containing the source code, extract it, and 
then run setup.py install.

     Another way--for example if you don't have a program in Windows 
that can open tar/gz files--is to install easy_install+distribute. 
Simply download http://python-distribute.org/distribute_setup.py and run 
`python distribute_setup.py`.  Then run: `easy_install RO`.  That should 
ensure that the RO package is installed in the proper place where Python 
can find it.


Erik

P.S.

     Don't worry about distutils--distutils is the standard product 
packaging system that comes with Python.  If you see a Python package 
that comes with a file named 'setup.py', then executing `python setup.py 
install` will install the package for you in such a way that it can 
always be found by Python.  The existence of a setup.py file means that 
the package is installable with distutils or some derivative thereof.

     distribute, which I suggested you install, is one such derivative. 
  It includes the program called easy_install which makes it relatively 
painless (in most cases) to install new Python packages hosted on the 
Python Packaging Index (http://pypi.python.org).

     For a full explanation of the Python packaging ecosystem, see my 
presentation at http://stsdas.stsci.edu/download/packaging-overview.pdf 
  I'll be happy to answer any further questions.

On 01/25/2012 05:02 PM, Wayne Watson wrote:
> OK, how do I untar it Win7? Ah, good fortune. I have MinGW (gfortran)
> that has a linux-like shell, and has tar.
>
> Is there a description of the module's contents?
>
> On 1/25/2012 1:41 PM, Russell Owen wrote:
>> No, it's a cross-platform unix/mac/windows package. It uses Python's older standard installation system (one that precedes easy_install).
>>
>> In windows I believe you go to the command line, cd to the package directory and type "setup.py install". On any other system you type "python setup.py install".
>>
>> -- Russell
>>
>> On Jan 25, 2012, at 12:59 PM, Wayne Watson wrote:
>>
>>> So it's a Linux application?  No msi or zip?  Never used distutils.  Sounds hairy.
>>>
>>> I have the fortran version, so maybe I'll try that.  What I liked about the py program is that it had a test inside it.
>>>
>>> On 1/25/2012 12:22 PM, Russell Owen wrote:
>>>> Yes to all that. It is pure python. Install it using distutils as usual.
>>>>
>>>> -- Russell
>>>>
>>>> On Jan 25, 2012, at 11:45 AM, Wayne Watson wrote:
>>>>
>>>>> Thanks, but it looks like your PyPI is in a tar file. I'm using Win7.  RO 2.9.3 is a download.  I see some refs to Win, but I'm not sure what to make of them.
>>>>>
>>>>> On 1/25/2012 9:34 AM, Russell Owen wrote:
>>>>>> You have an incomplete package. Download RO from PyPI. The stuff you are looking for is in RO.Astro. euler is included in the package.
>>>>>>
>>>>>> -- Russell
>>>>>>
>>>>>> On Jan 24, 2012, at 8:29 PM, Wayne Watson wrote:
>>>>>>
>>>>>>> It's been quite awhile since I used python, but I was digging around on
>>>>>>> PC for something on precession, and discovered some code for it,
>>>>>>> prec.py.   Here are the first few lines.
>>>>>>>
>>>>>>> #!/usr/bin/env python
>>>>>>> """
>>>>>>> History:
>>>>>>> P.T.Wallace   Starlink   10 July 1994
>>>>>>> 2002-07-08 ROwen    Converted to Python.
>>>>>>> 2007-04-24 ROwen    Converted from Numeric to numpy (in test code).
>>>>>>> """
>>>>>>> import RO.PhysConst
>>>>>>> from euler import *
>>>>>>> ...
>>>>>>> ...
>>>>>>>
>>>>>>> It dies on RO.PhysConst when I run it.  Probably a further difficulty is
>>>>>>> the euler reference.
>>>>>>> I have the code for RO.PhysConst.py
>>>>>>>
>>>>>>> What needs to be done to successfully execute prec.py?
>>>>>>>
>>>>>>> --
>>>>>>>              Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>>>>>>
>>>>>>>                (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>>>>>>>                 Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
>>>>>>>
>>>>>>>                        In 2904 there will be 5 solar eclipses.
>>>>>>>                        On July 16, 2185 the longest solar
>>>>>>>                        eclipse inf 5k years will occur, 7 min.
>>>>>>>
>>>>>>>                       Web Page:<www.speckledwithstars.net/>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> AstroPy mailing list
>>>>>>> AstroPy at scipy.org
>>>>>>> http://mail.scipy.org/mailman/listinfo/astropy
>>>>> --
>>>>>             Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>>>>
>>>>>               (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>>>>>                Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
>>>>>
>>>>>                       In 2904 there will be 5 solar eclipses.
>>>>>                       On July 16, 2185 the longest solar
>>>>>                       eclipse inf 5k years will occur, 7 min.
>>>>>
>>>>>                      Web Page:<www.speckledwithstars.net/>
>>>>>
>>>>>
>>> --
>>>             Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>>
>>>               (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>>>                Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
>>>
>>>                       In 2904 there will be 5 solar eclipses.
>>>                       On July 16, 2185 the longest solar
>>>                       eclipse inf 5k years will occur, 7 min.
>>>
>>>                      Web Page:<www.speckledwithstars.net/>
>>>
>>>
>>
>



From sierra_mtnview at sbcglobal.net  Wed Jan 25 21:03:39 2012
From: sierra_mtnview at sbcglobal.net (Wayne Watson)
Date: Wed, 25 Jan 2012 18:03:39 -0800
Subject: [AstroPy] Back to Python. Precession and PhysConst code.
In-Reply-To: <4F209EFD.7010707@stsci.edu>
References: <4F1F8529.4010303@sbcglobal.net>
	<E95B220B-5CF3-45DF-A298-769FF1D55B9B@uw.edu>
	<4F205BE2.4090608@sbcglobal.net>
	<771C9C40-25EC-4567-992F-63B054304694@uw.edu>
	<4F206D23.4080803@sbcglobal.net>
	<45CA1369-23A0-425A-AD62-083058AADF9A@uw.edu>
	<4F207BEA.4040502@sbcglobal.net> <4F209EFD.7010707@stsci.edu>
Message-ID: <4F20B47B.3060808@sbcglobal.net>

Hi, Erik. I tried the "Setup.py install", but I didn't have the folder 
installed under .../site-packages. It couldn't find setup.py. I'll 
adjust that per your comment. I was able to extract the tar.gz file onto 
my Win7 with IZarc.

Thanks for the P.S.  I'm in and out of the Python world as it is useful, 
which boils down to maybe a few days every month.  Matters could pick up 
though.

Two years ago or so I was looking for a way to distribute a py program 
in an (exe)cutable form, but whatever process I tried was much too trouble.

On 1/25/2012 4:31 PM, Erik Bray wrote:
> Hi Wayne,
>
>       Your best bet is to install packages into a standard location that
> Python is aware of.  On Windows that would be
> C:\PythonX.Y\site-packages.  As Russel wrote, one way to do that is to
> download the tar.gz file containing the source code, extract it, and
> then run setup.py install.
>
>       Another way--for example if you don't have a program in Windows
> that can open tar/gz files--is to install easy_install+distribute.
> Simply download http://python-distribute.org/distribute_setup.py and run
> `python distribute_setup.py`.  Then run: `easy_install RO`.  That should
> ensure that the RO package is installed in the proper place where Python
> can find it.
>
>
> Erik
>
> P.S.
>
>       Don't worry about distutils--distutils is the standard product
> packaging system that comes with Python.  If you see a Python package
> that comes with a file named 'setup.py', then executing `python setup.py
> install` will install the package for you in such a way that it can
> always be found by Python.  The existence of a setup.py file means that
> the package is installable with distutils or some derivative thereof.
>
>       distribute, which I suggested you install, is one such derivative.
>    It includes the program called easy_install which makes it relatively
> painless (in most cases) to install new Python packages hosted on the
> Python Packaging Index (http://pypi.python.org).
>
>       For a full explanation of the Python packaging ecosystem, see my
> presentation at http://stsdas.stsci.edu/download/packaging-overview.pdf
>    I'll be happy to answer any further questions.
>
> On 01/25/2012 05:02 PM, Wayne Watson wrote:
>> OK, how do I untar it Win7? Ah, good fortune. I have MinGW (gfortran)
>> that has a linux-like shell, and has tar.
>>
>> Is there a description of the module's contents?
>>
>> On 1/25/2012 1:41 PM, Russell Owen wrote:
>>> No, it's a cross-platform unix/mac/windows package. It uses Python's older standard installation system (one that precedes easy_install).
>>>
>>> In windows I believe you go to the command line, cd to the package directory and type "setup.py install". On any other system you type "python setup.py install".
>>>
>>> -- Russell
>>>
>>> On Jan 25, 2012, at 12:59 PM, Wayne Watson wrote:
>>>
>>>> So it's a Linux application?  No msi or zip?  Never used distutils.  Sounds hairy.
>>>>
>>>> I have the fortran version, so maybe I'll try that.  What I liked about the py program is that it had a test inside it.
>>>>
>>>> On 1/25/2012 12:22 PM, Russell Owen wrote:
>>>>> Yes to all that. It is pure python. Install it using distutils as usual.
>>>>>
>>>>> -- Russell
>>>>>
>>>>> On Jan 25, 2012, at 11:45 AM, Wayne Watson wrote:
>>>>>
>>>>>> Thanks, but it looks like your PyPI is in a tar file. I'm using Win7.  RO 2.9.3 is a download.  I see some refs to Win, but I'm not sure what to make of them.
>>>>>>
>>>>>> On 1/25/2012 9:34 AM, Russell Owen wrote:
>>>>>>> You have an incomplete package. Download RO from PyPI. The stuff you are looking for is in RO.Astro. euler is included in the package.
>>>>>>>
>>>>>>> -- Russell
>>>>>>>
>>>>>>> On Jan 24, 2012, at 8:29 PM, Wayne Watson wrote:
>>>>>>>
>>>>>>>> It's been quite awhile since I used python, but I was digging around on
>>>>>>>> PC for something on precession, and discovered some code for it,
>>>>>>>> prec.py.   Here are the first few lines.
>>>>>>>>
>>>>>>>> #!/usr/bin/env python
>>>>>>>> """
>>>>>>>> History:
>>>>>>>> P.T.Wallace   Starlink   10 July 1994
>>>>>>>> 2002-07-08 ROwen    Converted to Python.
>>>>>>>> 2007-04-24 ROwen    Converted from Numeric to numpy (in test code).
>>>>>>>> """
>>>>>>>> import RO.PhysConst
>>>>>>>> from euler import *
>>>>>>>> ...
>>>>>>>> ...
>>>>>>>>
>>>>>>>> It dies on RO.PhysConst when I run it.  Probably a further difficulty is
>>>>>>>> the euler reference.
>>>>>>>> I have the code for RO.PhysConst.py
>>>>>>>>
>>>>>>>> What needs to be done to successfully execute prec.py?
>>>>>>>>
>>>>>>>> --
>>>>>>>>               Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>>>>>>>
>>>>>>>>                 (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>>>>>>>>                  Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
>>>>>>>>
>>>>>>>>                         In 2904 there will be 5 solar eclipses.
>>>>>>>>                         On July 16, 2185 the longest solar
>>>>>>>>                         eclipse inf 5k years will occur, 7 min.
>>>>>>>>
>>>>>>>>                        Web Page:<www.speckledwithstars.net/>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> AstroPy mailing list
>>>>>>>> AstroPy at scipy.org
>>>>>>>> http://mail.scipy.org/mailman/listinfo/astropy
>>>>>> --
>>>>>>              Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>>>>>
>>>>>>                (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>>>>>>                 Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
>>>>>>
>>>>>>                        In 2904 there will be 5 solar eclipses.
>>>>>>                        On July 16, 2185 the longest solar
>>>>>>                        eclipse inf 5k years will occur, 7 min.
>>>>>>
>>>>>>                       Web Page:<www.speckledwithstars.net/>
>>>>>>
>>>>>>
>>>> --
>>>>              Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>>>
>>>>                (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>>>>                 Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet
>>>>
>>>>                        In 2904 there will be 5 solar eclipses.
>>>>                        On July 16, 2185 the longest solar
>>>>                        eclipse inf 5k years will occur, 7 min.
>>>>
>>>>                       Web Page:<www.speckledwithstars.net/>
>>>>
>>>>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>

-- 
            Wayne Watson (Watson Adventures, Prop., Nevada City, CA)

              (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
               Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet

                      In 2904 there will be 5 solar eclipses.
                      On July 16, 2185 the longest solar
                      eclipse inf 5k years will occur, 7 min.

                     Web Page:<www.speckledwithstars.net/>




From sierra_mtnview at sbcglobal.net  Wed Jan 25 21:15:46 2012
From: sierra_mtnview at sbcglobal.net (Wayne Watson)
Date: Wed, 25 Jan 2012 18:15:46 -0800
Subject: [AstroPy] Back to Python. Precession and PhysConst code.
In-Reply-To: <4F209EFD.7010707@stsci.edu>
References: <4F1F8529.4010303@sbcglobal.net>
	<E95B220B-5CF3-45DF-A298-769FF1D55B9B@uw.edu>
	<4F205BE2.4090608@sbcglobal.net>
	<771C9C40-25EC-4567-992F-63B054304694@uw.edu>
	<4F206D23.4080803@sbcglobal.net>
	<45CA1369-23A0-425A-AD62-083058AADF9A@uw.edu>
	<4F207BEA.4040502@sbcglobal.net> <4F209EFD.7010707@stsci.edu>
Message-ID: <4F20B752.7010305@sbcglobal.net>

Well, that didn't work.  Here's what happened.

C:\Python27\Lib\site-packages\RO-2.9.3>setup.py install
Traceback (most recent call last):
   File "C:\Python27\Lib\site-packages\RO-2.9.3\setup.py", line 31, in 
<module>
     from setuptools import setup, find_packages
ImportError: No module named setuptools

C:\Python27\Lib\site-packages\RO-2.9.3>dir
  Volume in drive C is HP
  Volume Serial Number is 7AB2-5106

  Directory of C:\Python27\Lib\site-packages\RO-2.9.3

01/25/2012  04:15 PM <DIR>          .
01/25/2012  04:15 PM <DIR>          ..
01/25/2012  04:15 PM <DIR>          docs
09/09/2011  02:58 PM             2,311 PKG-INFO
01/25/2012  04:15 PM <DIR>          python
08/03/2010  10:06 AM               281 README.txt
08/04/2010  05:09 PM             2,490 releaseNewVersion.py
01/25/2012  04:15 PM <DIR>          RO.egg-info
09/09/2011  02:58 PM                59 setup.cfg
06/18/2010  01:30 PM             3,145 setup.py
01/25/2012  04:15 PM <DIR>          tools
01/25/2012  04:15 PM <DIR>          ups
                5 File(s)          8,286 bytes
                7 Dir(s)  536,760,406,016 bytes free

C:\Python27\Lib\site-packages\RO-2.9.3>

-- 
            Wayne Watson (Watson Adventures, Prop., Nevada City, CA)

              (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
               Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet

                      In 2904 there will be 5 solar eclipses.
                      On July 16, 2185 the longest solar
                      eclipse inf 5k years will occur, 7 min.

                     Web Page:<www.speckledwithstars.net/>




From thomas.robitaille at gmail.com  Thu Jan 26 04:01:25 2012
From: thomas.robitaille at gmail.com (Thomas Robitaille)
Date: Thu, 26 Jan 2012 10:01:25 +0100
Subject: [AstroPy] Astropy website/logo competition!
Message-ID: <CAGMHX_1qKa37+n=-E_9nn1QLw3TSHuaTWT7sA14Cw+ya+52wzA@mail.gmail.com>

Hi everyone,

We are holding a design competition for the http://www.astropy.org
website and logo! There is a prize of a $50 (or equivalent) Amazon
Voucher for the winner, and the deadline for submissions is March 31st
2012. Instructions and guidelines can be found at the following page:

http://github.com/astropy/astropy/wiki/Website-logo-competition

Please let us know if you have any questions. We look forward to your
submissions!

Cheers,
Tom


From jeanluc.menut at free.fr  Thu Jan 26 09:57:21 2012
From: jeanluc.menut at free.fr (Jean-Luc Menut)
Date: Thu, 26 Jan 2012 15:57:21 +0100
Subject: [AstroPy] Back to Python. Precession and PhysConst code.
In-Reply-To: <4F207BEA.4040502@sbcglobal.net>
References: <4F1F8529.4010303@sbcglobal.net>
	<E95B220B-5CF3-45DF-A298-769FF1D55B9B@uw.edu>
	<4F205BE2.4090608@sbcglobal.net>
	<771C9C40-25EC-4567-992F-63B054304694@uw.edu>
	<4F206D23.4080803@sbcglobal.net>
	<45CA1369-23A0-425A-AD62-083058AADF9A@uw.edu>
	<4F207BEA.4040502@sbcglobal.net>
Message-ID: <4F2169D1.3080200@free.fr>

Le 25/01/2012 23:02, Wayne Watson a ?crit :
> OK, how do I untar it Win7? Ah, good fortune. I have MinGW (gfortran)
> that has a linux-like shell, and has tar.


Any decent archive manager such as 7zip works also with tar/gz/bz2 files


From embray at stsci.edu  Thu Jan 26 10:19:13 2012
From: embray at stsci.edu (Erik Bray)
Date: Thu, 26 Jan 2012 10:19:13 -0500
Subject: [AstroPy] Back to Python. Precession and PhysConst code.
In-Reply-To: <4F20B752.7010305@sbcglobal.net>
References: <4F1F8529.4010303@sbcglobal.net>
	<E95B220B-5CF3-45DF-A298-769FF1D55B9B@uw.edu>
	<4F205BE2.4090608@sbcglobal.net>
	<771C9C40-25EC-4567-992F-63B054304694@uw.edu>
	<4F206D23.4080803@sbcglobal.net>
	<45CA1369-23A0-425A-AD62-083058AADF9A@uw.edu>
	<4F207BEA.4040502@sbcglobal.net> <4F209EFD.7010707@stsci.edu>
	<4F20B752.7010305@sbcglobal.net>
Message-ID: <4F216EF1.9080305@stsci.edu>

That means that this RO package requires distribute or setuptools to 
install, but was not kind enough to include it with the package.

Download http://python-distribute.org/distribute_setup.py and run
`python distribute_setup.py`.  Then run: `easy_install RO` (assuming 
that you have C:\Python27\Scripts on your path, because that's where the 
easy_install program is installed to).

If you use that, then you don't have to worry about downloading the 
archive from PyPI or even extracting it.  easy_install will do that for 
you for any package on PyPI.

Erik

On 01/25/2012 09:15 PM, Wayne Watson wrote:
> Well, that didn't work. Here's what happened.
>
> C:\Python27\Lib\site-packages\RO-2.9.3>setup.py install
> Traceback (most recent call last):
> File "C:\Python27\Lib\site-packages\RO-2.9.3\setup.py", line 31, in
> <module>
> from setuptools import setup, find_packages
> ImportError: No module named setuptools
>
> C:\Python27\Lib\site-packages\RO-2.9.3>dir
> Volume in drive C is HP
> Volume Serial Number is 7AB2-5106
>
> Directory of C:\Python27\Lib\site-packages\RO-2.9.3
>
> 01/25/2012 04:15 PM <DIR> .
> 01/25/2012 04:15 PM <DIR> ..
> 01/25/2012 04:15 PM <DIR> docs
> 09/09/2011 02:58 PM 2,311 PKG-INFO
> 01/25/2012 04:15 PM <DIR> python
> 08/03/2010 10:06 AM 281 README.txt
> 08/04/2010 05:09 PM 2,490 releaseNewVersion.py
> 01/25/2012 04:15 PM <DIR> RO.egg-info
> 09/09/2011 02:58 PM 59 setup.cfg
> 06/18/2010 01:30 PM 3,145 setup.py
> 01/25/2012 04:15 PM <DIR> tools
> 01/25/2012 04:15 PM <DIR> ups
> 5 File(s) 8,286 bytes
> 7 Dir(s) 536,760,406,016 bytes free
>
> C:\Python27\Lib\site-packages\RO-2.9.3>
>



From taro at ap.smu.ca  Thu Jan 26 10:25:50 2012
From: taro at ap.smu.ca (Taro Sato)
Date: Thu, 26 Jan 2012 11:25:50 -0400
Subject: [AstroPy] Astropy website/logo competition!
In-Reply-To: <CAGMHX_1qKa37+n=-E_9nn1QLw3TSHuaTWT7sA14Cw+ya+52wzA@mail.gmail.com>
References: <CAGMHX_1qKa37+n=-E_9nn1QLw3TSHuaTWT7sA14Cw+ya+52wzA@mail.gmail.com>
Message-ID: <CA+ABecy_2vkG2ic6NWT43tgHdMPmNaNCdde5mFr8LTK+r8u-WQ@mail.gmail.com>

On Thu, Jan 26, 2012 at 5:01 AM, Thomas Robitaille
<thomas.robitaille at gmail.com> wrote:
> Hi everyone,
>
> We are holding a design competition for the http://www.astropy.org
> website and logo! There is a prize of a $50 (or equivalent) Amazon
> Voucher for the winner, and the deadline for submissions is March 31st
> 2012. Instructions and guidelines can be found at the following page:
>
> http://github.com/astropy/astropy/wiki/Website-logo-competition
>
> Please let us know if you have any questions. We look forward to your
> submissions!
>


Is the voucher only redeemable at US Amazon.com?



-- 
Taro Sato
Department of Astronomy & Physics
Saint Mary's University? ? ? ? ? ?? email: taro at ap.smu.ca
Halifax, NS B3H 3C3? ? ? ? ? ? ? ?? phone: (902)420-5018
Canada? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? web: http://ap.smu.ca/~taro


From thomas.robitaille at gmail.com  Thu Jan 26 10:30:17 2012
From: thomas.robitaille at gmail.com (Thomas Robitaille)
Date: Thu, 26 Jan 2012 16:30:17 +0100
Subject: [AstroPy] Astropy website/logo competition!
In-Reply-To: <CA+ABecy_2vkG2ic6NWT43tgHdMPmNaNCdde5mFr8LTK+r8u-WQ@mail.gmail.com>
References: <CAGMHX_1qKa37+n=-E_9nn1QLw3TSHuaTWT7sA14Cw+ya+52wzA@mail.gmail.com>
	<CA+ABecy_2vkG2ic6NWT43tgHdMPmNaNCdde5mFr8LTK+r8u-WQ@mail.gmail.com>
Message-ID: <CAGMHX_0LAGspzOh_Y20RUOZvk3ALuUh=3WZi9h9CVbs5WJycFQ@mail.gmail.com>

Hi Taro,

> Is the voucher only redeemable at US Amazon.com?

No, we'll make sure that we provide a voucher for the right country
(using the exchange rate at the deadline)

Tom :-)

>
>
>
> --
> Taro Sato
> Department of Astronomy & Physics
> Saint Mary's University? ? ? ? ? ?? email: taro at ap.smu.ca
> Halifax, NS B3H 3C3? ? ? ? ? ? ? ?? phone: (902)420-5018
> Canada? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? web: http://ap.smu.ca/~taro


From sierra_mtnview at sbcglobal.net  Thu Jan 26 14:16:36 2012
From: sierra_mtnview at sbcglobal.net (Wayne Watson)
Date: Thu, 26 Jan 2012 11:16:36 -0800
Subject: [AstroPy] Back to Python. Precession and PhysConst code.
In-Reply-To: <4F2169D1.3080200@free.fr>
References: <4F1F8529.4010303@sbcglobal.net>
	<E95B220B-5CF3-45DF-A298-769FF1D55B9B@uw.edu>
	<4F205BE2.4090608@sbcglobal.net>
	<771C9C40-25EC-4567-992F-63B054304694@uw.edu>
	<4F206D23.4080803@sbcglobal.net>
	<45CA1369-23A0-425A-AD62-083058AADF9A@uw.edu>
	<4F207BEA.4040502@sbcglobal.net> <4F2169D1.3080200@free.fr>
Message-ID: <4F21A694.7070505@sbcglobal.net>

My IZarc took care of it.

On 1/26/2012 6:57 AM, Jean-Luc Menut wrote:
> Le 25/01/2012 23:02, Wayne Watson a ?crit :
>> OK, how do I untar it Win7? Ah, good fortune. I have MinGW (gfortran)
>> that has a linux-like shell, and has tar.
>
> Any decent archive manager such as 7zip works also with tar/gz/bz2 files
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> http://mail.scipy.org/mailman/listinfo/astropy
>

-- 
            Wayne Watson (Watson Adventures, Prop., Nevada City, CA)

              (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
               Obz Site:  39? 15' 7" N, 121? 2' 32" W, 2700 feet

                      In 2904 there will be 5 solar eclipses.
                      On July 16, 2185 the longest solar
                      eclipse inf 5k years will occur, 7 min.

                     Web Page:<www.speckledwithstars.net/>




From embray at stsci.edu  Mon Jan 30 12:50:20 2012
From: embray at stsci.edu (Erik Bray)
Date: Mon, 30 Jan 2012 12:50:20 -0500
Subject: [AstroPy] [ANN] PyFITS 3.0.5 Released
Message-ID: <4F26D85C.3010501@stsci.edu>

I'm happy to announce the release of PyFITS 3.0.5.  This is a bug fix 
release--most of the issues fixed are relatively uncommon corner cases, 
though there is one fix that should greatly improve performance of 
reading tables containing string columns.

See http://www.stsci.edu/resources/software_hardware/pyfits/Download for 
download and installation information.

See http://www.stsci.edu/resources/software_hardware/pyfits/release for 
the full changelog.

Thanks for your continued interest in PyFITS.

Erik