problems on initiating IRAF
Guest wrote on Jun 13, 2007
Dear Sir/Madam,
I would like to install IRAF V2.12.1 on my decktop running Redhat-like
linux CentOS 5. The installation finished with no problem, however the
IRAF cannot be initiatized (cannot start iraf session with 'cl'
command). Below are some information:
1) 'IRAF V2.12.1 System Installation' script completed with:
"Congratulations! IRAF has been successfully installed on this system."
..
"Installation Completed With No Errors."
2) System settings:
New iraf root directory: /iraf/iraf
Default root image storage directory: /iraf/imdirs
Local unix commands directory: /usr/local/bin
Hostname = localhost.localdomai OS version = Linux 2.6.18-8.el5
Architecture = redhat HSI arch = redhat
New iraf root = /iraf/iraf Old iraf root = /iraf/iraf
New imdir = /iraf/imdirs Old imdir = /d0/imdirs
Local bin dir = /usr/local/bin
3) I'd tried the following commands in all user, included IRAF, root:
setenv iraf /iraf/iraf/
source $iraf/unix/hlib/irafuser.csh
But the the command 'login.cl' didn't work as 'Permission denied' in
non-iraf user.
However, sometime under IRAF login, 'login.cl' worked and I typed the
followings:
mkiraf
initalize uparm? Y
enter terminal type: xterm
Then I started ds9 and xterm and type 'cl', then 'command not found.'.
What should I do? I have no experience on installation of IRAF.
I am looking forward for your advice. Thanks.
Regards,
SO Chu Wing
Research student
department of Physics
University of Hong Kong
Post generated using Mail2Forum (http://www.mail2forum.com)
I would like to install IRAF V2.12.1 on my decktop running Redhat-like
linux CentOS 5. The installation finished with no problem, however the
IRAF cannot be initiatized (cannot start iraf session with 'cl'
command). Below are some information:
1) 'IRAF V2.12.1 System Installation' script completed with:
"Congratulations! IRAF has been successfully installed on this system."
..
"Installation Completed With No Errors."
2) System settings:
New iraf root directory: /iraf/iraf
Default root image storage directory: /iraf/imdirs
Local unix commands directory: /usr/local/bin
Hostname = localhost.localdomai OS version = Linux 2.6.18-8.el5
Architecture = redhat HSI arch = redhat
New iraf root = /iraf/iraf Old iraf root = /iraf/iraf
New imdir = /iraf/imdirs Old imdir = /d0/imdirs
Local bin dir = /usr/local/bin
3) I'd tried the following commands in all user, included IRAF, root:
setenv iraf /iraf/iraf/
source $iraf/unix/hlib/irafuser.csh
But the the command 'login.cl' didn't work as 'Permission denied' in
non-iraf user.
However, sometime under IRAF login, 'login.cl' worked and I typed the
followings:
mkiraf
initalize uparm? Y
enter terminal type: xterm
Then I started ds9 and xterm and type 'cl', then 'command not found.'.
What should I do? I have no experience on installation of IRAF.
I am looking forward for your advice. Thanks.
Regards,
SO Chu Wing
Research student
department of Physics
University of Hong Kong
Post generated using Mail2Forum (http://www.mail2forum.com)
Mike Fitzpatrick wrote on Jun 13, 2007
The 'login.cl' file isn't a command, it's a startup script for IRAF. To start IRAF, you would normally first do a 'mkiraf' to create the login.cl and a 'uparm' directory for storing parameters. Thereafter, the 'cl' command is used to login to IRAF.
A 'command not found' message usually means you just don't have the 'local bin directory' in your path, but sometimes after installing a new command you need to type 'rehash' at the unix prompt to pick up the new commands. Edit the 'path' (or 'PATH') settings in your .login/.cshrc file to include /usr/local/bin, or try starting explicitly with the command
Hope this helps,
-Mike
A 'command not found' message usually means you just don't have the 'local bin directory' in your path, but sometimes after installing a new command you need to type 'rehash' at the unix prompt to pick up the new commands. Edit the 'path' (or 'PATH') settings in your .login/.cshrc file to include /usr/local/bin, or try starting explicitly with the command
% /usr/local/bin/mkiraf
% /usr/local/bin/cl Hope this helps,
-Mike
Last post on Jun 13, 2007