iraf.net

In preliminary tests of the new OSX Yosemite (10.10) release there don't appear to be any issues in IRAF v2.16, either runtime or when compiling local package/tasks.

The only issue has to do with use of XGterm/XImtool, and perhaps other X11 applications as well: The binaries shipped with IRAF are expecting the X11 libraries to be under the /usr/X11R6 tree, however in Yosemite the X11 code has moved to /opt/X11. To restore working binaries you can simply make a symbolic link in the system to create the correct path, e.g.



Please post here if you find any additional problems.

Hello,

I updated my OS X to Yosemite last days and I have a problem with IRAF and ds9. When I try to use some tools on an image opened in ds9 I receive the next error:

\$this->_split2($m[0])ERROR: Cannot open device (node!imtool,,8192,8192)

I heard about the change in X11 directory and I tried what people suggest but that doesn't work for me. I do not know what to do T_T I am not very good with software installation stuff...

If someone had an idea, I would really appreciate it.

Thanks!

This is a bug in recent versions of DS9. The solution is to specify the inet socket to be used for display in the unix environment before you login to iraf, e.g.

setenv IMTDEV inet:5137 # for a C-shell
or
export IMTDEV=inet:5137 # for a Bash shell

You can put this in your startup files (e.g. .login/.cshrc/.bashrc) to make the change permanent, otherwise installing an older version of DS9 will also work (and could avoid another potential bug in cursor reads).

OMG, I know we have just met and it's too soon but I love you! It was driving me crazy and I spent hours searching for a solution on internet. Now it works! Thank you thank you thank you

I'm having an issue with iraf since I've updated my MacBook Pro to Yosemite. Iraf was running fine on my machine prior to this update. After updating I can no longer succefully login to iraf. I first had an issue with launching xgterm but have fixed this issue via the linking method described above. Now once xgterm term is launched if I type cl, iraf begins to launch but ultimately stalls. My xgterm looks like this:
.

If I then kill the login I get the following:
.

I'm not really sure why it isn't starting anymore. I've tried reinstalling iraf and rerunning mkiraf, but nothing changes.

Cheers,
Evan

Something similar has been reported a few times but I haven't been able to reproduce it. In v2.16.1 there is a new task, CHKUPDATE, called from the login.cl file to check a website here to see if your system is up to date. The hangup appears to be in this task trying to make the socket connection but the cause isn't clear (there are hints it has to do with local firewalls).

The fix is simply to comment out the call to CHKUPDATE in your login.cl (and the template login.cl in the iraf$unix/hlib directory). Post back if that doesn't fix it.

Thanks for the speedy reply. That fixed it!

Hello again,

So you're last suggestion helped, but once I got this previous issue resolved I had to put this project on the shelf for a few weeks. Anyways I'm back at it. Now I've come to realize that I am unable to open a plot window from within iraf. For example, I launch xgterm and login to iraf. If I try to use splot command then xgterm crashes without a warning or error before a plotting window is opened.

Cheers,
Evan

Hello,
I too have problems with Pyraf after updating to Yosemite. At the beginning I had a crash when clicking on the xgterm plot (in splot). I added the symbolic link pointing to the new location of xterm, but the result now is that when I click on the graphic window the program freezes, I continue to see the turning coloured ball and cannot do nothing in any iraf window.
Note that the issue is pyraf specific, as plain IRAF works.
I tried to reinstall via pip, I have now version 2.1.8, but no change.
Suggestions? Many thanks
Carla

---

Carla Maceroni INAF - Osservatorio Astronomico di Roma Monteporzio Catone (RM) Italy

It wasn't clear from the earlier message (which I completely missed) that both of these are pyraf-specific, however we've had no other reports of problems with xgterm under Yosemite. Be sure you're using a recent version of XGterm, for v2.16 systems you can look in $iraf/vendor/x11iraf/bin.macintel for a binary but the install script should link to this for you. Do a "which xgterm" to find out what binary you are actually running.

Otherwise, Pyraf has it's own graphics system and so you should probably contact the STScI Help Desk (help@stsci.edu) for problems specific to pyraf.