From perry at stsci.edu Thu Feb 24 16:46:11 2005 From: perry at stsci.edu (Perry Greenfield) Date: Thu, 24 Feb 2005 16:46:11 -0500 Subject: [AstroPy] Comments sought on WCS library Message-ID: We (STScI) have started work on implementing a WCS library. I've put some thoughts about the form that library should take (its functionality and user interface) on the astrolib wiki. We'd be interested in any feedback or comments about what features and interface a WCS library should have. http://www.scipy.org/wikis/topical_software/AstroLibWCS Perry Greenfield From mkuemmel at eso.org Fri Feb 25 10:17:10 2005 From: mkuemmel at eso.org (Martin Kuemmel) Date: Fri, 25 Feb 2005 16:17:10 +0100 Subject: [AstroPy] Design document for the AstroAsciiData library is online In-Reply-To: References: Message-ID: <200502251517.j1PFHB205622@serapis.hq.eso.org> In collaboration with Jonas Haase the work on the AstroAsciiData library has started. We put a design document on the astrolib wiki. The content of this documents descibes which kind of ASCII tables could/should be handled, describes a possible object structure and gives some examples of user applications. Any feedback, comments or suggestions are welcome. http://www.scipy.org/wikis/topical_software/AstroAsciiData Martin Kuemmel From Laurent.LeGuillou at ster.kuleuven.ac.be Fri Feb 25 11:52:19 2005 From: Laurent.LeGuillou at ster.kuleuven.ac.be (Laurent LE GUILLOU) Date: Fri, 25 Feb 2005 16:52:19 +0000 Subject: [AstroPy] SExtractor wrapper Message-ID: <421F57C3.2040805@ster.kuleuven.ac.be> Hi, I have written a small wrapper for SExtractor. It consists of 2 modules : sexcatalog.py -> Provides a class to read SExtractor ASCII catalogs as list of dictionaries ; sextractor.py -> A full wrapper, to manage SExtractor configuration (default.{sex,conv,params,...}) on the fly, run sextractor and return the resulting catalog as a list of dictionaries. Perhaps it may be useful for someone else. I don't know if this code is clean enough to be included somewhere in the Python Astro library you are working on. Cheers, Laurent ----------------------------------------------------------------------- Laurent LE GUILLOU Tel +34 922 425 412 Laurent.LeGuillou at ster.kuleuven.ac.be Fax +34 922 425 475 Mercator Telescope K.U. Leuven Sea Level Office - P.O. Box 474 Instituut voor Sterrenkunde Calle Alvarez de Abreu 70 Celestijnenlaan 200 B E-38700 Santa Cruz de La Palma B-3001 Leuven Spain Belgium -------------- next part -------------- A non-text attachment was scrubbed... Name: sexcatalog.py Type: application/x-python Size: 31334 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: sextractor.py Type: application/x-python Size: 17669 bytes Desc: not available URL: From perry at stsci.edu Fri Feb 25 12:41:57 2005 From: perry at stsci.edu (Perry Greenfield) Date: Fri, 25 Feb 2005 12:41:57 -0500 Subject: [AstroPy] Design document for the AstroAsciiData library is online In-Reply-To: <200502251517.j1PFHB205622@serapis.hq.eso.org> References: <200502251517.j1PFHB205622@serapis.hq.eso.org> Message-ID: <4a11b249e9cbff1a13838569e51e5889@stsci.edu> On Feb 25, 2005, at 10:17 AM, Martin Kuemmel wrote: > > In collaboration with Jonas Haase the work on the > AstroAsciiData library has started. We put a design document > on the astrolib wiki. The content of this documents descibes > which kind of ASCII tables could/should be handled, > describes a possible object structure and gives some > examples of user applications. > Any feedback, comments or suggestions are welcome. > > http://www.scipy.org/wikis/topical_software/AstroAsciiData > I think this a great idea, and I particularly appreciate airing the details on the wiki page. It's a very good first step. I've place some comments, questions, and suggestions on the wiki page regarding the design document. Perry From William.T.Bridgman.1 at gsfc.nasa.gov Fri Feb 25 14:07:19 2005 From: William.T.Bridgman.1 at gsfc.nasa.gov (W.T. Bridgman) Date: Fri, 25 Feb 2005 14:07:19 -0500 Subject: [AstroPy] Design document for the AstroAsciiData library is online In-Reply-To: <200502251517.j1PFHB205622@serapis.hq.eso.org> References: <200502251517.j1PFHB205622@serapis.hq.eso.org> Message-ID: <78815A13-8760-11D9-A5C8-0030657B87AC@gsfc.nasa.gov> I've been hacking custom readers for most of the ASCII data files I process with Python so this has appeal. IDL did not have the best functionality for reading these types of files, especially when the number of lines was unknown. A format that I've used often are the ASCII data tables formerly kept at http://adc.gsfc.nasa.gov but which can now be retrieved via http://cdsweb.u-strasbg.fr/cats/Cats.htx. A reader for these files would readily fit into the AsciiData model. These data files also have a fairly standard README with info on the file format. I wonder if the table browser actually parses the README to build the web interface on-the-fly. This might also be a useful method in AsciiData for building the column metadata, or perhaps as a subclass of AsciiData. Tom On Feb 25, 2005, at 10:17 AM, Martin Kuemmel wrote: > > In collaboration with Jonas Haase the work on the > AstroAsciiData library has started. We put a design document > on the astrolib wiki. The content of this documents descibes > which kind of ASCII tables could/should be handled, > describes a possible object structure and gives some > examples of user applications. > Any feedback, comments or suggestions are welcome. > > http://www.scipy.org/wikis/topical_software/AstroAsciiData > > Martin Kuemmel > _______________________________________________ > AstroPy mailing list > AstroPy at scipy.net > http://www.scipy.net/mailman/listinfo/astropy > > -- Dr. William T."Tom" Bridgman Scientific Visualization Studio Global Science & Technology, Inc. NASA/Goddard Space Flight Center Email: William.T.Bridgman.1 at gsfc.nasa.gov Code 610.3 Phone: 301-286-1346 Greenbelt, MD 20771 FAX: 301-286-1634 http://svs.gsfc.nasa.gov/ From stephen.walton at csun.edu Fri Feb 25 14:56:02 2005 From: stephen.walton at csun.edu (Stephen Walton) Date: Fri, 25 Feb 2005 11:56:02 -0800 Subject: [AstroPy] Links to pages Message-ID: <421F82D2.40109@csun.edu> I can't help but notice that the new AstroAsciiData and AstroLibWCS Wiki's don't seem to have parent links anywhere on the Scipy site. By that, I mean if you start at www.scipy.org and click to Wikis, then to Topical Software, they aren't listed there. In fact, that link takes you to Fernando Perez's list of Topical Software http://www.scipy.org/wikis/topical_software/TopicalSoftware which probably isn't what is wanted. I mention this because, while I saw the initial announcement and bookmarked the pages, I think we want folks who browse the Scipy Wiki to see them too. From perry at stsci.edu Fri Feb 25 15:01:56 2005 From: perry at stsci.edu (Perry Greenfield) Date: Fri, 25 Feb 2005 15:01:56 -0500 Subject: [AstroPy] Links to pages In-Reply-To: <421F82D2.40109@csun.edu> References: <421F82D2.40109@csun.edu> Message-ID: <4f5842de2009cfb4f260806e7bd97e82@stsci.edu> On Feb 25, 2005, at 2:56 PM, Stephen Walton wrote: > I can't help but notice that the new AstroAsciiData and AstroLibWCS > Wiki's don't seem to have parent links anywhere on the Scipy site. By > that, I mean if you start at www.scipy.org and click to Wikis, then to > Topical Software, they aren't listed there. In fact, that link takes > you to Fernando Perez's list of Topical Software > > http://www.scipy.org/wikis/topical_software/TopicalSoftware > > which probably isn't what is wanted. I mention this because, while I > saw the initial announcement and bookmarked the pages, I think we want > folks who browse the Scipy Wiki to see them too. > > _______________________________________________ > AstroPy mailing list > AstroPy at scipy.net > http://www.scipy.net/mailman/listinfo/astropy > If you go to the topical software wiki and you will see a link to astrolib under the astronomy section (the last one). That page has links to AstroLibWCS and AstroAsciiData. Or do you mean something else? Perry From stephen.walton at csun.edu Fri Feb 25 15:07:00 2005 From: stephen.walton at csun.edu (Stephen Walton) Date: Fri, 25 Feb 2005 12:07:00 -0800 Subject: [AstroPy] Links to pages In-Reply-To: <4f5842de2009cfb4f260806e7bd97e82@stsci.edu> References: <421F82D2.40109@csun.edu> <4f5842de2009cfb4f260806e7bd97e82@stsci.edu> Message-ID: <421F8564.6040503@csun.edu> Perry Greenfield wrote: > If you go to the topical software wiki and you will see a link to > astrolib under the astronomy section (the last one). That page has > links to AstroLibWCS and AstroAsciiData. Ah, thanks. Missed that detail. Steve From William.T.Bridgman.1 at gsfc.nasa.gov Fri Feb 25 15:20:45 2005 From: William.T.Bridgman.1 at gsfc.nasa.gov (W.T. Bridgman) Date: Fri, 25 Feb 2005 15:20:45 -0500 Subject: [AstroPy] Comments sought on WCS library In-Reply-To: References: Message-ID: I'm apparently not currently a member that can post to the wiki and I'm not sure where this should go since it is also relevant to the AstroLibCoords page. The focus so far seems to be more on dealing with sky coordinates (understandable). I'd like to note that the solar data groups have expressed some interest in python and I use pyFITS for an increasing amount of my solar image processing. While it may take some time to get various coordinate transformations implemented, we should be careful not to setup a system that is difficult/impossible to expand to other systems. I do notice some mention of mapping 2-D to 3-D coordinate systems so maybe this covers that aspect? Tom On Feb 24, 2005, at 4:46 PM, Perry Greenfield wrote: > We (STScI) have started work on implementing a WCS library. I've > put some thoughts about the form that library should take (its > functionality and user interface) on the astrolib wiki. We'd be > interested in any feedback or comments about what features and > interface a WCS library should have. > > http://www.scipy.org/wikis/topical_software/AstroLibWCS > > Perry Greenfield > > _______________________________________________ > AstroPy mailing list > AstroPy at scipy.net > http://www.scipy.net/mailman/listinfo/astropy > > -- Dr. William T."Tom" Bridgman Scientific Visualization Studio Global Science & Technology, Inc. NASA/Goddard Space Flight Center Email: William.T.Bridgman.1 at gsfc.nasa.gov Code 610.3 Phone: 301-286-1346 Greenbelt, MD 20771 FAX: 301-286-1634 http://svs.gsfc.nasa.gov/ From barrett at stsci.edu Fri Feb 25 15:36:14 2005 From: barrett at stsci.edu (Paul Barrett) Date: Fri, 25 Feb 2005 15:36:14 -0500 Subject: [AstroPy] Comments sought on WCS library In-Reply-To: References: Message-ID: <421F8C3E.3090203@stsci.edu> W.T. Bridgman wrote: > I'm apparently not currently a member that can post to the wiki and > I'm not sure where this should go since it is also relevant to the > AstroLibCoords page. If you are a member of the AstroPy mailing list, then you can edit the wiki pages. Check the monthly mailing list reminder for your password. -- Paul > The focus so far seems to be more on dealing with sky coordinates > (understandable). I'd like to note that the solar data groups have > expressed some interest in python and I use pyFITS for an increasing > amount of my solar image processing. While it may take some time to > get various coordinate transformations implemented, we should be > careful not to setup a system that is difficult/impossible to expand > to other systems. I do notice some mention of mapping 2-D to 3-D > coordinate systems so maybe this covers that aspect? Agreed! -- Paul > Tom > > On Feb 24, 2005, at 4:46 PM, Perry Greenfield wrote: > >> We (STScI) have started work on implementing a WCS library. I've >> put some thoughts about the form that library should take (its >> functionality and user interface) on the astrolib wiki. We'd be >> interested in any feedback or comments about what features and >> interface a WCS library should have. >> >> http://www.scipy.org/wikis/topical_software/AstroLibWCS >> >> Perry Greenfield >> >> _______________________________________________ >> AstroPy mailing list >> AstroPy at scipy.net >> http://www.scipy.net/mailman/listinfo/astropy >> >> > -- > Dr. William T."Tom" Bridgman Scientific Visualization > Studio > Global Science & Technology, Inc. NASA/Goddard Space Flight > Center > Email: William.T.Bridgman.1 at gsfc.nasa.gov Code 610.3 > Phone: 301-286-1346 Greenbelt, MD 20771 > FAX: 301-286-1634 http://svs.gsfc.nasa.gov/ > > _______________________________________________ > AstroPy mailing list > AstroPy at scipy.net > http://www.scipy.net/mailman/listinfo/astropy -- Paul Barrett, PhD Space Telescope Science Institute Phone: 410-338-4475 ESS/Science Software Branch FAX: 410-338-4767 Baltimore, MD 21218 From jh at oobleck.astro.cornell.edu Fri Feb 25 15:40:53 2005 From: jh at oobleck.astro.cornell.edu (Joe Harrington) Date: Fri, 25 Feb 2005 15:40:53 -0500 Subject: [AstroPy] Comments sought on WCS library In-Reply-To: (William.T.Bridgman.1@gsfc.nasa.gov) References: Message-ID: <200502252040.j1PKerte009761@oobleck.astro.cornell.edu> Ditto from the world of planetary science. We want to be able to put out maps in various projections as FITS files, and have WCS give the coordinates when you run a cursor over the image. Sometimes there is more than one coordinate system, such as planetographic and planetocentric latitude or System I and System III longitude, so it would be good to be able to put several coord systems in the header and select among them when viewing the image. BTW, I think the wikis are open to anyone who has a scipy.org account. If you are logged into your account there, you should see an edit tab at the top of the wiki window. If not, please let Janet Swisher know. --jh-- Tom wrote: I'm apparently not currently a member that can post to the wiki and I'm not sure where this should go since it is also relevant to the AstroLibCoords page. The focus so far seems to be more on dealing with sky coordinates (understandable). I'd like to note that the solar data groups have expressed some interest in python and I use pyFITS for an increasing amount of my solar image processing. While it may take some time to get various coordinate transformations implemented, we should be careful not to setup a system that is difficult/impossible to expand to other systems. I do notice some mention of mapping 2-D to 3-D coordinate systems so maybe this covers that aspect? Tom