iraf.net

Greetings everyone, I have two computers using IRAF: an iMac G5, and my MacBook (both using Mac OS X 10.5). I need to use IRAF for my research, but I'm very new to it and am having a difficult time troubleshooting.[1] I have installed IRAF into my two computers using this site: http://macsingularity.org/iraf-on-macos-x/
The IRAF user is another admin, so installation took like 5 minutes. I used all the built-in defaults.[2] iMac CPU up to 100% - fc-cache is hogging up my CPU. Normally goes away when I quit IRAF/X11, but sometimes it just hangs there for a minute.
On my MacBok, I never have CPU issues. Everything runs smoothly.[3] I have these tutorials on http://iraf.noao.edu/iraf/ftp/iraf/misc/ (file: exer211.tar.Z), and I'll need your help here. Let's expand the package and go to exercises/intro. Inside there are files fintro0001 and fintro0002. On previous installations, I could use rfits on the two files fine, but now on both computers, rfits gives me a "cannot open pixel file" error. It used to work fine on previous installations, and I always let the installer go with the defaults. What do I need to do to get IRAF to do an rfits correctly?Also, a note about the tutorial: On an old installation (2008), on my iMac G5, when I do an rfits and work with files, I am free to use .imh, but on my MacBook, the files come out as .fits and I have to work in .fits. Is there any way I can change that too?
I'm still new to IRAF and I really don't understand what's going on here, but I can sense that I'll be asking questions here for quite a while. Can you folks help me out?

[quote:5887d015c3]
[1] I have installed IRAF into my two computers using this site: http://macsingularity.org/iraf-on-macos-x/
The IRAF user is another admin, so installation took like 5 minutes. I used all the built-in defaults.[/quote:5887d015c3]Note that the macsingularity installer may be out of date, as I remember it is just the v2.14 system but not the latest v2.14.1 patch release.[quote:5887d015c3]
[2] iMac CPU up to 100% - fc-cache is hogging up my CPU. Normally goes away when I quit IRAF/X11, but sometimes it just hangs there for a minute.
On my MacBok, I never have CPU issues. Everything runs smoothly.
[/quote:5887d015c3]The fc-cache is the X11 font-cache and nothing to do with IRAF. X11 on Intel systems has all sorts of issues, check the various apple sites for hints on this.[quote:5887d015c3]
[3] I have these tutorials on http://iraf.noao.edu/iraf/ftp/iraf/misc/ (file: exer211.tar.Z), and I'll need your help here. Let's expand the package and go to exercises/intro. Inside there are files fintro0001 and fintro0002. On previous installations, I could use rfits on the two files fine, but now on both computers, rfits gives me a "cannot open pixel file" error. [/quote:5887d015c3]The error means that the 'imdir' environment variable is naming either a directory that doesn't exist, or one you can't write to. The 'imdir' is set in your login.cl file, you can use a value like[code:1:5887d015c3]reset imdir = "HDR$pix/"[/code:1:5887d015c3]to put the pixel files in a 'pix' subdirectory of where the headers live.[quote:5887d015c3]
Also, a note about the tutorial: On an old installation (2008), on my iMac G5, when I do an rfits and work with files, I am free to use .imh, but on my MacBook, the files come out as .fits and I have to work in .fits. Is there any way I can change that too?[/quote:5887d015c3]The default 'imtype' for v2.14 systems in now FITS, you can uncomment and edit the value in your login.cl file to reset it back to 'imh' if you like, but FITS files can be used directly by the system. For the tutorial data, you can add the needed ".fits" extension with the command[code:1:5887d015c3]cl> rename fintro* fits field=extn[/code:1:5887d015c3]-Mike

