installation help

Welcome to iraf.net Monday, May 20 2024 @ 04:43 AM GMT

	Forum Index > Archives > Sitemail Archives
installation help

Anonymous: Guest

04/19/2001 10:45PM (Read 818 times)

Hello,I am trying to install iraf on Red Hat linux 6.2. I have downloaded the
necessary as, ib, and nb files. I followed the install procedure and
created the directories as needed and unpacked the packages where they
belong (I think!). When it is time to run the install script under the
/unix/hlib directory I get the following message:new iraf root directory ():I don't know what to put for the answer??? If I put "iraf" it gives the
response of -- iraf/unix/hlib: No Such file or directoryHow to I solve this?
Thanks.Jon Faranda
jonfa@bellsouth.net

Anonymous: Guest

04/19/2001 10:45PM

Hi Jon,
Into which directory did you unpack the AS distribution files?
This is what you should reply with in the install script, but you should
also have been prompted with some sort of path (or did you actually use
the / root directory?). For reference, your IRAF directory tree should look
something like:
/iraf
/ \
(AS) /iraf /irafbin
/ \
(I

bin.redhat noao.bin.redhat (N

The graph indicates where each of the three distributions sets should be
unpacked. In this case /iraf/iraf is the "iraf root directory". Also,
the install script should be run as the root user with 'iraf' defined in
the environment, for example % su # become root
# setenv iraf /iraf/iraf/ # trailing '/' required,
# c-shell assumed
# cd /iraf/iraf/unix/hlib # go to the hlib directory
# ./install # run the install script Another thing to try that might make things simpler is to run the
SYSINFO script (http://iraf.noao.edu/sysinfo.html) on your system to check
for possible problems. You can download the script from the web page
which also contains instructions. Let us know if you still have problems.Regards,
Mike Fitzpatrick

Anonymous: Guest

04/19/2001 10:45PM

>From jonfa@bellsouth.net Thu Apr 19 18:07:10 2001
Sender: iraf@jxmls04.se.mediaone.net
From: Jon Faranda <jonfa@bellsouth.net>
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: installation helpHello,Thanks for the reply. I set up the tree exactly how you explained and
still no luck. I have created a user account called iraf. I then created
a directory named iraf and the tree is how you posted. When I run that
script you sent I get errors galore!!!! It says it ends due to severe
errors. I tried the /unix/hlib script again and no luck.
Looks like I'm stuck in the mud. Please save me.Is it possible for you to give a step by step install procedure for the
version of red hat I am using?
One thing I noticed was that if I try to execute the setenv command it
fails. It says "command not found". Should I be using a certain shell to
install this?I really do thank you for your time and patience.Jon Faranda
jonfa@bellsouth.net>From fitz Fri Apr 20 11:57:21 2001
To: jonfa@bellsouth.net
Subject: Re: installation helpHi Jon,
The last page of the installation guide contains a summary of the
install process, I can't do much better than that but there are a few hints
which may help: - It's assumed the 'iraf' user is setup to use a C-shell and not
a Bash or some other shell, and the login directory for the
account is iraf$local. This is because the system ships with
some environment files that help with maintanence. If you create
the iraf user *after* unpacking the files the system may have
overwritten these files with it's defaults.
- The root user is normally setup to use bash as the shell, and would
explain the "command not found". Once you su to root you can start
a c-shell using the command "csh", then do the setenv and run the
install script. The install script (and others in iraf) will
start their own csh to execute so normal users can use whichever
shell they like, the syntax of setting something like $iraf will
vary by shell, but "set iraf = /iraf/iraf/" will work for bash.The first item won't matter until you get the system installed an log in
as the iraf user. The second however could be the problem. C-shell is
almost always available but is sometimes an options, to be sure you have
one do a "which csh" (should say /bin/csh or /usr/bin/csh), if you get
a "command not found" you might not have it installed.
There is also a typo in the PC-IRAF install script (and extra
logical or (i.e. '||') at line 515) which prevents the /dev/imt1 fifo pipes
and /usr/local/lib/imtoolrc link from being created. This would cause
problems later on once you tried to display with something larger than a
512x512 frame buffer. You can download a patched version of the script from
our archive directory or just edit the file by hand.
Hope this helps, let me know if you still have problems or questions.Cheers,
-Mike

Anonymous: Guest

04/19/2001 10:45PM

>From jonfa@bellsouth.net Fri Apr 20 14:27:47 2001
From: Jon Faranda <jonfa@bellsouth.net>
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: installation help
Thanks for the reply.
One last thing and I promise I'll leave you alone. When it is time to
use the install script under /unix/hlib exactly what do I put for the
new iraf root directory? What ever I seem to put it gives me the reply
"file or directory not found" Is there something unique that has to be
entered here?For example, if i write:/iraf
iraf/
/iraf/iraf/
iraf/iraf
iraf/iraf/they all give the same result.Thanks.--
Regards,Jon Faranda
jonfa@bellsouth.net
>From fitz Fri Apr 20 14:38:47 2001
To: jonfa@bellsouth.net
Subject: Re: installation helpJon,
The "iraf root directory", if you've followed the tree sent earlier,
would be /iraf/iraf. I'm a little troubled that you don't get some sort
of prompt, since even if $iraf isn't defined in the environment and one of
a number of default directories isn't found, the fallback is to use the
parent directory relative to the hlib directory. Actually now that I
look at it again the default value is reset after that to something based
on $iraf, which if it remains initialized to an empty string would account
for the empty prompt. So, it seems that as long as you start a 'csh' as
root before running the script, do a "setenv iraf /iraf/iraf/" and then
run the install script you should see the prompt with /iraf/iraf as the
default value.
If you still have problems could you try running the script the
following way: csh -x installand then send me the results (reply to the prompt so I can see what happens
after that). Also, what kinds of errors did you get from the SYSINFO script?
I'm still trying to figure out if this is something in your directory
structure or just that csh isn't available. Lastly, just checking but
when you say "/unix/hlib" you mean this as shorthand for /iraf/iraf/unix/hlib
and not literally, right?Cheers,
-Mike

Anonymous: Guest

04/19/2001 10:45PM

>From jonfa@bellsouth.net Fri Apr 20 14:51:51 2001
From: Jon Faranda <jonfa@bellsouth.net>
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: installation helpHello,I got it! The problem was that I wasn't specifying the whole path name.
It installed without reporting any errors. Now what? How do I execute
the program? Are there this things that need to be compiled?
Thanks!!!!Jon Faranda
jonfa@bellsouth.net
>From fitz Fri Apr 20 14:56:44 2001
From: Mike Fitzpatrick <fitz>
To: jonfa@bellsouth.net
Subject: Re: installation helpJon,
The whole path name to what, the install script or the iraf tree?
To start it just log in as yourself and type "mkiraf" to create a login.cl
file in the directory, and then type "cl" to start IRAF. You should be
using an Xterm window so you can do graphics, or XGterm if you also installed
the X11IRAF tools (from the /iraf/x11iraf directory of our archive or the
CD). To display an image you'll need to have a server running first (e.g.
XImtool from X11IRAF, or SAOimage/SAOtng/DS9), these need to be installed
separately. When you run MKIRAF just tell it what type of terminal you
are using (probably xterm, but as I say xgterm is better (nicer graphics)).
If you get a "command not found" from either mkiraf/cl commands then the
"local bin directory" specified when you ran install is not in your default
path. If you get problems trying to login to the CL be sure the iraf
path was specified as /iraf/iraf.Cheers,
-MikeP.S. You might also want to have a look at a draft Beginner's Guide
available as ftp://iraf.noao.edu/pub/beguide.ps (PostScript so use the
'gv' command to view it or else print it out). Various other documents
(cookbooks etc) are available from our web site, the /iraf/docs directory
of the archive (see the README for a table of contents), and some
introductory tutorials are available /iraf/misc archive directory as
exer211.tar.Z. You don't need to compile anything unless you install
add-on packages and build from sources. Let me know if you still have
problems or questions.

Anonymous: Guest

04/19/2001 10:45PM

>From jonfa@bellsouth.net Fri Apr 20 15:16:16 2001
From: Jon Faranda <jonfa@bellsouth.net>
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: installation helpHi,The path name when it asked for the root directory was not the entire
path. I had to put /home/iraf/iraf/iraf/ in order for it to recognize
where it was/home/iraf is my iraf user home. I'm not sure if this was correct, but
it worked. I ran the mkiraf and it executed without any problems. I
chose xgterm. It loads ok and it appears to be working!!!!! The cl
command works fine.You wrote that in order to display an image, however,
I will need additional things. Can I install just XIMtool to load
images? If so, where do I obtain the package to do this?(I guess the
iraf site)Thanks a million!Jon Faranda
jonfa@bellsouth.net
>From fitz Fri Apr 20 15:21:03 2001
To: jonfa@bellsouth.net
Subject: Re: installation helpJon,
The X11IRAF tools for RedHat 6.2 are available as ftp://iraf.noao.edu/iraf/x11iraf/x11iraf-v1.2-bin.redhat6.tar.gzJust download in binary mode and unpack with the command % tar -zxvf x11iraf-v1.2-bin.redhat6.tar.gzThen follow the README file for instructions about where to copy the files
for installation. Note that you should actually be running an XGterm window
when you run iraf and tell it xgterm in the mkiraf. This sets the terminal
type in iraf, but if you use some other kind of window you usually get
garbage on the screen. X11IRAF includes both XGterm and XImtool.Cheers,
-Mike

Anonymous: Guest

04/19/2001 10:45PM

Anonymous: Guest

04/19/2001 10:45PM

>From jonfa@bellsouth.net Fri Apr 20 16:42:49 2001
From: Jon Faranda <jonfa@bellsouth.net>
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: installation helpThis is the last question I promise. How do I display a fits image using
iraf? I'm a little confused. Do I loggin into iraf (cl) or do I use the
other package Ximtool? I will read and review the basics of using iraf
tonight, but after the many days I have been trying to get this to work
and I would really like to display an image for satisfaction.I downloaded and installed the ds9 software and opened an image with,
but I don't think this is where I will be doing calibration such as dark
subtraction and flat fielding of images, correct? Also, does it matter
where I put the executable ds9 file? (does it need to be in the
/usr/local/bin ?)How do I make the cl file in /usr/local/bin global? If I execute it from
any other directory it gives me a "no login.cl file found in current
directory, but loads the package anyway.Thanks
Jon Faranda>From fitz Fri Apr 20 16:50:08 2001
To: jonfa@bellsouth.net
Subject: Re: installation helpJon,> This is the last question I promise. How do I display a fits image using
> iraf? I'm a little confused. Do I loggin into iraf (cl) or do I use the
> other package Ximtool? I will read and review the basics of using iraf
> tonight, but after the many days I have been trying to get this to work
> and I would really like to display an image for satisfaction. FITS images are supported directly by IRAF, so once you log
into the CL you would display an image using something like cl> reset stdimage = imt1024 # set a 1024x1024 frame buffer
cl> display foo.fits 1 # display the imageThe GDEVICES command will list the available frame buffers, the packages
you need are loaded automatically. As long as you have ximtool/ds9 running
before you try the display you should see the image. For immediate
gratification you can display the standard test image with cl> display dev$pix 1
> I downloaded and installed the ds9 software and opened an image with,
> but I don't think this is where I will be doing calibration such as dark
> subtraction and flat fielding of images, correct? Also, does it matter
> where I put the executable ds9 file? You can put DS9 anywhere in your path, /usr/local/bin is a good
choice. It has some of it's own analysis capabilities but things like
normal CCD processing are done with various IRAF tasks. DS9 just provides
an image display, tasks like IMEXAMINE and IMEDIT use it to let you interact
with the image. You can also just put the name of a FITS file on the command
line when you start it to have it display automatically, or the Load panel
from the File menu will do it as well.> How do I make the cl file in /usr/local/bin global? If I execute it from
> any other directory it gives me a "no login.cl file found in current
> directory, but loads the package anyway. The 'cl' command is just what's used to startup iraf, the login.cl
file on the other hand is unique to wherever you did the MKIRAF. It's
purpose is the set various parameters needed (e.g. default printer, frame
buffer, etc), but MKIRAF also creates a "uparm" directory to keep track
of your parameter settings. You can't really have a global login.cl file,
just do a new MKIRAF in the new directory or most people just create a
working directory they always use to log in and store images.Cheers,
-Mike

Anonymous: Guest

04/19/2001 10:45PM

>From jonfa@bellsouth.net Sat Apr 21 14:07:01 2001
Sender: iraf@jxmls04.se.mediaone.net
Date: Sat, 21 Apr 2001 17:04:40 -0400
From: Jon Faranda <jonfa@bellsouth.net>
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: installation helpHi Mike,This morning when I went to load an image DS9 crashes and I get an
error. This is what I am doing:I open DS9
Then I run the cl command to open iraf
I type cl>reset stdimage = imt1024
cl>display image.fit 1 #image.fit is any imageThe error I get is: ERROR: Write to IPC with no readerIt closes DS9 and returns me to the cl prompt. It worked fine last
night, but now I cannot get it to work.Also, When I run the sysinfo script I notice some errors and warnings,
but it runs through the screen too fast. is there a way to slow it down
so I can read it step-by-step and report to you what it says?ThanksJon Faranda
jonfa@bellsouth.net
>From jonfa@bellsouth.net Sat Apr 21 14:26:06 2001
Date: Sat, 21 Apr 2001 17:23:40 -0400
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: installation helpHi Mike,I ran the sysinfo script again and I get at the end of it syaing:Tests Passed: 30
warnings: 10
Errors: 4This can't be good.Jon Faranda
jonfa@bellsouth.net
>From fitz Sat Apr 21 21:19:54 2001
To: jonfa@bellsouth.net
Subject: Re: installation helpHi Jon,> I open DS9 Then I run the cl command to open iraf
> I type cl>reset stdimage = imt1024
> cl>display image.fit 1 #image.fit is any image
>
> The error I get is: ERROR: Write to IPC with no reader The error message is misleading in that you got it because DS9
died for some reason, and the iraf task suddenly lost it's connection
(i.e. the "reader"). Why DS9 died is the question. This might have
happened if there was no /usr/local/lib/imtoolrc link (is there?) and
you were using the larger frame buffer size today and imt512 yesterday.
In that case see my earlier mail about why you might not have this
link.> Also, When I run the sysinfo script I notice some errors and warnings,
> but it runs through the screen too fast. is there a way to slow it down
> so I can read it step-by-step and report to you what it says? You can save the messages by redirecting the output to a file
and then just paging that. For example, try any of the following % sysinfo > spool
% less spool
or
% sysinfo | less> I ran the sysinfo script again and I get at the end of it syaing:
>
> Tests Passed: 30
> Warnings: 10
> Errors: 4
>
> This can't be good. It's not all bad either. Warnings include things like a mention
that you could optionally clean up some of the $iraf/unix/bin directories
to reclaim disk space, an Error might indicate iraf networking isn't
enabled (but it might not be configured yet). You'll have to examine the
output to be sure, wherever possible the script tries to explain the error
and what to do about it.Cheers,
-Mike

Anonymous: Guest

04/19/2001 10:45PM

>From jonfa@bellsouth.net Sat Apr 21 23:01:40 2001
From: Jon Faranda <jonfa@bellsouth.net>
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: installation helpHi Mike,You mentioned the imtoolrc link. No, it isn't there and that was one of
the error messages reported by the sysinfo script. How do I create this?Thanks.>From fitz Sat Apr 21 23:08:10 2001
To: jonfa@bellsouth.net
Subject: Re: installation helpHi Jon,
The imtoolrc is normally created
by the iraf install script but only of the /usr/local/lib directory
existed already. There was also a typo in the PC-IRAF install script (and
extra logical or (i.e. '||') at line 515) which prevents this. If you
don't have the file you can rerun the install script (after making a
/usr/local/lib directory or fixing the typo as needed), or if you don't
have permission to do that just copy the dev$imtoolrc to your unix login
directory as ".imtoolrc" and restart the server. Without this file all
you can use is the imt512 frame buffer.Cheers,
-Mike>From jonfa@bellsouth.net Sat Apr 21 23:42:21 2001
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: installation helpHi Mike,I reran the install script after correcting the || problem. It works
fine now when I use the int1024 buffer. I still that error: Unable to
open parameter file `uparm$tvdisply.par`>From fitz Sat Apr 21 23:45:15 2001
To: jonfa@bellsouth.net
Subject: Re: installation helpThat's usually a permissions or path problem. E.g., you ran the MKIRAF
as 'iraf' and so it owns the login.cl file and uparm directory, but
you're logged in now as yourself and trying to use the same files. Or,
you copied the login.cl rather than run a new MKIRAF in the new location,
this fails because the 'uparm$' logical path is defined when mkiraf is
run. It's not fatal either way, it just means your parameters won't be
saved after running the task.>From jonfa@bellsouth.net Sat Apr 21 23:46:53 2001
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: installation helpOk it works if I use the 512 buffer. I do, however, get a message
saying:Unable to open parameter file 'uparm$tvdisply.par' ????? I have no
clue what this means, but it does display the image ok.You wrote;
or if you don't
have permission to do that just copy the dev$imtoolrc to your unix logindirectory as ".imtoolrc" and restart the server. Without this file all
you can use is the imt512 frame buffer.Where is the imtoolrc? And when you say unix loggin directory do you
mean /iraf/iraf/unix directory?
The /usr/local/lib directory was already created when iraf was
installed, but the imtoolrc wasn't there. I will try correcting the
install script and rerunning.>From jonfa@bellsouth.net Sat Apr 21 23:48:48 2001
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: installation helpShould I rerun mkiraf as the iraf user and not root like I did? Is it
allowed?>From fitz Sat Apr 21 23:51:44 2001
To: jonfa@bellsouth.net
Subject: Re: installation helpAny user can run MKIRAF, and in general the iraf user account is only
needed when installing or maintaining the system. You should log in
as yourself and do a MKIRAF in your account directory and use that.When I say "unix login directory" I'm referring to your login directory
outside of iraf, e.g. log in to linux and you're in /home/jon or some
such. The "dev$imtoolrc" file is /home/iraf/iraf/dev/imtoolrc on your
machine, which you would copy to /home/jon/.imtoolrc. >From jonfa@bellsouth.net Sat Apr 21 23:59:48 2001
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: installation helpOk! Thanks for the quick help. I understand the file arrangement now.
Time to learn the commands.......Jon

