iraf.net

I installed cygwin, IRAF/cygwin and ds9 in my WinXP laptop a
couple months ago. I am able to display images on ds 9 from IRAF
(such as using display,overlay contour, etc). However, when I try to use any interactive tasks (such as imexamine)
and I type any keys (such as "a", "?", etc), ds9 crashes and disappears.
I also notice that when I type "g", it is one of "key-stroke"command
within ds9. Please help! Thanks in advance!Josephine

Jospehine,I haven't seen this error nor can I reproduce it using DS9 v4.0b9. Are you doing anything special when starting the task, e.g. setting an IMTDEV variable to display to sockets or setting a command line flag? Are you able to read the cursor with the RIMCURSOR command at the cl prompt? Does restarting your IRAF/DS9 clear the problem? Typically a DS9 crash will create a "write to IPC with no reader" message on the iraf side, are you seeing this?As for the 'g' keystroke being reserved in DS9, that's a known issue ds9 will have to fix. I'm not aware of a way to remap the keys (at least not from the last time I looked at it).Cheers,
-Mike

Hi Mike, Thank you for your quick response!

I did the following:

windpower(Jose)-->>setenv IMTDEV inet:5137:127:0.0.1
windpower(Jose)-->>ds9
windpower(Jose)-->>cl
ecl> display m51.fits
frame to be written into (1:16) (1):
z1=35. z2=346.0218 #m51 image on ds9
ecl>
ecl> rimcursor #hit space-bar once
405. 275. 100 \040
ERROR: Cannot open device (node!imtool,,512,512)
called as: `rimcursor ()' #ds9 crashes
ecl> logout
windpower(Jose)-->>ls ds9*
ds9.exe.stackdump*
Any suggestion! Thanks again!.
Josephine

Check the DS9 version: release v4.0b7 claims to "fix a problem with iis and cursors". You can the version from the About box under the File menu, update to a newer release if it's before 4.0b7. -Mike

Thank you again!The version that I am using is v4.0b11.More suggestions, please!
Josephine

My last suggestion is that you contact Bill Joye at SAO ( saord@cfa.harvard.edu) to see if he has any ideas, I can't reproduce the problem myself. Please post a solution if you get one.-Mike

Thanks again!I have sent an email to saord@cfa.harvard.edu to ask for help!If I get a solution, I will definitely post it here.Josephine

Good News!

Actually, there is a bug in v4.0b11.

Now, a new version v4.12 of ds9 is available. I reinstalled it.
Up to this minute, both iraf and ds9 work together well.


Josephine

Dear fitz,In response to your reply to rfinger, we are running a dual 2.0 GHz
G5 PPC XServe under OS 10.9 and IRAF 2.13b2. We get a bus
error whenever we try to display a FITS image in ds9, although
we can display dev$pix OK. Note that all IRAF interactions
are done using XWindows over a campus network, like with
XWIN32 on PCs.Based upon a document I found about installing
IRAF 2.13b2, I did the following:login as iraf
sudo chmod g+w /Downloaded ib.macx.ppc.tar.gz and nb.macx.ppc.tar.gz
from your ftp site.Unzipped and extracted ib.macx.ppc and nb.macx.ppc (i.e.,
two files).Moved ib.macx.ppc to /iraf/irafbin/bin.macosx
Moved nb.macx.ppc to /iraf/irafbin/noao.bin.macosxI couldn't do
setenv iraf /iraf/iraf/
because setenv wasn't recognized,
so I logged out and logged back in as root.
Then,setenv iraf /iraf/iraf/
cd $iraf/unix/hlib
sudo ./installand followed the instructions as per the usual IRAF installation.This appeared to make no difference (we still get bus errors), and surprisingly, the ib and nb files remained in their directories.You can probably tell from this I don't know what I am doing, although
I did manage to get everything to work under IRAF 2.12.2. What
has made life difficult is that I have used Marcos Huerta's installer
exclusively before this, so the gory details described above are
nothing I have encountered before.Your cogent advice would be appreciated.Best wishes,
Marshall

Hi Marshall,Glad to hear from an email address I recognize from back in the day .... [quote:79b59a714d]login as iraf
sudo chmod g+w /Downloaded ib.macx.ppc.tar.gz and nb.macx.ppc.tar.gz
from your ftp site.Unzipped and extracted ib.macx.ppc and nb.macx.ppc (i.e.,
two files).Moved ib.macx.ppc to /iraf/irafbin/bin.macosx
Moved nb.macx.ppc to /iraf/irafbin/noao.bin.macosx[/quote:79b59a714d]To be clear: You moved the unzipped contents of these files to those directories and not the actual file, right?[quote:79b59a714d]I couldn't do
setenv iraf /iraf/iraf/
because setenv wasn't recognized,
so I logged out and logged back in as root.[/quote:79b59a714d]Most of the recent platforms will default to 'bash' as the default shell, the 'setenv' is a csh/tcsh command and all of the IRAF scripts and install instructions assume a C-shell. Just type 'csh' to start a C-shell and you should be able to follow the install directions literally (except for the architecture name.[quote:79b59a714d]
....and followed the instructions as per the usual IRAF installation.This appeared to make no difference (we still get bus errors), and surprisingly, the ib and nb files remained in their directories.[/quote:79b59a714d]Again, are we talking about the actual IB and NB tarballs or the unpacked files?A command such as[code:1:79b59a714d]dir bin$*.e long+[/code:1:79b59a714d]should show file dates from 6/06 to indicate the patch was properly applied, anything earlier and there was a problem.Cheers,
-Mike

Dear Mike,Sorry I called you fitz, but I couldn't remember your first name. Glad to see you are alive and kicking.[quote:cb0e726480]To be clear: You moved the unzipped contents of these files to those directories and not the actual file, right? [/quote:cb0e726480]Well, your focus on this issue led me to examine things more closely. When I click on the two files on your ftp site, they are downloaded and unzipped automatically. The results are single files with no extension. Since there was no .tar on the end, I figured whatever was tarred was also de-tarred by the Mac, and so I figured I was dealing with a measly 2 files.So, instead of simply clicking on the files, I took pains to save the files on your server on to our disk without alteration, i.e., the .gz versions. This was possible by choosing a "Save Link to Disk" option put forward by clicking the right button on a two-button mouse we are using. Then, I put them in the appropriate directories, and executedtar zxpf ib.macx.ppc.gz (e.g.)Lo and behold, out popped a nice long list of files. After doing all this,
I re-did the install, and magically we no longer have any bus errors.So, the Mac's automatic gunzipping feature was the root of our problems, combined with my ignorance of what the results represented. I suppose I could have detarred the unzipped files if I had usedtar xpf rather thantar zxpfbut I am happy I made any progress at all.Thanks for your insights and incredibly quick response on this subject.Best wishes,
Marshall