iraf.net

Hi Peter,On Mon, 22 Aug 2005, Peter Teuben wrote:> I was going to try and install the new ECL based iraf. But i need to
> do this from scratch. I have a new Fedora Core 4, and it doesn't have
> much. But assuming i can't be root on it, or even make a /iraf, how can
> one install iraf? Is that still impossible? It was never impossible to install iraf without root permissions,
it was just never a default option. To do this you would setup the iraf
tree as you would for a normal install but the rather than run the install
script you'd move things by hand and define environment variables so IRAF
can be found. I'll append more detailed instructions on how to do this.> In an older (1998) document i read lines like
>
> setenv iraf /iraf/iraf/
>
> and using $iraf, hoping this would be
> possible now. I don't need any special tape access or anything like it,
> can i still install iraf in e.g. $HOME/opt/iraf See below for details, let me know if you have any problems. Note
the ECL installation needs to be done separately and perhaps also by hand,
I haven't tried th ecl install script on a personal iraf installation. Cheers,
-Mike
> It can be done but there will be some limitations. What you need
> to do is define everything in your environment rather than rely on the
> defaults. This means in your .cshrc (*not* .login) define something like
>
> setenv iraf /home/user/iraf/ # trailing '/' required
> source $iraf/unix/hlib/irafuser.csh # get aliases
> setenv IRAFARCH ssun # define architecture
>
> For building packages etc be sure you have all the dirs specified in the
> $iraf/.cshrc path in your path. You will need a directory for the iraf
> commands, something like $HOME/bin, which must also be in your path.
> The installation is done by unpacking all the files in the normal
> way under a user directory. Instead of running the install script however
> you would do it by hand as follows:
>
> 1) Edit the new iraf path into the files
>
> $iraf/unix/hlib/mkiraf.csh
> $iraf/unix/hlib/libc/iraf.h # multiple instances here!
> $iraf/unix/hlib/cl.csh
> $iraf/local/.login
> $iraf/local/.cshrc
>
> This isn't critical since the environment should supply the path,
> but it provides a backup for yourself and other users.
>
> 2) Edit the default imdir to be used in $hlib/mkiraf.csh. If you'll
> be using a HDR$ type imdir then edit it directly into hlib$login.cl.
>
> 3) Make symlinks for the iraf commands in the $HOME/bin directory you
> created, be sure you've defined the environment above:
>
> ln -s $hlib/cl.csh cl
> ln -s $hlib/mkiraf.csh mkiraf
>
> ln -s $hbin/generic.e generic
> ln -s $hbin/mkpkg.e mkpkg
> ln -s $hbin/rmbin.e rmbin
> ln -s $hbin/rmfiles.e rmfiles
> ln -s $hbin/rtar.e rtar
> ln -s $hbin/sgidispatch.e sgidispatch
> ln -s $hbin/wtar.e wtar
> ln -s $hbin/rpp.e rpp
> ln -s $hbin/xpp.e xpp
> ln -s $hbin/xyacc.e xyacc
> ln -s $hbin/xc.e xc
>
> 4) If you'll be doing image display you'll need to make a private
> copy of the frame buffer config file:
>
> % cp $iraf/dev/imtoolrc $HOME/.imtoolrc
>
> DS9 must be started using private fifos and a private graphcap
> file (see our FAQ 6.4), XImtool will work normally.
>
> Then procede with configuring printers and such. The limitations I spoke
> of deal with IRAF networking and tape allocation, neither will work but
> you may not need them.
> As you can see it may just be easier to get your sysadmin to
> create and iraf account for you and run the install script once your are
> done unpacking it.