Anonymous: Guest

04/19/2001 10:45PM

>From fitz Mon Apr 23 16:11:29 2001
From: Mike Fitzpatrick <fitz>
Subject: Re: installation helpHi Jon,> When I try to plot an image all I get are random characters and numbers
> running down the screen. I imagine that this is due to not having
> ximtool open correct?

This means that iraf thinks you're using one type of terminal
(e.g. and xgterm or xterm), but in fact you're using something else. Since
you installed the X11IRAF stuff I'd recommend you just use an xgterm
when logging into iraf (e.g. type "xgterm" to start the xgterm window, and
in that window go to your iraf login directory and do a "cl"). Some
terminal windows such as RXVT don't support graphics at all, but even if
you're using an Xterm (which does do graphics) iraf may be sending the
wrong escape codes. You enter the terminal type when you first do a
MKIRAF, you can use e.g. "stty xgterm" to reset the type once logged in
or "show stdgraph" to see what the current setting is. > If I try to activate ximtool I get the BadMatch error you warned me about.
> However, I cannot seem to start my xserver in 8 or 16 bit mode. Where
> should I type "startx -- -bpp8"??? Do I comtrol-alt-F# to a plain command
> prompt or simply type it at a terminal prompt from my desktop? If I try
> it at the desktop I get an error stating: Unrecognized option -bpp8. The command is actually "-bpp 8" not "-bpp8". If you don't use a
graphical login then you would type this startx command at the console
when you first log in. If you do use xdm/kdm to have a graphical login
then the server is already running in it's default mode and you either
need to Ctrl-Alt-F# to switch to a different console, or you can edit the
/etc/X11/xdm/Xservers file as root and add the "-bpp 8" option to the last
line of the file and reboot. Note that DS9 works in 24-bit mode so that's
another alternative if you don't want to switch depths.> Is using ximtool the only way to do graphics such as plots?
XImtool is only used for image display, graphics are done in the
terminal window.Cheers,
-Mike>From jonfa@bellsouth.net Mon Apr 23 16:21:25 2001
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: installation helpHi Mike,Thanks for the information. I got it to work by typing xgterm as you
suggested. I can now plot images and other things. Funny, when I
executed the mkiraf I did tell it xgterm and when it loads iraf it says
loading xgterm??? Simply typing xgterm before the cl command is an easy
fix. Thanks!>From fitz Mon Apr 23 16:28:11 2001
To: jonfa@bellsouth.net
Subject: Re: installation help The 'xgterm' you reply in MKIRAF is just used to tell iraf what
kind of terminal you are using, it doesn't actually start it as part of
the login. In general, starting the windows (the terminal or display
server) is left to the user.>From jonfa@bellsouth.net Mon Apr 23 16:48:27 2001
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: installation helpMike,Thanks for the help these past couple of days. If possible can you give
me a couple of quick commands to do simple calibration? For example, say
I had 5 images of a star field and 5 dark frames. How would I median
combine the dark frames to produce a master dark frame and then subtract
this new master dark frame from the light images and save them? If I
have a template to go by I can figure it out for bias and flats too.This is under ccdred command in the noao directory, correct? Are there
any links on calibrating images on the noao website?>From fitz Mon Apr 23 16:55:01 2001
To: jonfa@bellsouth.net
Subject: Re: installation helpJon,
The best thing would be to read something like the "User's Guide
to CCD Reductions with IRAF" by Phil Massey at ftp://iraf.noao.edu/iraf/docs/ccduser3.ps.Z(compressed postscript, so download in binary mode). All the other cookbooks
for various reductions are available in that same directory, see the
README file for a table of contents or the web page at http://iraf.noao.edu/docsfor a categorized listing. The CCDPROC command will do most of the
processing.
Another thing to check would be the tutorials we have available
from the /iraf/misc archive directory as exer211.tar.Z. They'll lead you
through some of the basics of processing, the cookbooks go into more depth.Cheers,
-Mike>From jonfa@bellsouth.net Mon Apr 23 17:10:02 2001
From: Jon Faranda <jonfa@bellsouth.net>
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: installation helpMike,I downloaded the GUI's extras that were available for redhat
(guiapps-bin.redhat). After unpacking it where do the .e files get
placed?Jon Faranda
jonfa@bellsouth.net
>From fitz Mon Apr 23 17:46:26 2001
To: jonfa@bellsouth.net
Subject: Re: installation helpJon,
External packages are usually distributed as source tarfiles
named something like pkg.tar.Z, and prebuilt binaries pkg-bin.arch.Z.
Both are compressed tar files. You need the pkg.tar.Z in all cases
and can build the package from sources that way, you can also get
the prebuilt binaries and then just unpack those in the package bin
directory. So for example you would unpack guiapps.tar.Z in the
/home/iraf/extern/guiapps directory (which you create), and the
guiapps-bin.redhat.Z file in the /home/iraf/extern/guiapps/bin.redhat
directory. In either case, see the guiapps.readme file for the installation
instructions in more detail.Cheers,
-Mike