This package contains the suite of packages developed at the RGO for the reduction of data from ING telescopes. Included below are installation instructions. If you have any problems in installing this, please contact Jim Lewis via email (jrl@ast.cam.ac.uk). Note that before you can install the rgo package you'll need to have the tables package installed! [1] The package is distributed as a tar archive; IRAF is distributed with a tar reader. The tar archive may be obtained by anonymous ftp To obtain the package via ftp (assuming a UNIX computer): % ftp ftp.ast.cam.ac.uk login: anonymous password: [your email address] ftp> cd /pub/jrl/iraf ftp> get README.rgo ftp> binary ftp> get rgo.tar.gz ftp> quit % gunzip rgo.tar.gz The readme.rgo file contains these instructions. [2] Create a directory to contain the rgo external package files. This directory should be outside the IRAF directory tree and must be owned by the IRAF account. In the following examples, this root directory is named usr1:[rgo] (VMS) or /local/rgo/ (UNIX). Make the appropriate file name substitutions for your site. [3] Log in as IRAF and edit the extern.pkg file in the hlib$ directory to define the package to the CL. From the IRAF account, outside the CL, you can move to this directory with the commands: $ set def irafhlib # VMS example % cd $hlib # UNIX example Define the environment variable rgo to be the pathname to the rgo root directory. The '$' character must be escaped in the VMS pathname; UNIX pathnames must be terminated with a '/'. Edit extern.pkg to include: reset rgo = usr\$1:[rgo] # VMS example reset rgo = /local/rgo/ # UNIX example task $rgo.pkg = rgo$rgo.cl Near the end of the hlib$extern.pkg file, update the definition of helpdb so it includes the rgo help database, copying the syntax already used in the string. Add this line before the line containing a closing quote: ,rgo$lib/helpdb.mip\ NOTE: In IRAF V2.8 the length of the helpdb string cannot exceede 160 characters. A helpdb string longer than 160 characters will cause the CL startup process to fail. [4] Log into the CL from the IRAF account and unpack the archive file. Change directories to the rgo root directory created above and use 'rtar': cl> cd rgo cl> softools cl> rtar -xrf where is the host name of the archive file or the IRAF tape device for tape distributions. On VMS systems, an error message will appear ("Copy 'bin.generic' to './bin fails") which can be ignored. Also on VMS systems, the four bin.'mach' directories created by rtar under [rgo.bin] can be deleted. UNIX sites should leave the symbolic link 'bin' in the RGO root directory pointing to 'bin.generic' but can delete any of the bin.`mach' directories that won't be used. The archive file can be deleted once the package has been successfully installed. [5] When the archive has been unpacked, build the RGO package executable. Define the system architecture with the command: cl> mkpkg -p rgo ssun (Sun running Solaris) or cl> mkpkg -p rgo sparc (Sun running SunOS) or cl> mkpkg -p rgo alpha (Dec Alpha machine) The compilation and linking of the RGO package is done using the following command: cl> mkpkg -p rgo -p noao -p tables update >& spool & NOTE: On systems that concurrently support different architectures (e.g., Suns, Convex), you must configure the system for the desired architecture before issuing the above command. SUN/IRAF sites must execute a pair of 'mkpkg' commands for each supported architecture type. The Unix environment variable IRAFARCH must be set as well before compiling. For example: # Assuming IRAFARCH is set to ssun (Sun running Solaris) cl> mkpkg -p rgo ssun cl> mkpkg -p rgo -p noao -p tables update >& rgo.ssun & # Now reset IRAFARCH to f68881 before continuing cl> mkpkg -p rgo f68881 cl> mkpkg -p rgo -p noao -p tables update >& rgo.f68881 & The spool file(s) should be reviewed upon completion to make sure there were no errors. This can be done with: cl> mkpkg summary