The simple answer is too many Python irons in the fire right now. PIL,
Tkinter, and some Python apps. When I get stuck on one area, I wait for
a solution, and move to another topic. I've just rotated back to FITS (
and the Pmw toolkit). I'll try DS9 out of curiosity, but I do like do
some ground work first. I'm also trying not to take some mis-steps here.
It's all to easy for people to misunderstand matters, and go off in
unintended directions. Another reason to dive right in is that the app
I'm working on works among its users pretty well, but they may not be
receptive to changes I'm working (to a program I didn't write) if they
have to do too many extras. For example, I do not want to complicate the
install process for them. Virtually none of them is familiar with fits,
although they certainly profit it by it. As another example, I wrote
some simple utilities a few months ago, but no one picked up on them,
since they required Python 2.5. They are stuck on version Pyton 2. 5 of
the program. The sponsor even added new features to the app, but in 2.5,
so there's reluctance even there. When I finish my additions to the app,
I think people will clearly see it has features they need. It'll be in 2.5.
I actually heard of DS9 about 3 weeks ago when my ccdsoft (Bisque
product) that deals with fits as its normal format died. I needed to
look at some files in fits, and someone recommended DS9. I think there's
a web interactive version of it. I finally wrestled ccdsoft back into
operability, and found a simpler way to deal with a fits file in the
interim. I have lots of balls in the air.
Cheers.
Stefan Schwarzburg wrote:
On Tue, Apr 7, 2009 at 11:29, Wayne Watson
<sierra_mtnv...@sbcglobal.net <mailto:sierra_mtnv...@sbcglobal.net>>
wrote:
Thanks, but I'm not sure why people keep bringing up DS9. As I
understand it, it is a stand alone program of sorts that has no
interface with Python. It seems to me it would be like saying use
Word or Adobe Photoshop.
DS9 is a external program with a python interface. From the user /
programmer point of view you can not distinguish between a python ds9
interface that has the "imshow" command and a pure python modeule that
has the "imshow" command. You can also (from that point of view) not
distinguish between a pure python module and one that is a wrapper for
a c library or something like this.
If you don't have stronger requirements, like for example a custom
python virtual machiene that can not run external programs, then I
don't see why you should care if this is an interface to a program or
if it is a interface to a module.
By the way: have you tried it? Is there some reason why you don't like
this kind of solution?
Cheers,
Stefan
Stefan Schwarzburg wrote:
On Mon, Apr 6, 2009 at 20:46, Cohen-Tanugi Johann
<co...@lpta.in2p3.fr <mailto:co...@lpta.in2p3.fr>> wrote:
the main thing missing when using matplotlib is the correct
use of
astronomical coordinate information, and that is a pretty big
plus of ds9.
J
I'm not sure if I posted this reply already to this thread, or if
it was the same topic on a different thread:
You can also try pysao to comminicate with ds9, the interface is
nicer (although the implementation might not, I don't know).
http://code.google.com/p/python-sao/
>>> import pysao
# run new instance of ds9
>>> ds9 = pysao.ds9()
>>> import pyfits
>>> f = pyfits.open('test.fits')
# display first extension of fits file
>>> ds9.view(f[0])
Note also, that there is the kapteyn package which uses
matplotlib (pylab) to display the data from fits files according
to the wcs (World Coordinate System) contained in most fits files
in the correct way. http://www.astro.rug.nl/software/kapteyn/
Cheers,
Stefan
Phil Hodge wrote:
>> The question is whether ds9 is a module that can be used
within a Python
>> program? I really do not know, but indications are that it
is not.
>>
>
>
> ds9 is not a Python module, it's a stand-alone program that
you run from
> Unix. However, there is an interface for displaying images
to it, and
> the Python module numdisplay uses that interface. The
advantage of ds9
> is that it is so powerful. imshow in matplotlib is pretty
good, though,
> and you may want to use matplotlib anyway for plotting.
>
> Phil
>
> _______________________________________________
> AstroPy mailing list
> astr...@scipy.org <mailto:astr...@scipy.org>
> http://mail.scipy.org/mailman/listinfo/astropy
>
_______________________________________________
AstroPy mailing list
astr...@scipy.org <mailto:astr...@scipy.org>
http://mail.scipy.org/mailman/listinfo/astropy
--
Institut für Astronomie und Astrophysik
Eberhard Karls Universität Tübingen
Sand 1 - D-72076 Tübingen
schw...@astro.uni-tuebingen.de
<mailto:schw...@astro.uni-tuebingen.de>
stefan.schwarzb...@googlemail.com
<mailto:stefan.schwarzb...@googlemail.com>
Tel.: 07071/29-78605
-----------------------------------------------------------------------
------------------------------------------------------------------------
_______________________________________________ AstroPy mailing
list astr...@scipy.org <mailto:astr...@scipy.org>
http://mail.scipy.org/mailman/listinfo/astropy
--
Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
(121.01 Deg. W, 39.26 Deg. N) GMT-8 hr std. time)****
"Less than all cannot satisfy Man." -- William Blake
--
Institut für Astronomie und Astrophysik
Eberhard Karls Universität Tübingen
Sand 1 - D-72076 Tübingen
schw...@astro.uni-tuebingen.de <mailto:schw...@astro.uni-tuebingen.de>
stefan.schwarzb...@googlemail.com
<mailto:stefan.schwarzb...@googlemail.com>
Tel.: 07071/29-78605
-----------------------------------------------------------------------
--
Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
(121.01 Deg. W, 39.26 Deg. N) GMT-8 hr std. time)****
"Less than all cannot satisfy Man." -- William Blake
_______________________________________________
Image-SIG maillist - Image-SIG@python.org
http://mail.python.org/mailman/listinfo/image-sig
