iraf.net

HeyI'm trying to install IRAF on my Macbook running Snow Leopard. I downloaded the 64bit tar file from iraf's website, set up an iraf user as told, and set terminal to run in cshWhen I install i get the following:[code:1:e6fa1b12fa][ajclarke:~] iraf% cd iraf/unix/hlib/
[ajclarke:~/iraf/unix/hlib] iraf% sudo ./install IRAF V2.15 System Installation
================================ Welcome to the IRAF installation script. This script will first
prompt you for several needed path names. The system will be verified
for proper structure before the actual install begins, all error must
must be corrected before you will be allowed to continue. Recommend-
ations for fixing problems will be made but no corrective action will
be taken directly. Once properly installed, you will be allowed to
do some minimal configuration. For each prompt: hit <CR> to accept the default value, 'q' to quit,
or 'help' or '?' to print an explanation of the prompt.
========================================================================
===================== Query for System Settings ======================
========================================================================New iraf root directory (/Users/iraf/iraf):
Default root image storage directory (/imdirs):
Local unix commands directory (/usr/local/bin): ========================================================================
===================== Verifying System Settings ======================
========================================================================Hostname = ajclarke.local OS version = Darwin 10.5.0
Architecture = macosx HSI arch = macosx
New iraf root = /Users/iraf/iraf Old iraf root = /Users/iraf/iraf
New imdir = /imdirs Old imdir = /imdirs
Local bin dir = /usr/local/bin
Checking definition of iraf root directory ... [ OK ]
Checking iraf root and imdir directory ... [ OK ]
Checking iraf directory write permissions ... [ OK ]
Checking Core system binary directory ... [ OK ]
Checking NOAO package binary directory ... [ OK ]
Checking that local bin directory exists ... [ OK ]
Checking for existing commands directory... [ OK ]Proceed with installation? (yes):
========================================================================
========================= Begin Installation =========================
======================================================================== Editing Paths
-------------
Editing the iraf user .login/.cshrc paths ... [ OK ]
Editing iraf/imdir paths into system files ... [ OK ] Checking File Permissions
-------------------------
Checking iraf file permissions ... foreach: No match.
[/code:1:e6fa1b12fa]I would love help on this. My knowledge of terminal is small to say the least, but right now im spending more time trying to install iraf when I should be getting some science out of it.Thanks a bunch for your help.
Adam

Same problem here on my new iMac.
I didn't create an IRAF user, since it worked this way on Ubuntu...Don't want to switch back to the 2.14 release of Scisoft...cheers

To be honest I have since tried it on my main account i set up upon installation of Snow Leopard too and I had the same issue. :SAny help here would be very much appreciated. My project time is ticking on and Im beginning to panic a little

It would appear that at some point the build tree had some of the HSI binaries removed for certain architectures, this is what's causing the problem.What I've done is rebuild he distribution files so you can either try downloading them again, or to simply get the missing binaries you can download ftp://iraf.noao.edu/iraf/v215/support/hsi_bin.tar.gzUnpack this file in the $iraf/unix directory (NOT the $iraf), then try rerunning the install script.Sorry for the inconvenience.-Mike

@adamclarkeIf this does not work for you, you can get the scisoft package here:
http://web.mac.com/npirzkal/Scisoft/Scisoft.htmlThis installs IRAF and other components into a completely different environment, so it does not affect your own installation, and works 100%. cheers

[quote:02d4ba28ac]
If this does not work for you, you can get the scisoft package here:
http://web.mac.com/npirzkal/Scisoft/Scisoft.html [/quote:02d4ba28ac]Note this is still the older v2.14.1 release, no dynamic packages, no ppc support, etc.....
[quote:02d4ba28ac]
This installs IRAF and other components into a completely different environment, so it does not affect your own installation, and works 100%. [/quote:02d4ba28ac]As long as you don't need to print anything.....

