ds9 locations
Tom Duvall wrote on May 21, 2015
In my old setup at Stanford (linux iraf; version 6 ds9), I could get nice positions within an image by loading the image into ds9 using the display task (say after setting stdimage=imt800) and putting the cursor onto a location and reading off the position in either the 'physical' or 'image' readout at the top of the page.
In my new setup at MPS in Gottingen, Germany (linux iraf; version 7.2 ds9), the readouts of the cursor are associated with the imt800 and go from 1-->800 and don't seem to know about the image that has been loaded. Is there some configuration parameter that I should know about? I can load the image into ds9 from the unix command line( ds9 image), but I like using the display task. Is there some way to get this to work?
Thanks.
Tom
Mike Fitzpatrick wrote on May 22, 2015
Frame buffer sizes are defined in two files: the dev$graphcap file that IRAF tasks use (i.e. the "imt800" entry) and the "imtoolrc" file used by the server (ds9 or ximtool), IRAF tells the server which size to use by passing the configuration number and not the actual size. The install script will put the dev$imtoolrc file in /usr/local/lib/imtoolrc as one of the standard locations, but ds9/ximtool will also look for a $HOME/.imtoolrc file before using a builtin-table. It sounds like the configuration is being found since you're seeing an 800x800 size.
That said, the ds9 v7.1 and later versions have known issues with reading back the cursor that can only be fixed by using an earlier version of ds9. Other problems with ds9 can be fixed by not using the default unix sockets and forcing the inet socket to be used by defining
setenv IMTDEV inet:5137
in the terminal before logging into the CL. You might also check the SAO site to see if these bugs have been fixed in a newer/beta version.
Tom Duvall wrote on May 27, 2015
Thanks for the tips. I guess I didn't realize that I could just use ximtool. That seems to work fine for me.
Tom
Last post on May 27, 2015