From rij at stsci.edu Fri Apr 1 14:20:45 2005 From: rij at stsci.edu (Robert Jedrzejewski) Date: Fri, 01 Apr 2005 14:20:45 -0500 Subject: [AstroPy] STSDAS v3.3.1 patch and stsci_python v2.1 now available Message-ID: <424D9F0D.9050003@stsci.edu> ************************************************* STSDAS v3.3.1 and STSCI_PYTHON v2.1 NOW AVAILABLE ************************************************* The Science Software Project of the Space Telescope Science Institute is pleased to announce the availability of version 3.3.1 of the Space Telescope Science Data Analysis Software (STSDAS). This is a patch release that includes changes to the STIS package and changes to the dither package related to MultiDrizzle. This version must be installed on top of STSDAS v3.3. STSDAS includes some Python-based tasks; running these requires the STScI Python Libraries to be installed (all the non-Python tasks can be used in the traditional way and do not require Python or the STScI Python libraries). These tasks can only be run from PyRAF using standard IRAF CL task syntax, or within Python scripts using Python syntax. The Science Software Project of STScI is also pleased to announce the release of version 2.1 of STSCI_PYTHON. The primary change in this version is the release of new versions of PyDrizzle and MultiDrizzle, as well as upgrades to all of the included packages. This means that a full installation is required to ensure that there are no dependency problems. Use of the Python tasks in STSDAS 3.3.1 requires upgrading to this version of STSCI_PYTHON. WHERE TO OBTAIN THIS SOFTWARE STSDAS v3.3.1 can be downloaded from the STSDAS web site http://www.stsci.edu/resources/software_hardware/stsdas/download Installation instructions are available on the web site. Precompiled binaries also exist for some of the ports supported by NOAO, including Sun Solaris, RedHat Linux and Mac OS X. STSCI_PYTHON v2.1 can be downloaded from the web site http://www.stsci.edu/resources/software_hardware/pyraf/stsci_python/current/download This web site also includes installation instructions. Please contact us through e-mail (help at stsci.edu) or by telephone at (410) 338-1082 if you have problems with these releases. From stephen.walton at csun.edu Sun Apr 3 23:47:31 2005 From: stephen.walton at csun.edu (Stephen Walton) Date: Sun, 03 Apr 2005 20:47:31 -0700 Subject: [AstroPy] Re: HIERARCH In-Reply-To: <6da6b67843c97c520151bde81afc17eb@stsci.edu> References: <200503310124.j2V1OqCp016968@oobleck.astro.cornell.edu> <0f5b52f88fdc081c6c493cf92178f4e7@stsci.edu> <200503311445.j2VEjwqI024313@oobleck.astro.cornell.edu> <1112285271.9834.14.camel@bit.localdomain> <6da6b67843c97c520151bde81afc17eb@stsci.edu> Message-ID: <1112586451.12093.5.camel@localhost.localdomain> FWIW, CFITSIO's handling of HIERARCH is documented at http://heasarc.gsfc.nasa.gov/docs/software/fitsio/c/c_user/node112.html As I read it, a new header keyword is checked for adherence to the FITS standard (8 characters or less, alphanumerics plus underscore only). If it does not comply, then HIERARCH is prepended to the keyword and it is written accordingly. The only time an exception is raised is if the keyword/value pair doesn't fit in 80 characters. Steve From stephen.walton at csun.edu Sun Apr 3 23:50:54 2005 From: stephen.walton at csun.edu (Stephen Walton) Date: Sun, 03 Apr 2005 20:50:54 -0700 Subject: [AstroPy] Draft specification for PyFITS functional interface In-Reply-To: <424C1024.3030104@stsci.edu> References: <200503302236.j2UMaLr09908@laplace.astro.cornell.edu> <424C1024.3030104@stsci.edu> Message-ID: <1112586654.12093.8.camel@localhost.localdomain> On Thu, 2005-03-31 at 09:58 -0500, Victoria G. Laidler wrote: > Honestly, people who are worried about namespace pollution *shouldn't use* > > from foo import *. > > Of course we all get lazy sometimes, Some of us are also trying to avoid carpal tunnel syndrome...I usually do stuff like "import Numeric as N". From abeelen at mpifr-bonn.mpg.de Wed Apr 20 09:53:55 2005 From: abeelen at mpifr-bonn.mpg.de (Alexandre Beelen) Date: Wed, 20 Apr 2005 15:53:55 +0200 Subject: [AstroPy] AstroLibWCS & AstroLibCoords Message-ID: <1114005235.19916.25.camel@localhost.localdomain> Hi, I am part of the BoA [1] project which aimed to write a flexible software to reduce data coming from various bolometers arrays. The core of this software is written in python, which some extension in fortran for the intensive computation task. I started to implement a somehow light WCS system to deals with map coordinates. Before going any further, I would like to know what are the status, and if it was possible to access and use, the AstroLibWCS & AstroLibCoords library. In case where a few modules are present would it be also possible to participate to their development ? I was also thinking to wrap the WCSLIB [2] using swig or something else, does any of you tried this before ? a. [1] http://www.openboa.de (old not really updated web site) [2] http://www.atnf.csiro.au/people/mcalabre/WCS/ From perry at stsci.edu Wed Apr 20 10:42:13 2005 From: perry at stsci.edu (Perry Greenfield) Date: Wed, 20 Apr 2005 10:42:13 -0400 Subject: [AstroPy] AstroLibWCS & AstroLibCoords In-Reply-To: <1114005235.19916.25.camel@localhost.localdomain> References: <1114005235.19916.25.camel@localhost.localdomain> Message-ID: <6a36e5a0a0e27f771f76822b1189ae02@stsci.edu> On Apr 20, 2005, at 9:53 AM, Alexandre Beelen wrote: > Hi, > > I am part of the BoA [1] project which aimed to write a flexible > software to reduce data coming from various bolometers arrays. The core > of this software is written in python, which some extension in fortran > for the intensive computation task. I started to implement a somehow > light WCS system to deals with map coordinates. > > Before going any further, I would like to know what are the status, and > if it was possible to access and use, the AstroLibWCS & AstroLibCoords > library. In case where a few modules are present would it be also > possible to participate to their development ? > We did have someone working on this. That work will be put on hold for a month or so because of another project. I'm waiting for the Enthought people to give us subversion privileges so we can start putting early versions on their subversion repository (I was told that we would get the privileges any hour now). If you want to look at what we've done I don't have a problem sending what we have to you (some of the interfaces may change though since it is still under development) > I was also thinking to wrap the WCSLIB [2] using swig or something > else, > does any of you tried this before ? > We've done that too. If you are interested we can make the wrappers available. We decided to see if was just as easy to re-implement and use wcslib for test comparisons. (And it turns out, that much of the complexity of handling FITS WCS headers is not really handled by wcslib; it basically presumes you have extracted the necessary set of keywords for its use (if I recall correctly). > Perry From stephen.walton at csun.edu Thu Apr 21 10:25:42 2005 From: stephen.walton at csun.edu (Stephen Walton) Date: Thu, 21 Apr 2005 07:25:42 -0700 Subject: [AstroPy] AstroLibWCS & AstroLibCoords In-Reply-To: <6a36e5a0a0e27f771f76822b1189ae02@stsci.edu> References: <1114005235.19916.25.camel@localhost.localdomain> <6a36e5a0a0e27f771f76822b1189ae02@stsci.edu> Message-ID: <4267B7E6.3040004@csun.edu> Perry Greenfield wrote: > On Apr 20, 2005, at 9:53 AM, Alexandre Beelen wrote: > >> I was also thinking to wrap the WCSLIB [2] using swig or something else, >> does any of you tried this before ? >> > We've done that too. If you are interested we can make the wrappers > available. We decided to see if was just as easy to re-implement and > use wcslib for test comparisons. (And it turns out, that much of the > complexity of handling FITS WCS headers is not really handled by > wcslib; it basically presumes you have extracted the necessary set of > keywords for its use (if I recall correctly). This is not as true as it used to be. From a March 18 posting by William Pence to the fitswcs discussion group: >1. call the fits_hdr2str routine in CFITSIO to read the image header >keywords into a long character string variable. > >2. pass this string variable to the wscpih routine in WCSLIB, which then >parses all the WCS keywords and creates internal structures that will be >used in subsequent transforms between pixel and world coordinates. > >3. call the wcsp2s routine in WCSLIB to convert any input pixel coordinate >into world coordinates. The complete archived message is at http://listmgr.cv.nrao.edu/pipermail/fitswcs/2005-March/000334.html Steve Walton From laidler at stsci.edu Fri Apr 29 13:00:39 2005 From: laidler at stsci.edu (laidler at stsci.edu) Date: Fri, 29 Apr 2005 13:00:39 -0400 Subject: [AstroPy] AstroLibCoords wiki discussion Message-ID: <31883098.f4b093aa.81a0700@comet.stsci.edu> Hi folks, We at STScI are starting to work more actively on developing a coordinate object for the Python AstroLib effort. (Recall that AstroLib is intended to supply something like the IDL "astron" library functionality.) Please check out the newly active wiki page, http://www.scipy.org/wikis/topical_software/AstroLibCoordsHome and post your comments, questions, and suggestions on the wiki. We're presently working on clarifying the scope and functionality of the Coords object, as opposed to other objects or libraries that it may collaborate with, and developing some use cases that will identify and exercise the desired functionality. cheers, Vicki Laidler