Hi Mike, I think that your reply is way over me at the moment.Alright about X11... my intel machine runs X11 fine. It's my iMac G5 (PowerPC) that is gunning the CPU up to 100% when I am using IRAF. I have no idea what to do, but I can't use this. I have to use IRAF on my MacBook.Alright, now as for the login.cl file... alright, I'm really confused. I know where my login.cl file is, and I might as well post what I have inside:[code:1:ba5dd755dd]
# LOGIN.CL -- User login file for the IRAF command language.# Identify login.cl version (checked in images.cl).
if (defpar ("logver"))
logver = "IRAF V2.13 March 2006"set home = "/Users/andrej/iraf/"
set imdir = "/iraf/imdirs/andrej/"
set uparm = "home$uparm/"
set userid = "andrej"# Set the terminal type. We assume the user has defined this correctly
# when issuing the MKIRAF and no longer key off the unix TERM to set a
# default.
if (access (".hushiraf") == no)
print "setting terminal type to xgterm..."
stty xgterm
# Uncomment and edit to change the defaults.
#set editor = vi
#set printer = lp
#set pspage = "letter"
#set stdimage = imt800
#set stdimcur = stdimage
#set stdplot = lw
#set clobber = no
#set filewait = yes
#set cmbuflen = 512000
#set min_lenuserarea = 64000
#set imtype = "imh"
#set imextn = "oif:imh fxf:fits,fit plf:pl qpf:qp stf:hhh,??h"
# XIMTOOL/DISPLAY stuff. Set node to the name of your workstation to
# enable remote image display. The trailing "!" is required.
#set node = "my_workstation!"# CL parameters you mighth want to change.
#ehinit = "nostandout eol noverify"
#epinit = "standout showall"
showtype = yes
# Load the default CL package. Doing so here allows us to override package
# paths and load personalized packages from our loginuser.cl.
clpackage
# Default USER package; extend or modify as you wish. Note that this can
# be used to call FORTRAN programs from IRAF.package usertask $adb $bc $cal $cat $comm $cp $csh $date $dbx $df $diff = "$foreign"
task $du $find $finger $ftp $grep $lpq $lprm $ls $mail $make = "$foreign"
task $man $mon $mv $nm $od $ps $rcp $rlogin $rsh $ruptime = "$foreign"
task $rwho $sh $spell $sps $strings $su $telnet $tip $top = "$foreign"
task $vi $emacs $w $wc $less $rusers $sync $pwd $gdb = "$foreign"task $xc $mkpkg $generic $rtar $wtar $buglog = "$foreign"
#task $fc = "$xc -h $* -limfort -lsys -lvops -los"
task $fc = ("$" // envget("iraf") // "unix/hlib/fc.csh" //
" -h $* -limfort -lsys -lvops -los")
task $nbugs = ("$(setenv EDITOR 'buglog -e';" //
"less -Cqm +G " // envget ("iraf") // "local/bugs.*)")
task $cls = "$clear;ls"
task $clw = "$clear;w"
task $pg = ("$(less -Cqm $*)")if (access ("home$loginuser.cl"))
cl < "home$loginuser.cl"
;keep
prcache directory
cache directory page type help# Print the message of the day.
if (access (".hushiraf"))
menus = no
else {
clear; type hlib$motd
}# Delete any old MTIO lock (magtape position) files.
if (deftask ("mtclean"))
mtclean
else
delete uparm$mt?.lok,uparm$*.wcs verify-# List any packages you want loaded at login time, ONE PER LINE.
images # general image operators
plot # graphics tasks
dataio # data conversions, import export
lists # list processing# The if(deftask...) is needed for V2.9 compatibility.
if (deftask ("proto"))
proto # prototype or ad hoc taskstv # image display
utilities # miscellaneous utilities
noao # optical astronomy packageskeep[/code:1:ba5dd755dd]I have no idea what all this means, but I do not see a "reset imdir" anywhere, but I do see "set imdir."Where inside of the login.cl document would I add the code that you prescribed? Which line specifically would I comment out?

All you need to do is verify or change the path on the "set imdir = '/iraf/imdirs/adrej/". To change the 'imtype' remove the leading '#' char to uncomment the line, you don't need to change the value. Then just log back into IRAF for the changes to take effect.

Alright well that directory exists... weird, all I did was re-confirm the same Read & Write permissions to that folder, which I thought I had set over the weekend.The "#" technique worked.I haven't gone through the rest of the tutorial in spectacular detail, but as things come up, I'll have more questions. The help has been useful thus far.
Oh, and I found a workaround for the problem with X11. Apparently I had been using
xgterm &in Terminal, but for whatever dumb reason, this sometimes causes the iMac G5 to go nuts, but this does not happen on my MacBook. I just tried it again on my iMac, and it worked fine now. (??) I think that I'll be going directly to X11 whenever I can.