README FOR IRAF VERSION 2.10.4 SunOS Version Revised Wed May 22 1996 ----------------------------------------------------------------------------- 30 May 1995 Initial V2.10.4 release 12 Sep 1995 patch 1 - see "Patch 1" below 22 May 1996 patch 2 - see "Patch 2" below ----------------------------------------------------------------------------- 1. INTRODUCTION 1.1. WHAT IS SUNOS/IRAF V2.10.4? SunOS/IRAF V2.10.4 is the SunOS version of Sun/IRAF. A separate version of IRAF V2.10.4 is available for systems running Solaris. V2.10.4 is mainly a bug-fix and system support followon to the V2.10.3 release made in the summer of 1994. While V2.10.3 and V2.10.4 are similar from the point of view of the applications software, except for bug fixes and upgrades to support new systems, both include much of the new IRAF applications software developed since the original V2.10 release and similar with what will be in V2.11. 1.2 WHO SHOULD UPGRADE? Any site currently running SunOS/IRAF V2.10.3 should upgrade to V2.10.4. A site should upgrade to V2.10.4 if they are installing Solaris/IRAF and have a mixed SunOS/Solaris environment, or if they want to begin using the new capabilities and applications that will be in the upcoming V2.11 release. V2.10.4 is only available for a limited number of platforms, e.g. all Sun platforms and all new ports, including the DEC Alpha running OSF/1 and PC platforms running Linux, Solaris x86, and BSD (the latter ports should be available summer 1995). V2.11 will be available for all supported platforms. 2. INSTALLING SUNOS/IRAF The procedure for installing SunOS/IRAF is unchanged from earlier versions. Refer to the Sun/IRAF Installation Guide (suniraf.ps.Z) for detailed installation instructions. A full installation, as for a major release, will be required. There are no bug-fix patches yet for V2.10.4, merely install the entire system from scratch from the distribution files. The installation guide contains the full installation instructions (see also the notes below) but one quick pointer here: the installation will be simplified if you set up the iraf directories as follow: /iraf root of iraf related files /iraf/iraf root iraf directory (AS dist) /iraf/irafbin iraf bin dirs go here /iraf/irafbin/bin.sparc sparc binaries for core system /iraf/irafbin/noao.bin.sparc sparc binaries for noao packages /iraf/extern external packages (tables etc.) Here "" is the path where all this is located, e.g., "/u3/iraf" on the IRAF development system here at NOAO. The path can be anything, although it is best to keep it short. You might want to also set up a symbolic link "/iraf" pointing to the "/iraf" directory. This allows all iraf files to be referred to relative to /iraf, regardless of where the files actually are located. 2.1 Patch 1 (12 September 1995) Case 1: You already have the V2.10.4 system installed and you want to install the patch. Unpack patch1.tar.Z at the iraf root and upgrade the BINs. % cd $iraf % zcat patch1.tar.Z | tar -xpf - To upgrading the BINs download the new IB and NB distributions and reinstall the BINs as if you were installing for the first time. Patch 1 does not modify any site dependent files, other than the motd (to update the version information). You can install the patch file without concern that site dependent files such as the DEV files may be modified. Case 2: You are installing V2.10.4 from scratch. Just do a normal install, all of the distribution files have been regenerated to include patch1. You can ignore the patch1.tar.Z file, this is only used to upgraded older installations. 2.2 Patch 2 (22 May 1996) Patch 2 for SunOS/IRAF includes a number of minor bug fixes and enhancements. Only the sparc distribution is patched (the old Sun-3 ffpa and f68881 distributions were not updated). Case 1: You already have the V2.10.4 system installed and you want to install the patch. Unpack patch2.tar.Z at the iraf root and upgrade the BINs (install patch1 above first, excluding the BINs, if you have not yet done so): % cd $iraf % zcat patch2.tar.Z | tar -xpf - To upgrade the BINs download the new IB and NB distributions and reinstall the BINs as if you were installing for the first time. Patch 2 does not modify any site dependent files, other than the motd (to update the version information). You can install the patch file without concern that site dependent files such as the DEV files may be modified. Case 2: You are installing V2.10.4 from scratch. Just do a normal install, all of the distribution files have been regenerated to include both patch1 and patch2. You can ignore the patch1.tar.Z and patch2.tar.Z files, these are only used to upgrade older installations. 3. X11/GUI SUPPORT IRAF V2.10.4 includes full support for the X11IRAF utilities - these include xgterm for xterm-compatible terminal emulation and graphics, and ximtool for image display under X. The X11IRAF package is not included in IRAF; you need to get this and install it separately, as you would any other X software. The X11IRAF utilities are still under development and during the develop/test phase new versions are being made available on the IRAF ftp server in the scratch directory iraf.noao.edu:pub/v2103-beta. Instructions for installing and using these programs will be found in this directory. The files you may want to download from this directory are the following: xgterm current xgterm executable (SunOS) xgterm.info info file for latest xgterm xgterm.ad app-defaults file for xgterm ximtool current ximtool executable (SunOS) ximtool.info info file for latest ximtool xtapemon current xtapemon executable (SunOS) xtapemon.info info file for latest xtapemon x11iraf.tar.Z full sources for x11iraf Development of these utilities is still underway, and the executables are updated periodically as bugs are fixed. New versions with extended capabilities are added from time to time. If you use this software be sure to install the new versions as they become available. The SunOS version of V2.10.4 IRAF can also be used with SunView (gterm/imtool) or with graphics terminals - these capabilities are unchanged by the new additions. Xterm and SAOimage may also be used as in the past. Although V2.10.4 contains builtin support for IRAF applications with integrated GUIs (graphical user interfaces) none of the applications supplied with V2.10.4 currently use this facility, as the new GUI applications currently under development have not yet been installed in IRAF. Look for these to appear initially as layered packages that can be installed into V2.11. A few integrated GUI applications will appear for the first time in V2.11. For pointers on usage and to learn about new versions as they become available you can follow the "adass.iraf" newsgroups - contact iraf@noao.edu for further information if you do not know how to access these newsgroups. 3.1 THE X11 DESKTOP Although most people probably run Sun's OpenWindows on Sun platforms, this is not required. The X11IRAF utilities require only an X server and should work with any desktop or window manager, e.g. Motif mwm, twm, fvwm, and so on. 3.2 THINGS TO WATCH OUT FOR (IRAF) In general V2.10.4 is very similar to V2.10.3. We did this intentionally since this release is mostly to fix bugs and provide system support for new operating systems or compilers. Major new applications or serious changes to existing applications are being saved for the V2.11 release. An exception is the syntax of the "set node = blah" syntax, used to enable remote image display under IRAF networking. The new syntax introduced in this release requires that an exclamation be appended to the node name, e.g. cl> set node = "blah!" There have also been some changes to the calling sequences of various IRAF tasks: parameter have been added or removed, and so on. Any change like this can break a user script which calls such a task. For a summary of changes to the calling sequences of IRAF tasks see the adass.iraf.announce newsgroup or contact IRAF site support (the adass newsgroups area available directly from iraf.noao.edu via NNTP, via the IRAF Web server, or via email subscription, if your site doesn't carry them locally). 3.3 THINGS TO WATCH OUT FOR (X11) A few things to watch out for if you use IRAF with the new X11IRAF utilities. The point here is to mention briefly some of the more common problems or points of confusion people can run into. See the ".info" files supplied with the x11iraf software for further information. o Rule number zero is: you must install these applications before you can use them. They are not automatically installed by IRAF as the x11iraf programs are a separate product, not part of the IRAF distribution. The x11iraf applications are conventional X programs that must be installed in your unix X environment like other X programs. Ximtool and xtapemon are standalone and will run with only that the executable be installed. Xgterm requires that the app-defaults file also be installed. An ximtool option is to install the extended colormap directory in /usr/local/lib/imtoolcmap; this will give you more colormaps to work with in ximtool, and a place to easily add your own colormaps. o When using xgterm, be sure you have done an "stty xgterm" first! You can run IRAF under xgterm with stty set to xterm or gterm, but various capabilities will be lost. If plots come up white on black instead of in color, this probably means that you have stty set to xterm. ==> When xgterm is used correctly with V2.10.4, you should get nice colored plots on a color workstation. A black and white plot probably indicates an stty problem. <== o You should have "focus follows mouse" enabled when using the x11iraf programs, because they warp the cursor in and out of windows when entering and exiting cursor mode. For example when using imexamine the cursor is warped into the graphics or image windows when you request a graphics or image cursor. If you do not have focus-follows-mouse enabled this can be very confusing. For Sun's OpenWindows window manager, the following .Xdefaults entry will enable focus-follows-mouse mode: olwm.SetInput: followmouse o Be warned that ximtool is NOT saoimage. The SAOimage command line arguments are not recognized by ximtool. In particular, if you are running multiple ximtools on the same workstation, the procedure for doing this is different with ximtool than it is with SAOimage. For example, while ximtool still supports fifos for client-server communications, it also supports two types of sockets and it will listen on all three types of ports for client connections. To run multiple ximtools on a single host you can still set up private fifos and a private graphcap, however with ximtool it is preferable to use sockets, and the private graphcap is no longer needed. For a more complete description of the ximtool client-server i/o system refer to the ximtool.info file available with the program. Further information is available online in the adass.iraf newsgroups, in the IRAF FAQ, or by sending mail to iraf@noao.edu. o Ximtool uses a private colortable to ensure that there are enough colors to display an image. In some circumstances you may see colors change in the displayed image, or in other windows on the same screen, as the mouse is moved in and out of the ximtool image window. This is normal and happens because most workstations can only display a maximum of 256 colors simultaneously on the workstation screen (this is a hardware limitation). Ximtool goes to some trouble to avoid this color flashing and you can avoid the problem by avoiding using ximtool simultaneously with other applications that use a lot of colors, e.g. mosaic, xv, saoimage, and so on. Refer to the ximtool.info file for a more complete discussion of this problem. o Although the image device interface in V2.10.4 will work with any image display server (imtool, ximtool, saoimage, etc.) there is a limitation currently when trying to display remotely to an older version of IRAF. That is, if you run the display task in V2.10.4 and try to display to a remote host that is running an earlier version of IRAF, it won't work. You can workaround this using a private graphcap (or by adding entries to your standard graphcap), if it should be a problem. Contact us for the details if this is a problem at your site. Don't be scared off by these caveats; basic usage of the new X11 programs is for the most part straightforward and intuitive once the programs have been installed by the local IRAF or UNIX system manager. 4. SOLARIS COMPATIBILITY SunOS/IRAF V2.10.4 is V2.10.4 IRAF built on SunOS for SunOS platforms. Although SunOS/IRAF V2.10.4, like SunOS/IRAF V2.10.2, will run on a Solaris 2.3 or newer system in compatibility mode, it is preferable to run Solaris/IRAF V2.10.4 on Solaris systems. Solaris/IRAF is a native port of IRAF to Solaris, customized for Solaris, built using the SunSoft compilers, with full support for the Solaris operating system and environment. SOS4 V2.10.4 for SunOS systems SSOL V2.10.4 for Solaris systems don't confuse the above with the following, which are the old V2.10.3 distributions (if they haven't been deleted by the time you read this). old/SOS4-v2103-beta V2.10.3 for SunOS systems old/SSOL-v2103-beta V2.10.3 for Solaris systems Although SunOS/IRAF and Solaris/IRAF are identical IRAF systems from the user's point of view, meaning that all the IRAF software is the same on both systems, they are quite different systems at the host operating system level. While the SunOS binaries will run at the 99% level on Solaris in compatibility mode, the reverse is not true, i.e., Solaris binaries will not run on a SunOS system. SunOS/IRAF does not work at the 100% level on Solaris systems, e.g. there is no compiler support, and there are minor problems with things like tape allocation. Hence if a site operates both SunOS and Solaris systems in a mixed IRAF environment, it is recommended that both the SSOL and SOS4 distributions be obtained and installed separately on different (Solaris and SunOS) hosts. A single copy of an IRAF layered package can be shared by SunOS/IRAF and Solaris/IRAF systems. Build the "sparc" architecture on SunOS, and the "ssun" architecture on Solaris. Further information on building IRAF layered packages for multiple architectures can be found in the Sun/IRAF Site Manager's Guide (sunsmg.ps.Z) , and in the installation documentation for the major layered packages. Again, separate copies of IRAF will be required for the two platforms. =============================================================================== The following is the text of the original 08May92 README file for the SOS4 (SunOS) distribution. This is still accurate and contains generally useful information about downloading and installing the distribution. We include it here unchanged. In cases where there is any overlap the text above for the V2.10.4 distribution supercedes what follows. =============================================================================== README FOR IRAF VERSION 2.10 IRAF version 2.10 was frozen in late April and after a week or so or testing of the distribution files and a few final bug fixes, is being released to the public. As of this date the release related documentation is incomplete. Full, detailed system and package revisions notes files are available, as is a revisions summary for the applications packages. Still to be completed are the system revisions summary and technical papers on the new magtape i/o subsystem and the new networking subystem. The installation and site manager's guides also need to undergo minor revisions for V2.10. If you have installed version 2.9 IRAF, you should have no problem installing version 2.10. The only significant change affecting installation is the "tapecap" file (dev$tapecap) used in V2.10. See the brief notes below for hints on how to configure this - note that the old "devices" file is no longer used. As always, help is available via IRAF site support if you have any problems. Alternatively you can delay the V2.10 installation until all the release related documentation is available. The initial release of V2.10 IRAF is known as V2.10.0. This is a major release of IRAF, containing many (literally thousands) of systems and package revisions, as well as major new or revised subsystems and applications packages and tasks. Although the system has undergone months of testing, it is inevitable that bugs will continue to be found and fixed. Please report any problems you experience with the system. There will be a bug fix update in approximaely 1-3 months (V2.10.1) fixing all the bugs discovered after the initial release. Additional V2.10 patch-upgrades will be released over the next year or two before the next major release of IRAF is issued. Although there is a great deal of new systems and applications software in version 2.10 IRAF, it still "looks" like previous versions of IRAF. In particular, for Sun/IRAF, the situation for window support has not yet changed, i.e., you have a choice of Sunview (with gterm/imtool) or X11 (with xterm/saoimage). Work is in progress on both graphics user interfaces for IRAF, and on general support for X11 for grapihics and imaging. Due to our limited resources, it was not possible to complete this work in time for the initital V2.10 release, at least not without further delaying the release. An all-new X11 support kit containing the X11 help browser, XGTERM (a replacement for XTERM much better tuned for IRAF applications) and other utiltities will follow later this year. TAPECAP CONFIGURATION A technical paper is planned which will fully document the new IRAF magtape system. Most users however, will not need such detailed documentation in order to configure the V2.10 magtape system for their local tape drives. What you must do after the initial install is edit the file dev$tapecap. The old dev$devices file is no longer used, but keep it around for reference, so that you can remember which unix device names referred to what IRAF device names (usually "mta", "mtb", etc.). The format of the tapecap file is standard BSD UNIX "termcap" format, like the IRAF termcap and graphcap files. The only difference is that it describes magtape devices. Refer to unix termcap documentation for a full description of this file format. Alternatively, if you inspect the file and use the existing entries as examples, it should not be hard to figure out how to modify the file for your local devices. The V2.10 tapecap file is broken into two major sections. The top of the file contains host machine or site specific entries - these are the entries which will have to be changed for your site. The bottom of the file, begining with "# Unit assignments", is fairly generic and should be usable at most Sun/IRAF sites. Although the list of supported devices is not exhaustive, the odds are that generic entries for your local devices are already present in this list. To interface a local device you don't actually *have* to do anything - you can just use the generic device entries. For example, to access the HP 1/2 inch drive on unit 0, you could refer to device "mthp0" in your IRAF DATAIO commands. For backwards compatibility however, it is often desirable to provide device aliases such as "mta", "mtb", etc. referring to the logical IRAF devices in use at your site. This is done by adding site specific alias for your local site. Refer to the entries at the top of the file for examples. Note that in v2.10 IRAF, although you can still allocate a tape drive before accessing it, and the allocation facilities have not changed substantially, you no longer *have* to allocate a drive before accessing it. If you don't allocate the drive DEVSTATUS will warn that it has not been allocated, but you will still be able to access it. The new magtape system has many other features, and is adaptable to devices not already supported in the tapecap file. These will be documented in the reference manual when it becomes available. Again, please contact IRAF site support if you experience problems interfacing your local devices. The remainder of this README is largely taken from the V2.9 README, but should still be valid. Refer to the installation and site manager's guides for detailed instructions. THE SUN/IRAF NETWORK DISTRIBUTION This directory and its subdirectories contains the Sun/IRAF distribution, for all Sun-3s and Sun-4s (including sparcstations) running SunOS-4. The V2.9 binary distribution was compiled under SunOS 4.0.3. The Sun386i is a substantially different system and hence has its own distribution; this is in the directory v29/S386 (../S386). README This file. as.sos4.gen AS.SOS4.GEN (all sources) ib.sos4.f68 IB.SOS4.F68 (core system, f68881 binaries) ib.sos4.fpa IB.SOS4.FPA (core system, ffpa binaries) ib.sos4.spc IB.SOS4.SPC (core system, sparc binaries) nb.sos4.f68 NB.SOS4.F68 (NOAO packages, f68881 binaries) nb.sos4.fpa NB.SOS4.FPA (NOAO packages, ffpa binaries) nb.sos4.spc NB.SOS4.SPC (NOAO packages, sparc binaries) # See the v2.9 distribution or iraf/docs for these files. #gterm.man.Z GTERM manual page source #gterm.ps.Z GTERM manual page, Postscript output #imtool.man.Z IMTOOL manual page source #imtool.ps.Z IMTOOL manual page, Postscript output # The following have been updated for V2.10. suniraf.ms.Z Sun/IRAF installation guide source suniraf.ps.Z Sun/IRAF installation guide, Postscript output sunsmg.ms.Z Sun/IRAF Site Manager's Guide source sunsmg.ps.Z Sun/IRAF Site Manager's Guide, Postscript zzmake Build utility (not part of distribution) To install Sun/IRAF you will need to transfer the AS.SOS4.GEN file plus the binaries for whatever systems you want to run IRAF on. For example, to install IRAF on a Sun-4 or a sparcstation, you will need AS.SOS4.GEN and the sparc binaries for the core system and NOAO packages, files IB.SOS4.SPC and NB.SOS4.SPC. REGISTERING YOUR SITE While the network archive makes it easier to get IRAF, it also makes it harder for us to track IRAF usage by the community. We need this information, e.g., to help obtain funding to continue to develop and support IRAF for the community. PLEASE REGISTER YOUR SITE IF YOU USE IRAF! This takes only a moment; all you need do is fill out the form in the v29/REGISTER file and mail it to iraf-requests@noao.edu. As an added benefit you will get on the IRAF mailing list, and will receive the IRAF Newsletter and other IRAF mail. You can also now register via the IRAF Web pages at http://iraf.noao.edu. TRANSFERRING THE FILES Each distribution file is stored in a subdirectory containing the compressed and split distribution file, a CHECKSUMS file, and a FILES.Z file. The distribution file is a UNIX TAR file containing one or more directory trees from the IRAF system. To facilitate transfers over unreliable network connections, the distribution file is split into a number of smaller (512 Kb) files. The files can be transferred as follows. These examples are for the SunOS version of FTP. o If you did not start up FTP as "ftp -i", exit and restart it with the "-i" switch. This is necessary to be able to do bulk transfers without having to answer annoying and unnecessary yes or no queries for each individual file. o On the local system, create a subdirectory for each distribution file you want to transfer, e.g., ftp> !mkdir as.sos4.gen o Set the current directory on both the local and remote systems. ftp> cd as.sos4.gen ftp> lcd as.sos4.gen o Transfer all the files in the distribution file directory. A binary transfer is required for the compressed tar files, and will work for the text files as well since both systems are UNIX. ftp> binary ftp> mget * If problems are encountered, use the CHECKSUMS file to verify that any subfiles already transferred are correct. Delete any partially transferred subfiles and restart the transfer (by subfile we mean the 512 Kb files with extensions .00, .01, .02 etc. files making up the distribution file). Both BSD (Sun) and SYS5 checksums are given. The SunOS command "sum" will compute the checksum of a file. Once all the files have been transferred the subfiles can be concatenated and uncompressed to reconstruct the original distribution TAR file, e.g.: % cat as.* | uncompress | tar -tvf - would list the contents of the distribution file. Such a listing is provided in the file FILES.Z in each distribution file directory. An easy way to look at a compressed text file such as FILES.Z is with "zcat": % zcat FILES.Z | page INSTALLING SUN/IRAF Complete instructions for installing and configuring Sun/IRAF are given in the Sun/IRAF Installation Guide and Sun/IRAF Site Manager's Guide, compressed Postscript versions of which are given in the files suniraf.ps.Z and sunsmg.ps.Z. On most BSD networks containing a Postscript printer, a hardcopy version of the manual can be obtained with a command such as % zcat suniraf.ps.Z | lpr [-P] where is the name of the local printer device you want the manual to be printed on. Troff source for the manuals is also provided for sites that do not have ready access to a Postscript printer. Installation is as described in the manuals except that, since you will be installing a network distribution, you install from the compressed and split disk version of the distribution file instead of from tape. For example, to restore AS.SOS4.GEN to the remote directory $iraf, while logged in as user "iraf": % whoami iraf % cd SOS4/as.sos4.gen % cat as.* | uncompress | (cd $iraf; tar -xpf -) This example assumes that "iraf" is defined in your unix environment (if not, just type in the pathname of the iraf root directory instead). As a variation, suppose the distribution files are stored on the local system "alex" in directory /tmp2/SOS4 and you want to install iraf in the root directory /usr/iraf on the remote system "fred": % cd /tmp2/SOS4/as.sos4.gen % cat as.* | uncompress | rsh fred "cd /usr/iraf; tar -xpf -" Or, if you are logged in on fred instead: % cd /usr/iraf % rsh -n alex "cat /tmp2/SOS4/as.sos4.gen/as.*" |\ uncompress | tar -xpf - (The -n argument allows you to suspend the rsh without having the job stop waiting for terminal input). Note that, even if the two systems are connected by NFS, it is always safer, faster, and more efficient to use rsh instead of NFS for file transfers such as these. The BIN directories are restored in much the same fashion, e.g., % cd /usr/iraf % rm bin.sparc; mkdir bin.sparc % cd bin.sparc % (cd /tmp2/SOS4/ib.sos4.spc; cat ib.*) | uncompress | tar -xpf - % cd /usr/iraf/noao % rm bin.sparc; mkdir bin.sparc % cd bin.sparc % (cd /tmp2/SOS4/nb.sos4.spc; cat nb.*) | uncompress | tar -xpf - If multiple architecture support is desired you need only create additional sets of BIN directories, e.g., bin.68881, bin.ffpa, and so on. Note that the system as shipped will contain existing symbolic links with these names which should be deleted (you can use a symbolic link to store the BIN directory on another disk if space is tight). DO NOT delete the "bin.generic" directory, or modify the symbolic links "iraf$bin" and "iraf$noao/bin" to point to anything other than bin.generic. Please read the installation guide for more complete instructions regarding the installation. There is more to installing and configuring IRAF than just restoring the files to disk as discussed in these examples. ----------------------------------------------------------------------------- POST DISTRIBUTION NOTES - When users find things we note them here. Thu Sep 21 11:53:15 MST 1995 Compilation failed with "-lU77" not found when compiling from the IRAF account. Traced to the presence of an old "f77" in /usr/local/bin. Changing the path in the .cshrc for the iraf account to set path = (. /usr/lang /usr/local/bin /usr/ucb /bin /usr/bin) fixed this problem, and is probably a better path.