Yep, thats some reasons, why I don't want to switch back to Scisoft and I really like the 2.15 release so far!!
e.g.: Scisoft killed part of my macports installation last time...
Anyway, your hint helped, IRAF is running now.
There is just one other thing:Autocompletion (with TA and showing previous commands (with up arrow key) does not work...they work in the xgterm, but as soon as I log into IRAF, they stop working... This has to be a problem of my IRAF installation, since I tried to install x11iraf 1.3.1. I also started IRAF from the bash, where the same error occurs...thanks for any hint on that.

I guess I'm still working out the bugs in my build scripts.....Near as I can tell, the ecl.e for macintel was actually the cl.e, hence no tab completion or other readline goodies. Distro was updated yet again, and you can get a working binary from ftp://iraf.noao.edu/iraf/v215/support/ecl.e.macinteljust install as iraf$bin.macintel/ecl.eApologies once again.

Perfect!!! No need to apologize, I never had such a good software support before.@adamclarke: If you experience the same error, don't forget to chmod the correct file permissions for the new ecl.e after replacing the old one, otherwise it won't run.

I'm still getting the same error :/ Checked the chmod permissions and made sure I had read write and execute for the new folders and files.

which error, did you download the hsi_bin.tar.gz mentioned by fitz above and have you followed the instructions?The ecl.e is just for resolving the autocompletion feature.

I did both. Right I have now redownloaded the full OSx 64 bit release.I now have it working on my iraf account. But when i log into my usual account, and move to the directory I want to run iraf from and type mkiraf, it says it is an unknown command :/Managed to fix it - changed my terminal Open Shell to "/bin/csh" whereas before it was /usr/bin/loginThis was opening it in bash, which I thought was ok, as long as I changed to csh before trying mkiraf. But this doesnt seem to be the case. I have to admit to not fully understanding shells. Though I was told bash would be better for me than csh, and it shouldn't have been as issue, since I can always run csh by just typing the command.Perhaps someone could clarify for me?- edit: THere also seems to be an issue that terminal I can set to run in csh and the commands work, though I would prefer to use bash and hand change it when i need iraf, since all my aliases are set up for it, however X11 which I'll need for the graphical use of Iraf seems determined to used bash, and changing it by typing csh then means $ cl wont work :s- edit2: Managed to find a work around. Instead of opening X11 itself and trying to use IRAF, instead i open Terminal, type xterm, which opens X11 (still says bash which is confusing) and then it works. Bit fiddly though. Would much prefer just to open X11.

Right another issue now. I have iraf working seemingly, though the problems with X11 and terminal being different seem usual for mac users so hence is not an issue wth IRAF.However, I put the new ecl.e in the folder, made sure to chmod it for xwr yet the tab -auto-completion still isn't working :/

[quote:007722caa2]
This was opening it in bash, which I thought was ok, as long as I changed to csh before trying mkiraf. But this doesnt seem to be the case. I have to admit to not fully understanding shells. Though I was told bash would be better for me than csh, and it shouldn't have been as issue, since I can always run csh by just typing the command. Perhaps someone could clarify for me? [/quote:007722caa2]IRAF commands like MKIRAF and CL are in fact C-shell scripts, however it doesn't matter what *your* shell is since the C-shell interpreter will be invoked to the run the script regardless. What does matter, is whether the environment in your shell defines a 'path' variable that can find these commands in the first place. For bash and csh the shell startup file is different (e.g. .bashrc and .cshrc), and if your 'path' is defined in a .login then it depends on whether you create a 'login shell' that reads this file.[quote:007722caa2]
- edit: THere also seems to be an issue that terminal I can set to run in csh and the commands work, though I would prefer to use bash and hand change it when i need iraf, since all my aliases are set up for it, however X11 which I'll need for the graphical use of Iraf seems determined to used bash, and changing it by typing csh then means $ cl wont work :s [/quote:007722caa2]This sounds like your user account is setup to use bash (use 'chsh' to change it), when you type 'csh' you create a C-shell but not a 'login shell', i.e. definitions in your .login file are not read. Check the value of $path to see whether the directory containing the 'cl' command is include, and adjust your .cshrc file definition of $path accordingly.
[quote:007722caa2]
- edit2: Managed to find a work around. Instead of opening X11 itself and trying to use IRAF, instead i open Terminal, type xterm, which opens X11 (still says bash which is confusing) and then it works. Bit fiddly though. Would much prefer just to open X11.[/quote:007722caa2]In this case the xterm opened is running your user bash shell and your environment is correct, iraf works because the commands automatically run under the C-shell and are being found.[quote:007722caa2]
However, I put the new ecl.e in the folder, made sure to chmod it for xwr yet the tab -auto-completion still isn't working :/[/quote:007722caa2]What is the value of the TERM environment variable (i.e. "cl> !echo $TERM' to find out from the CL)? Some variant of 'xterm' should work, if it says 'dumb' then that explains it (put a 'setenv TERM xterm-color' in your .cshrc to fix it).