INSTALLATION (Sep97) ifocas INSTALLATION (Sep97) IFOCAS: IRAF FAINT OBJECT CLASSIFICATION AND ANALYSIS SYSTEM Release Notes and Installation Instructions SUMMARY The IFOCAS external package is used to detect and catalog objects in images. RELEASE INFORMATION April 2001 Increase the maximum size line for DETECT to 16000. September 1997 Alpha test version of FOCAS layered on the IRAF system. Requires V2.10.3 or later. INSTALLATION INSTRUCTIONS Installation of this external package consists of obtaining the files, creating a directory containing the package, compiling the executables or installing precompiled executables, and defining the environment to load and run the package. The package may be installed for a site or as a personal installation. If you need help with these installation instructions contact iraf@noao.edu or call the IRAF HOTLINE at 520-318-8160. [1-site] If you are installing the package for site use login as IRAF and edit the IRAF file defining the packages. $ set def irafhlib # VMS example % cd $hlib # UNIX example Define the environment variable ifocas to be the pathname to the ifocas root directory. The '$' character must be escaped in the VMS pathname and UNIX pathnames must be terminated with a '/'. Edit extern.pkg to include the following. reset ifocas = usr\$1:[ifocas] # VMS example reset ifocas = /local/ifocas/ # UNIX example task ifocas.pkg = ifocas$ifocas.cl Near the end of the hlib$extern.pkg file, update the definition of helpdb so it includes the ifocas help database, copying the syntax already used in the string. Add this line before the line containing a closing quote: ,ifocas$lib/helpdb.mip\ [1-personal] If you are installing the package for personal use define a host environment variable with the pathname of the directory where the package will be located. Note that Unix pathnames must end with '/'. For example: % setenv ifocas /local/ifocas/ In your login.cl or loginuser.cl file make the following definitions somewhere before the "keep" statement. reset ifocas = /local/ifocas/ task ifocas.pkg = ifocas$ifocas.cl printf ("reset helpdb=%s,ifocas$lib/helpdb.mip\nkeep\n", envget("helpdb")) | cl flpr [2] Login into IRAF. Create a directory to contain the package files. This directory should be outside the standard IRAF directory tree. cl> mkdir ifocas$ cl> cd ifocas [3] The package is distributed as a tar archive for the sources and, as an optional convenience, a tar archive of the executables for select host computers. Note that IRAF includes a tar reader. The tar file(s) are most commonly obtained via anonymous ftp. Below is an example from a Unix machine. cl> ftp iraf.noao.edu (140.252.1.1) login: anonymous password: [your email address] ftp> cd iraf/extern ftp> get ifocas.readme ftp> binary ftp> get ifocas.tar.Z ftp> get ifocas-bin..Z ftp> quit cl> !uncompress ifocas.tar cl> !uncompress ifocas-bin. The readme file contains these instructions. The in the optional executable distribution is replaced by the standard system identification for your computer (sparc, ssun, alpha, linux, etc.). Upon request the tar file(s) may be otained on tape for a service charge. In this case you would mount the tape and specify the device name in the next step. [4] Extract the source files from the tar archive using 'rtar". cl> softools so> rtar -xrf ifocas.tar so> bye On some systems, an error message will appear ("Copy 'bin.generic' to './bin fails") which can be ignored. Also on VMS systems, the various bin.'mach' directories created by rtar can be deleted. UNIX sites should leave the symbolic link 'bin' in the package root directory pointing to 'bin.generic' but can delete any of the bin. directories that won't be used. If there is no binary directory for the system you are installing it will be created when the package is compiled later. If the binary executables have been obtained these are now extracted into the appropriate bin. directory. # Example of sparc installation. cl> cd ifocas cl> rtar -xrf ifocas-bin.sparc The archive file(s) can be deleted once the package has been successfully installed or the tape device can be freed. [5] For a source installation you now have to build the package executable(s). First you configure the package for the particular architecture. To check the architecture names you can look at the mkpkg file. cl> cd ifocas cl> mkpkg # Substitute sparc, ssun, alpha, etc. cl> mkpkg -p ifocas cl> mkpkg generic This will change the bin link from bin.generic to bin.. The binary directory will be created if not present. Then any executables are compiled and and moved to the binary directory. Check for errors. If the executables are not moved to the binary directory then step [1] was not done correctly. The last step restores the package to a generic configuration. This is not necessary if you will only have one architecture for the package. This should complete the installation. You can now load the package and begin testing and use.