Installation Instructions for the MX Software Package Version 15 September 1995 MXPACKAGE -- A suite of IRAF based packages developed at Steward Observatory, University of Arizona, Tucson, Arizona. Contact J. M. Hill for more information. jhill@as.arizona.edu mxreduce data reduction for the MX Spectrometer mxcoord coordinate processing for the MX Spectrometer mxobserve observing with the MX Spectrometer and ccd mxproto miscellaneous prototype quality tasks The MX Spectrometer reduction package, MXPACKAGE, is being distributed separately from the IRAF V2.10 distribution. This package is being made available for use on a user-beware basis. This is NOT an officially supported IRAF package in any sense of the word, but it follows the general standards for external IRAF packages. MXPACKAGE.MXREDUCE contains assorted scripts for reducing MX Spectrometer data from two-dimensional processing through extraction and sky-subtraction. These scripts have been updated for the modifications to imred and onedspec in IRAF V2.10. The pre-V2.10 scripts compatible with V2.9 plus newimred live in MXPACKAGE.OLDREDUCE MXPACKAGE.MXCOORD contains a set of SPP programs for coordinate processing and target assignment for multifiber observations. The package was originally written for the MX Spectrometer, but it is now in the process of being adapted to deal with other multifiber instruments such as Hydra. MXPACKAGE.MXOBSERVE contains a set of SPP programs and scripts used for interfacing with the MX Spectrometer instrument on the telescope. These task send code and commands and coordinates to the microprocessor that runs the instrument (ENTERPRISE). MXPACKAGE.MXONEDSPEC AND MXPACKAGE.SPECRED contain MX specific parameter files for the general packages ONEDSPEC and SPECRED. These allow you to keep your MX parameters separated from your other IRAF work. The installation instructions that follow assume that you have copied the tar format MXPACKAGE archive onto your host machine. The method you use to copy the file (or remotely access the tar file) is OS dependent and is not discussed in this document. If your IRAF system has been stripped of the IRAF libraries (via 'mkpkg stripall') you will not be able to build the MXPACKAGE executable as described here. [1] The package is distributed as a tar archive; IRAF is distributed with a tar reader. The tar archive may be obtained by magnetic tape or anonymous ftp. For magnetic tape go to step [2] and when reading the tar archive simply mount the tape and use the tape device name for the archive name in step [4]. To obtain the package via ftp (assuming a UNIX computer): % ftp as.arizona.edu login: anonymous password: [your last name] ftp> cd pub ftp> get mxpackage.readme ftp> binary ftp> get mxpackage.tar.Z ftp> quit % ls -l *mxpackage* -rw-r--r-- 1 iraf 4895 May 14 22:57 mxpackage.readme -rw-r--r-- 1 iraf 756835 Jul 23 14:30 mxpackage.tar.Z % uncompress mxpackage.tar The mxpackage.readme file contains these instructions. A full copy of the package with Solaris binaries lives in mxpackage.big.Z. PREFERRED OPTION: (Requires IRAF account access) [2] Create a directory to contain the MXPACKAGE 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:[mxpackage] (VMS) or /local/mxpackage/ (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 mxpackage to be the pathname to the mxpackage root directory. The '$' character must be escaped in the VMS pathname; UNIX pathnames must be terminated with a '/'. Edit extern.pkg to include: reset mxpackage = usr\$1:[mxpackage] # VMS example reset mxpackage = /local/mxpackage/ # UNIX example task $mxpackage.pkg = mxpackage$mxpackage.cl Near the end of the hlib$extern.pkg file, update the definition of helpdb so it includes the MXPACKAGE help database, copying the syntax already used in the string. Add this line before the line containing a closing quote: ,mxpackage$lib/h.mip\ [4] Log into the CL from the IRAF account and unpack the archive file. Change directories to the MXPACKAGE root directory created above and use 'rtar': cl> cd mxpackage 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 [newimred.bin] can be deleted. UNIX sites should leave the symbolic link 'bin' in the MXPACKAGE 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 MXPACKAGE package executable. The compilation and linking of the MXPACKAGE package is done using the following command: cl> mkpkg -p mxpackage -p noao update >& mxpackage.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 ffpa cl> mkpkg -p mxpackage -p noao ffpa cl> mkpkg -p mxpackage -p noao update >& mxpackage.ffpa & cl> mkpkg -p mxpackage-p noao f68881 # Now reset IRAFARCH to f68881 before continuing cl> mkpkg -p mxpackage -p noao update >& mxpackage.f68881 & The spool file(s) should be reviewed upon completion to make sure there were no errors. ------------------------------------------------------------------------------- INSTRUCTIONS FOR INSTALLING A PRIVATE COPY OF MXPACKAGE IN YOUR OWN DIRECTORY. (assumes you have uncompressed the tar archive already) [2U] Create a directory to contain the MXPACKAGE external package files. This directory should be outside the IRAF directory tree and must be owned by the USER account. In the following examples, this root directory is named /u/joeuser/mxpackage/ (UNIX). Make the appropriate file name substitutions for your site. [3U] Log in as USER and edit the loginuser.cl file in the home directory to define the package to the CL. In your loginuser.cl file include: set mxpackage=/u/joeuser/mxpackage/ # directory containing package task mxpackage = mxpackage$mxpackage.cl # define the package reset helpdb = (envget ("helpdb") // ",mxpackage$lib/h.mip") [A bug related to IRAF in OpenWindows means that the above statements need to be located before the default loginuser.cl command: cl < iraf$/local/user/loginuser.cl We don't know why, but otherwise helpdb gets truncated. Aug 92] [4U] Log into the CL from the USER account and unpack the archive file. Change directories to the MXPACKAGE root directory created above and use 'rtar': cl> cd mxpackage cl> softools cl> rtar -xrf mxpackage.tar [5U] Remove the tar archive to save disk space. cl> delete mxpackage.tar [6U] Define a UNIX environment variable for MXPACKAGE before getting into the CL. (You might put this command in your .login file.) This is needed because your personal package is not defined in hlib$extern.pkg and therefore mkpkg cannot interpret the "-p mxpackage" part of the command line in the next step. % setenv mxpackage /u/joeuser/mxpackage/ If this variable is not set correctly, mxpackagebin$ will not be properly defined and the executables will not end up in the bin$ directory where they belong. [7U] When the archive has been unpacked, build the package executable. The compilation and linking of the MXPACKAGE package is done using the following command: cl> mkpkg -p mxpackage -p noao update >& mxpackage.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 ffpa cl> mkpkg -p mxpackage -p noao ffpa cl> mkpkg -p mxpackage -p noao update >& mxpackage.ffpa & cl> mkpkg -p mxpackage -p noao f68881 # Now reset IRAFARCH to f68881 before continuing cl> mkpkg -p mxpackage -p noao update >& mxpackage.f68881 & The spool file(s) should be reviewed upon completion to make sure there were no errors.