iraf.net

I'm getting this error message when running the task "simulator" in the external ucsclris package. I've just done a new install of iraf, on a Macbook Pro running Yosemite, following these instructions:

http://www2.lowell.edu/users/massey/Macsoftware.html

The SIMULATOR task appears to be compiled into the UCSCLRIS binary, but isn't normally declared as a task in the package. Apparently you figured out how to do this yourself or was the task already declared as part of some version of the package you installed (i.e. did you do a "make ucsclris" to install the package or get a version some other way)?

Since the task hasn't been modified since 2001 it is likely this is a 64-bit problem if it's not some more mundane coding bug. If so, you could try installing the 32-bit 'macosx' architecture version and use that binary instead. For example,



Even on a 64-bit system IRAF will be able to use older 32-bit binaries.

If the problem continues then it may be because this is a graphics task and the CL (which provides the graphics kernel) is unhappy about something. You can get 32-bit versions of the CL binaries from ftp://iraf.noao.edu/iraf/v216/support/macosx you can install in your iraf$bin.macintel directory to see if this fixes the problem.

Ultimately the package will need to be ported to 64-bits, however it was developed by an outside author so didn't receive much testing (esp. the undeclared simulator task!). Hope this helps.

I tried your suggestion to create a 32-bit version and sure enough the simulator task is now working.

That was fast - thanks Mike!

-Adam

If I wanted to try using the 32-bit cl, I'm not sure what to do once I've retrieved the CL binaries from ftp://iraf.noao.edu/iraf/v216/support/macosx - $iraf/bin.macintel already has cl.e, ecl.e, and vocl.e files.

Even though I was able to start up the simulator task after remaking ucsclris, the interface to the gterm is not working correctly.

Just make sure the binaries are executable and install them in the iraf$bin.macintel directory. If you like, make a backup of the existing *cl.e binaries first.

So replace the existing macintel binaries with the macosx binaries? do I need to set IRAFARCH to macosx too?

The system will look in whichever directory IRAFARCH specifies, if it finds a 'macosx' binary instead of 'macintel' it won't matter (or notice).

Thanks. The 32-bit cl appears to have solved the gterm issue.