Installation Instructions for the Digiphotx Package --------------------------------------------------------------- The IRAF external package, DIGIPHOTX (a new version of the DIGIPHOT package), is being made available prior to its first official release in IRAF 2.10.3. DIGIPHOTX contains: 1) a new version of the DAOPHOT package, DAOPHOTX, which is the IRAF implementation of Peter Stetson's DAOPHOT II package, 2) a new curve of growth analysis task in the PHOTCALX package, 3) several new tasks in the PTOOLSX package, 4) minor enhancements and bug fixes to existing tasks that have been discovered since the last exported version. The installation instructions that follow describe how to retrieve the DIGIPHOTX archive file, unpack the source files, build, and link the package. Some DIGIPHOTX tasks make use of the STSDAS TABLES package library routines. In order to successfully link all the DIGIPHOTX executables, the STSDAS TABLES package must be installed. A copy of the ST TABLES package retrieval and installation instructions is included at the end of the file. If you have any questions about or problems with the sofware, please contact the author (602-325-9221) or davis@noao.edu [arch] In the following steps you will need to know the IRAF architecture identifier for your IRAF installation. This identifier is similar to the host operating system type. The identifiers are things like "ssun" for Solaris, "alpha" for Dec Alpha, and "linux" or "redhat" for most Linux systems. The IRAF architecture identifier is defined when you run IRAF. Start the CL and then type cl> show arch .ssun This is the value you need to know is without the leading '.'; i.e. the IRAF architecture is "ssun" in the above example. [1-site] If you are installing the package for site use login as the 'iraf' user and edit the IRAF file defining the packages, i.e. hlib$extern.pkg % cd $hlib % vi extern.pkg Define the environment variables digiphotx to be the pathname to the digiphotx package root directory. The UNIX pathnames MUST be terminated with a '/'. Edit extern.pkg to include the following. reset digiphotx = //digiphotx/ task digiphotx.pkg = digiphotx$digiphotx.cl Where "" is the place you unpacked the package distribution files. Near the end of the extern.pkg file, update the definition of helpdb so it includes the digiphotx help database, copying the syntax already used in the string. Add this line before the line containing a closing quote: ,digiphotx$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 (needed in order to build the package from the source code). Note that pathnames must end with '/'. For example: % setenv digiphotx /local/digiphotx/ In your login.cl or loginuser.cl file make the following definitions somewhere before the "keep" statement. reset digiphotx = /local/digiphotx/ task digiphotx.pkg = digiphotx$digiphotx.cl printf ("reset helpdb=%s,digiphotx$lib/helpdb.mip\nkeep\n", envget("helpdb")) | cl flpr If you will be compiling the package, as opposed to installing a binary distribution, then you need to define various environment variables. The following is for Unix/csh which is the main supported environment. # Example % setenv iraf /iraf/iraf/ # Example path to IRAF root % source $iraf/unix/hlib/irafuser.csh # Define rest of environment % setenv IRAFARCH ssun # IRAF architecture where you need to supply the appropriate path to the IRAF installation root in the first step and the IRAF architecture identifier for your machine in the last step. [2] Login into IRAF. Create a directory to contain the package files. These directory should be outside the standard IRAF dir- ectory tree. cl> mkdir digiphotx$ cl> cd digiphotx [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 where the compressed files have the ".Z" extension. Files with ".gz" or ".tgz" can be handled similarly. cl> ftp iraf.noao.edu (140.252.1.1) login: anonymous password: [your email address] ftp> cd iraf/extern ftp> get digiphotx.readme ftp> binary ftp> get digiphotx.tar.Z ftp> get digiphotx-bin..tar.Z (optional) or .... ftp> get digiphotx-bin..tar.gz (optional) ftp> quit cl> !uncompress digiphotx.tar cl> !uncompress digiphotx-bin..tar (optional) The readme file contains these instructions. The in the optional executable distribution is replaced by the IRAF architecture identification for your computer. Upon request the tar file(s) may be otained on tape for a service charge. In this case you would mount the tape use rtar to ext- ract the tar files. [4] Extract the source files from the tar archive using 'rtar". cl> softools so> rtar -xrf digiphotx.tar so> bye On some systems, an error message will appear ("Copy 'bin.generic' to './bin fails") which can be ignored. 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 or when the binaries are installed. If the binary executables have been obtained these are now extracted into the appropriate bin. directory. # Example of sparc installation. cl> cd digiphotx cl> rtar -xrf digiphotx-bin.sparc.tar # Creates bin.sparc directory The various tar files can be deleted once they have been successfully installed. [5] For a source installation you now have to build the package executable(s). First go to the package root directory with cl> cd digiphotx If you are updating to a newer version and you earlier built the libraries and executables it is necessary to delete these. Otherwise, depending on the dates of files in the new version and the locally built libraries, it may cause the new version to be ignored. To do this the package is configured "generic" which puts all the binary files in one binary directory, the files are deleted and then you continue in the same way as a completely new installation. cl> mkpkg -p digiphotx generic cl> delete bin./* # Substitute sparc, ssun, alpha, etc. Configure the package for the particular architecture to be built. cl> mkpkg -p digiphotx # Substitute sparc, ssun, alpha, etc. This will change the bin link from bin.generic to bin.. The binary directory will be created if not present. If an error occurs in setting the architecture then you may need to add an entry to the file "mkpkg". Just follow the examples in the file. To create the executables and move them to the binary directory cl> mkpkg -p digiphotx # build executables cl> mkpkg -p digiphotx generic # optionally restore generic setting Check for errors. If the executables are not moved to the binary directory then step [1] to define the path for the package 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.