From aldcroft at head.cfa.harvard.edu Tue Oct 4 20:51:49 2011 From: aldcroft at head.cfa.harvard.edu (Tom Aldcroft) Date: Tue, 4 Oct 2011 20:51:49 -0400 Subject: [AstroPy] asciitable 0.8.0: fixed width tables Message-ID: I'd like to announce the availability of asciitable 0.8.0. This release adds full support for reading and writing fixed-width tables. Please see the Fixed-width Gallery for the myriad of table formats this provides: http://cxc.harvard.edu/contrib/asciitable/fixed_width_gallery.html As always you can get the new version on PyPI or https://github.com/taldcroft/asciitable. Cheers, Tom Aldcroft From erwin at mpe.mpg.de Fri Oct 7 08:07:54 2011 From: erwin at mpe.mpg.de (Peter Erwin) Date: Fri, 7 Oct 2011 14:07:54 +0200 Subject: [AstroPy] Updated telarchive (v1.6.5) + fetchsdss Message-ID: <2141848F-2A86-43AF-BF2B-57A766B335F4@mpe.mpg.de> Hi, This is an announcement of an updated version (1.6.5) of my quick-and- dirty, Python-based telescope archive search tool, available here: http://www.mpe.mpg.de/~erwin/code/ (A short summary of what it does is appended below.) Fixes: - Restored coordinate lookup via SIMBAD (broken due to changes in SIMBAD output HTML) - Restored searches for Spitzer observations - Restored searches for SMOKA (Subaru and other Japanese telescopes) observations; includes latest instruments (FMOS and HiCIAO on Subaru) - Switched HST archival searches from ESO/ST-ECF to STScI - Various minor bug fixes [previous summary, updated:] "Telarchive" is a command-line program which simplifies searching various public telescope archives to see if they might have data on a particular astronomical object or part of the sky. This includes the HST and general MAST archive, as well as the ESO, UKIRT, CFHT, and AAT ground-based archives, and imaging data from Data Release 7 (DR7) of the Sloan Digital Sky Survey. The NOAO Science Archive is also included, though it has very little publically available data at this point. Recent additions are Spitzer, SMOKA (the archive for Subaru and several older Japanese telescopes), and the Gemini Science Archive. The Isaac Newton Group Archive is also searched, but only for data from 2001 or earlier (newer data is handled by the new archive interface, which is currently not usable by this program). The program won't *get* the data for you, of course (but see "fetchsdss" for SDSS images), or even tell you very much about it -- for that, you still need to visit the individual archive web pages. But it will save you lots of clicking and typing in web-page forms if you just want to find out if there is *any* data available. An example (searching within a 2-arcminute box centered on the planetary nebula NGC 7027; searching on coordinates directly is also possible): $ telarchive "ngc 7027" 2.0 SIMBAD (Simbad 4, France): Found object coordinates: RA = 21 07 01.593, Dec = +42 14 10.18 Searching archives for ngc 7027 (RA = 21 07 01.593, dec = +42 14 10.18), with search box = 2.0 arcmin... Sloan Digital Sky Survey (DR7) Coordinate-Search Server: No data found. NOAO Science Archive: No data found. AAT Archive: No data found. ESO Archive: No data found. Spitzer Archive: Data exists! (13 records found) 1 mipssed, 2 iracmap, 3 mipsphot, 7 irsstare Multimission Archive at STScI (MAST): Data exists! (50 observations found) COPERNICUS (1); FUSE (2); GALEX (11); IUE (36) UKIRT Archive: Data exists! (943 observations found) ING Archive (old interface): Data exists! (577 observations found) 143 images, 391 spectra, 43 unclassified JKT -- RBS (1), FWHL (2), AGBX (102); INT -- WFC (9), PFCU (30), IDS (66), MES (17), FOS_1 (10); WHT -- TAURUS_2 (5), unknown (43), ISIS_BLUE_ARM (159), UES (58), ISIS_RED_ARM (75) HST archive: Data exists! (109 records found) 13 FOS, 26 NICMOS, 25 WFPC, 18 WFPC2, 3 FOC, 24 STIS Gemini Science Archive: Data exists! (252 observations found) 162 long-slit, 45 imaging, 45 IFU michelle (9), NIRI (198), GMOS-N (45) CFHT Archive: Data exists! (213 observations found) BEAR (200), GECKO (4), AOBVIS (3), AOBIR (6) SMOKA (Subaru Mitaka Okayama Kiso Archive): Data exists! (1407 observations found) Subaru -- HDS (14), Subaru -- OHS/CISCO (38), Subaru -- IRCS (363), Subaru -- COMICS (955), Kiso -- 1k CCD (3), Okayama -- HIDES (31), Okayama -- SNG (3) It's available as a gzipped tar file here: http://www.mpe.mpg.de/~erwin/code/ There are installation instructions/suggestions in the README file. (And feel free to email with questions or suggestions about it!) cheers, Peter ============================================================= Peter Erwin Max-Planck-Insitute for Extraterrestrial erwin at mpe.mpg.de Physics, Giessenbachstrasse tel. +49 (0)89 30000 3695 85748 Garching, Germany fax +49 (0)89 30000 3495 http://www.mpe.mpg.de/~erwin From superluminique at gmail.com Sat Oct 8 02:52:22 2011 From: superluminique at gmail.com (Rene Breton) Date: Sat, 8 Oct 2011 02:52:22 -0400 Subject: [AstroPy] patch for pywcs Message-ID: Hi, I don't know if Michael Droettboom is still the maintainer of pywcs but I have a patch to submit for the next release. There have been major changes to pyfits 3.x compared to 2.x and hence pywcs fails to export to header properly (pywcs.WCS.to_header). I have fixed the problem. Currently, it requires a "try... except" because I haven't found an elegant way to make it compatible with both 2.x and 3.x. When pywcs moves to requiring pyfits >3.x then the exception clause could be removed. At the same time, I've also remove the header.has_key and replaced them for "key in header" as the header.has_key spits out a DeprecationWarning. The patch is attached. Cheers, Rene -------------- next part -------------- A non-text attachment was scrubbed... Name: patch.diff Type: application/octet-stream Size: 2887 bytes Desc: not available URL: From embray at stsci.edu Mon Oct 10 07:36:04 2011 From: embray at stsci.edu (Erik Bray) Date: Mon, 10 Oct 2011 07:36:04 -0400 Subject: [AstroPy] patch for pywcs In-Reply-To: References: Message-ID: <4E92D8A4.5070805@stsci.edu> Hi, I'm pretty sure Mike is still the pywcs maintainer, but as the pyfits maintainer I can say it looks good to me. The 'fromstring' portion of your patch is already fixed in pywcs's trunk (it checks the pyfits version with pyfits.__version__ by the way). But the all the has_keys still need to be fixed. That one's a bit surprising since I thought I grepped most of our code base for that and removed them, but I guess a few slipped through the cracks. Thanks! Erik On 10/08/2011 02:52 AM, Rene Breton wrote: > Hi, > > I don't know if Michael Droettboom is still the maintainer of pywcs but > I have a patch to submit for the next release. There have been major > changes to pyfits 3.x compared to 2.x and hence pywcs fails to export to > header properly (pywcs.WCS.to_header). I have fixed the problem. > Currently, it requires a "try... except" because I haven't found an > elegant way to make it compatible with both 2.x and 3.x. When pywcs > moves to requiring pyfits >3.x then the exception clause could be removed. > > At the same time, I've also remove the header.has_key and replaced them > for "key in header" as the header.has_key spits out a DeprecationWarning. > > The patch is attached. > > Cheers, > > > Rene > _______________________________________________ > AstroPy mailing list > AstroPy at scipy.org > http://mail.scipy.org/mailman/listinfo/astropy From mdroe at stsci.edu Mon Oct 10 10:19:24 2011 From: mdroe at stsci.edu (Michael Droettboom) Date: Mon, 10 Oct 2011 10:19:24 -0400 Subject: [AstroPy] patch for pywcs In-Reply-To: <4E92D8A4.5070805@stsci.edu> References: <4E92D8A4.5070805@stsci.edu> Message-ID: <4E92FEEC.2010807@stsci.edu> Thanks for the report. It looks good. As Erik said, the pyfits 3.x compatibility change is already there, but I've gone ahead and put the "has_key"-related changes in the SVN repository. Mike On 10/10/2011 07:36 AM, Erik Bray wrote: > Hi, > > I'm pretty sure Mike is still the pywcs maintainer, but as the pyfits > maintainer I can say it looks good to me. The 'fromstring' portion of > your patch is already fixed in pywcs's trunk (it checks the pyfits > version with pyfits.__version__ by the way). > > But the all the has_keys still need to be fixed. That one's a bit > surprising since I thought I grepped most of our code base for that and > removed them, but I guess a few slipped through the cracks. > > Thanks! > > Erik > > On 10/08/2011 02:52 AM, Rene Breton wrote: >> Hi, >> >> I don't know if Michael Droettboom is still the maintainer of pywcs but >> I have a patch to submit for the next release. There have been major >> changes to pyfits 3.x compared to 2.x and hence pywcs fails to export to >> header properly (pywcs.WCS.to_header). I have fixed the problem. >> Currently, it requires a "try... except" because I haven't found an >> elegant way to make it compatible with both 2.x and 3.x. When pywcs >> moves to requiring pyfits>3.x then the exception clause could be removed. >> >> At the same time, I've also remove the header.has_key and replaced them >> for "key in header" as the header.has_key spits out a DeprecationWarning. >> >> The patch is attached. >> >> Cheers, >> >> >> Rene >> _______________________________________________ >> 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 thomas.robitaille at gmail.com Mon Oct 17 17:18:39 2011 From: thomas.robitaille at gmail.com (Thomas Robitaille) Date: Mon, 17 Oct 2011 17:18:39 -0400 Subject: [AstroPy] AstroPy CfA workshop summary Message-ID: Hi everyone, The first AstroPy development coordination meeting took place last week at the CfA in Cambridge, MA, and was attended by 20 participants (16 local and 4 remote). We made significant progress on all fronts. A detailed agenda and minutes are available here: https://github.com/astropy/astropy/wiki/CfAMeeting2011Agenda https://github.com/astropy/astropy/wiki/CfAMeeting2011Minutes so if you are interested in all the decisions that were made, and the motivation behind these, I encourage you to read through these! Below I summarize some of the main decisions: * Discussions relating to development of the AstroPy package will now take place on the astropy-dev at googlegroups.com mailing list. If you are interesting in the astropy development, please sign up for this mailing list, either at: http://groups.google.com/group/astropy-dev or by sending an empty email to: astropy-dev+subscribe at googlegroups.com You can use the web interface to catch up with any discussions you might have missed. * We decided on initial areas of development. These areas are listed below, along with names in square brackets which indicate participants who volunteered to (at least temporarily) coordinate efforts in these areas in the short term. The aim was to guarantee that leaving the workshop, we had at least one person who is happy to coordinate getting things started. - astropy.constants (with cgs and si sub-modules) [Erik Tollerud, Thomas Robitaille] - astropy.units - unit conversion routines [Perry Greenfield] - astropy.io.fits - FITS file I/O [Erik Bray] - astropy.io.vo - VO tables and communication (both technically I/O) [Mike Droettboom] - astropy.table - a base class for tables (and registry facility for read/write functions) [Tom Aldcroft and Thomas Robitaille] - astropy.wcs - WCS transformations [Mike Droettboom and Nadia Dencheva] - astropy.coords - coordinate transformations (ultimately including Alt/Az type conversions that depend on time) [Erik Tollerud] - astropy.time - handling of astronomical times (e.g. julian dates, etc.) [Wolfgang K. and Erik Tollerud] - astropy.nddata - arbitrary n-dimensional datasets with WCS [Steve Crawford] - astropy.image - image-specific routines [Thomas Robitaille] - astropy.spectrum - spectrum-specific routines [Wolfgang Kerzendorf, Erik Tollerud, Adam Ginsburg] The coordinators will get in touch with people listed on https://github.com/astropy/astropy/wiki/Developers to coordinate things. You are also free to contact these people directly to let them know of your interests in contributing. * AstroPy will be released under a 3-clause BSD license (https://github.com/astropy/astropy/blob/master/licenses/LICENSE.rst) * The py.test testing framework will be used for developing tests (instructions and guidelines for testing will be uploaded to the http://www.astropy.org website shortly). * The main aspects of the core package layout were finalized. * API decisions regarding low-level data objects (NDData, Spectral/Spectrum1D/Spectrum2D, Image, etc.) were made (details available in the minutes). * We plan to hold a logo/website design competition, and will send details out to this mailing list shortly! Additionally, we held a coding sprint on Friday, and made significant progress in certain areas. You can follow the progress at https://github.com/astropy/astropy. Please do not hesitate if you would like clarifications or have any questions! Thomas From thomas.robitaille at gmail.com Mon Oct 17 17:20:56 2011 From: thomas.robitaille at gmail.com (Thomas Robitaille) Date: Mon, 17 Oct 2011 17:20:56 -0400 Subject: [AstroPy] IMPORTANT: developer mailing list Message-ID: Hi everyone, I just want to repeat one of the points I made in my previous email, which is that discussions relating to development of the AstroPy package will now take place on the astropy-dev at googlegroups.com mailing list. If you are interesting in the astropy development, please sign up for this mailing list, either at: http://groups.google.com/group/astropy-dev or by sending an empty email to: astropy-dev+subscribe at googlegroups.com You can use the web interface to catch up with any discussions you might have missed. Cheers, Thomas From kellecruz at gmail.com Mon Oct 17 18:21:12 2011 From: kellecruz at gmail.com (Kelle Cruz) Date: Mon, 17 Oct 2011 18:21:12 -0400 Subject: [AstroPy] AstroPy CfA workshop summary In-Reply-To: References: Message-ID: I'm so happy this meeting happened! Did ya'll talk about when the next one will be? or the necessary frequency of them? Also, I think that the larger astro community should be informed of these efforts and progress. Could someone generate an update from the meeting that's readable by a more general audience. It can be posted to Astropython, Tom (or I) can post it to AstroBetter...it can also be posted to the Astronomers FB group, and maybe even go out as an announcement in the AAS Newsletter. We want the community to know that there is coordinated effort going into Python to further facilitate the transition from IDL/IRAF. kelle On Mon, Oct 17, 2011 at 5:18 PM, Thomas Robitaille < thomas.robitaille at gmail.com> wrote: > Hi everyone, > > The first AstroPy development coordination meeting took place last > week at the CfA in Cambridge, MA, and was attended by 20 participants > (16 local and 4 remote). We made significant progress on all fronts. A > detailed agenda and minutes are available here: > > https://github.com/astropy/astropy/wiki/CfAMeeting2011Agenda > https://github.com/astropy/astropy/wiki/CfAMeeting2011Minutes > > so if you are interested in all the decisions that were made, and the > motivation behind these, I encourage you to read through these! > > Below I summarize some of the main decisions: > > * Discussions relating to development of the AstroPy package will now > take place on the astropy-dev at googlegroups.com mailing list. If you > are interesting in the astropy development, please sign up for this > mailing list, either at: > > http://groups.google.com/group/astropy-dev > > or by sending an empty email to: > > astropy-dev+subscribe at googlegroups.com > > You can use the web interface to catch up with any discussions you > might have missed. > > * We decided on initial areas of development. These areas are listed > below, along with names in square brackets which indicate participants > who volunteered to (at least temporarily) coordinate efforts in these > areas in the short term. The aim was to guarantee that leaving the > workshop, we had at least one person who is happy to coordinate > getting things started. > > - astropy.constants (with cgs and si sub-modules) [Erik Tollerud, > Thomas Robitaille] > - astropy.units - unit conversion routines [Perry Greenfield] > - astropy.io.fits - FITS file I/O [Erik Bray] > - astropy.io.vo - VO tables and communication (both technically I/O) > [Mike Droettboom] > - astropy.table - a base class for tables (and registry facility for > read/write functions) [Tom Aldcroft and Thomas Robitaille] > - astropy.wcs - WCS transformations [Mike Droettboom and Nadia Dencheva] > - astropy.coords - coordinate transformations (ultimately including > Alt/Az type conversions that depend on time) [Erik Tollerud] > - astropy.time - handling of astronomical times (e.g. julian dates, > etc.) [Wolfgang K. and Erik Tollerud] > - astropy.nddata - arbitrary n-dimensional datasets with WCS [Steve > Crawford] > - astropy.image - image-specific routines [Thomas Robitaille] > - astropy.spectrum - spectrum-specific routines [Wolfgang Kerzendorf, > Erik Tollerud, Adam Ginsburg] > > The coordinators will get in touch with people listed on > > https://github.com/astropy/astropy/wiki/Developers > > to coordinate things. You are also free to contact these people > directly to let them know of your interests in contributing. > > * AstroPy will be released under a 3-clause BSD license > (https://github.com/astropy/astropy/blob/master/licenses/LICENSE.rst) > > * The py.test testing framework will be used for developing tests > (instructions and guidelines for testing will be uploaded to the > http://www.astropy.org website shortly). > > * The main aspects of the core package layout were finalized. > > * API decisions regarding low-level data objects (NDData, > Spectral/Spectrum1D/Spectrum2D, Image, etc.) were made (details > available in the minutes). > > * We plan to hold a logo/website design competition, and will send > details out to this mailing list shortly! > > Additionally, we held a coding sprint on Friday, and made significant > progress in certain areas. You can follow the progress at > https://github.com/astropy/astropy. > > Please do not hesitate if you would like clarifications or have any > questions! > > Thomas > _______________________________________________ > AstroPy mailing list > AstroPy at scipy.org > http://mail.scipy.org/mailman/listinfo/astropy > -- Kelle Cruz, PhD ? http://kellecruz.com/ 917.725.1334 ? Hunter ext: 16486 ? AMNH ext: 3404 -------------- next part -------------- An HTML attachment was scrubbed... URL: From erik.tollerud at gmail.com Tue Oct 18 13:58:16 2011 From: erik.tollerud at gmail.com (Erik Tollerud) Date: Tue, 18 Oct 2011 13:58:16 -0400 Subject: [AstroPy] AstroPy CfA workshop summary In-Reply-To: References: Message-ID: > I'm so happy this meeting happened! Did ya'll talk about when the next one > will be? or the necessary frequency of them? There was some discussion - we definitely thought a spring meeting this year would be a good idea to keep up the momentum, although no definitive decision was reached. Location was not definitively decided, although STScI seems like a logical choice. The other possibility might be to try for a location on the west coast, to try to pull in more people from there. Depending on how the development pace proceeds, we thought at least once per year would be good, and perhaps twice. We also discussed having a AAS session and concluded we probably didn't want to do that for this winter, but possibly next summer or next winter. If there's enough interest, we could hold some sort of informal AAS meeting this winter (not that many of those who were present last week will be at AAS, but I will, so I'm happy to meet with a group if desired). > Also, I think that the larger astro community should be informed of these > efforts and progress. Could someone generate an update from the meeting > that's readable by a more general audience. It can be posted to Astropython, > Tom (or I) can post it to AstroBetter...it can also be posted to the > Astronomers FB group, and maybe even go out as an announcement in the AAS > Newsletter. > We want the community to know that there is coordinated effort going into > Python to further facilitate the transition from IDL/IRAF. We discussed this a little, and are a bit wary of making big announcements until we have at least some sort of package that can actually be installed and provide some functionality. Michael Droettboom and Erik Bray are going to move PyWCS and PyFITS into astropy, and we have at least initial scaffolding for some of the modules that can be put in place soon. The tentative plan would be for something like a "pre-release" this winter, to give an opportunity to start battle-testing it by early adopters, and then a first actual release (with associated "PR campaign") next year. Having said this, you have a good point that it's worthwhile to at least start spreading the word that something is happening, even if the package itself isn't quite ready. I think we'd want to hold off on a AAS type of announcement, but a post on AstroBetter and similar is definitely a good idea. -- Erik Tollerud > On Mon, Oct 17, 2011 at 5:18 PM, Thomas Robitaille > wrote: >> >> Hi everyone, >> >> The first AstroPy development coordination meeting took place last >> week at the CfA in Cambridge, MA, and was attended by 20 participants >> (16 local and 4 remote). We made significant progress on all fronts. A >> detailed agenda and minutes are available here: >> >> https://github.com/astropy/astropy/wiki/CfAMeeting2011Agenda >> https://github.com/astropy/astropy/wiki/CfAMeeting2011Minutes >> >> so if you are interested in all the decisions that were made, and the >> motivation behind these, I encourage you to read through these! >> >> Below I summarize some of the main decisions: >> >> * Discussions relating to development of the AstroPy package will now >> take place on the astropy-dev at googlegroups.com mailing list. If you >> are interesting in the astropy development, please sign up for this >> mailing list, either at: >> >> http://groups.google.com/group/astropy-dev >> >> or by sending an empty email to: >> >> astropy-dev+subscribe at googlegroups.com >> >> You can use the web interface to catch up with any discussions you >> might have missed. >> >> * We decided on initial areas of development. These areas are listed >> below, along with names in square brackets which indicate participants >> who volunteered to (at least temporarily) coordinate efforts in these >> areas in the short term. The aim was to guarantee that leaving the >> workshop, we had at least one person who is happy to coordinate >> getting things started. >> >> - astropy.constants (with cgs and si sub-modules) [Erik Tollerud, >> Thomas Robitaille] >> - astropy.units - unit conversion routines [Perry Greenfield] >> - astropy.io.fits - FITS file I/O [Erik Bray] >> - astropy.io.vo - VO tables and communication (both technically I/O) >> [Mike Droettboom] >> - astropy.table - a base class for tables (and registry facility for >> read/write functions) [Tom Aldcroft and Thomas Robitaille] >> - astropy.wcs - WCS transformations [Mike Droettboom and Nadia Dencheva] >> - astropy.coords - coordinate transformations (ultimately including >> Alt/Az type conversions that depend on time) [Erik Tollerud] >> - astropy.time - handling of astronomical times (e.g. julian dates, >> etc.) [Wolfgang K. and Erik Tollerud] >> - astropy.nddata - arbitrary n-dimensional datasets with WCS [Steve >> Crawford] >> - astropy.image - image-specific routines [Thomas Robitaille] >> - astropy.spectrum - spectrum-specific routines [Wolfgang Kerzendorf, >> Erik Tollerud, Adam Ginsburg] >> >> The coordinators will get in touch with people listed on >> >> https://github.com/astropy/astropy/wiki/Developers >> >> to coordinate things. You are also free to contact these people >> directly to let them know of your interests in contributing. >> >> * AstroPy will be released under a 3-clause BSD license >> (https://github.com/astropy/astropy/blob/master/licenses/LICENSE.rst) >> >> * The py.test testing framework will be used for developing tests >> (instructions and guidelines for testing will be uploaded to the >> http://www.astropy.org website shortly). >> >> * The main aspects of the core package layout were finalized. >> >> * API decisions regarding low-level data objects (NDData, >> Spectral/Spectrum1D/Spectrum2D, Image, etc.) were made (details >> available in the minutes). >> >> * We plan to hold a logo/website design competition, and will send >> details out to this mailing list shortly! >> >> Additionally, we held a coding sprint on Friday, and made significant >> progress in certain areas. You can follow the progress at >> https://github.com/astropy/astropy. >> >> Please do not hesitate if you would like clarifications or have any >> questions! >> >> Thomas >> _______________________________________________ >> AstroPy mailing list >> AstroPy at scipy.org >> http://mail.scipy.org/mailman/listinfo/astropy > > > > -- > Kelle Cruz, PhD ??http://kellecruz.com/ > 917.725.1334 ??Hunter ext: 16486 ? AMNH ext: 3404 > > _______________________________________________ > AstroPy mailing list > AstroPy at scipy.org > http://mail.scipy.org/mailman/listinfo/astropy > > From oneaufs at gmail.com Wed Oct 19 11:42:43 2011 From: oneaufs at gmail.com (Prasanth) Date: Wed, 19 Oct 2011 21:12:43 +0530 Subject: [AstroPy] IMPORTANT: developer mailing list In-Reply-To: References: Message-ID: Hello, In addition to the Google groups discussions, Github pull request discussions are also good place to check the progress of various proposed additions. You may have to create a Github account and "watch" the project to get news feeds of the discussion. Prasanth On Tue, Oct 18, 2011 at 2:50 AM, Thomas Robitaille < thomas.robitaille at gmail.com> wrote: > Hi everyone, > > I just want to repeat one of the points I made in my previous email, > which is that discussions relating to development of the AstroPy > package will now take place on the astropy-dev at googlegroups.com > mailing list. If you are interesting in the astropy development, > please sign up for this mailing list, either at: > > http://groups.google.com/group/astropy-dev > > or by sending an empty email to: > > astropy-dev+subscribe at googlegroups.com > > You can use the web interface to catch up with any discussions you > might have missed. > > Cheers, > Thomas > _______________________________________________ > AstroPy mailing list > AstroPy at scipy.org > http://mail.scipy.org/mailman/listinfo/astropy > -------------- next part -------------- An HTML attachment was scrubbed... URL: