README FOR DIGITAL UNIX IRAF VERSION 2.11 Last Updated Mon Sep 18 2000 Current Patch Level V2.11.3 ----------------------------------------------------------------------------- 23Dec97 Initial V2.11.1 release for Digital Unix on the DEC Alpha 21Aug99 ***** V2.11.2 patch ***** 14Dec99 ***** V2.11.3 patch ***** 10Feb00 V2.11.3a (applications) patch (see "patch3a" notes below) 18Sep00 V2.11.3b (misc bug fix) patch (see "patch3b" notes below) If you are INSTALLING IRAF FOR THE FIRST TIME ignore any patch files and just do a normal install from the AS, IB, and NB distributions as described in the installation guide in this directory. If you already have either the original DUNX IRAF V2.11 release (V2.11.1) or the summer 99 V2.11.2 patch installed and you are updating to V2.11.3, you have the option of either doing a full install or installing patch3.tar.Z (or patch3.tar.gz) as outlined below. In either case you must update your binaries as well (the IB and NB distributions). The December release of DUNX/IRAF is at IRAF version V2.11.3. The IRAF distribution does not itself include graphics and image visualization tools, these are distributed separately. See /iraf/x11iraf and /contrib. You should use Xgterm for any IRAF line graphics. Ximtool, SaoTNG, SAOimage, and other related image viewers may be used for image interaction. See also the post-distribution notes at the end of this file. These are continually updated after the release as any problems are encountered. ----------------------------------------------------------------------------- 1. INTRODUCTION 1.1. THE DIGITAL UNIX V2.11 RELEASE Digital Unix IRAF (DUNX/IRAF) V2.11 is a port of IRAF to DEC Alpha platforms running Digital Unix V4.x (we used V4.0 for our port). For brevity we will sometimes refer to Digital Unix V4.0 as "DU4". README This file as.dunx.gen All-Sources (main IRAF distribution) ib.dunx.sun Core system binaries for DU4 nb.dunx.sun NOAO package binaries for DU4 The distribution directories contain large compressed Tar files split into a number of modest size (e.g. 512KB) chunks, to allow recovery if the network fails during a transfer. The Installation Guide provides detailed instructions on how to use these files to install IRAF. 1.2 WHO SHOULD UPGRADE? IRAF V2.11 is a major IRAF release for all supported IRAF platforms. Support for older versions of IRAF is limited so sites running earlier versions of IRAF should update to the new version of IRAF. There may be incompatibilities between V2.11 and earlier versions of IRAF, so updating in the middle of an analysis program might not be advisable. Mixing different versions of IRAF works in most cases, but there can be complications. Large installations may want to keep and older version of IRAF around to give users time to complete their programs before switching to the new version of IRAF (e.g. here at NOAO, "cl" or "iraf" runs V2.11, and "irafo" will bring up the older V2.10.4 release). 2. INSTALLING DUNX/IRAF The procedure for installing DUNX/IRAF is unchanged from earlier versions of DUNX/IRAF and other versions of IRAF. Refer to the DUNX/IRAF Installation Guide for detailed installation instructions (see (dunxiraf.ps.Z in the distribution directory). A full installation, as this is a major release, will be required. The installation guide contains the full installation instructions (see also the notes below) but one thing is worth emphasizing here: the installation will be simplified if you set up the iraf directories as follows: /iraf root of iraf related files /iraf/iraf root iraf directory (AS dist) /iraf/irafbin iraf bin dirs go here /iraf/irafbin/bin.alpha Alpha DU4 binaries for core system /iraf/irafbin/noao.bin.alpha Alpha DU4 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 actual path to the iraf root can be anything. 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, and agrees with the default configuration used in the distribution files. NOTE: Our usual practice is to use the "-p" flag as in "tar -xpf" to unpack the distribution tar archives. Unfortunately under Digital Unix this produces a warning on each unpacked file, so we use the flags "-xf" instead, dropping the "-p". The result is that the old file access modes and groups are not preserved when the files are restored. This should be harmless for an IRAF user installation unless you have an unusual umask. (If you don't understand what this all means just follow the direction in the Installation Guide and there shouldn't be any problem). The V2.11 DUNIX/IRAF release currently supports only one architecture. The "alpha" architecture is the DU4 architecture for Alpha platforms running Digital Unix, built using the standard DU4 compilers. 3. X11/GUI SUPPORT IRAF V2.11 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 it and install it separately, as you would any other X software. X11IRAF is available in /iraf/x11iraf on the main IRAF network server (iraf.noao.edu). Other IRAF-compatible GUIs can also be used with IRAF, e.g. SAOimage, SAOtng, and IPAC SkyView. This software is continually under development and new versions appear on a timetable independent of that for the main IRAF distribution. 3.1 THE X11 DESKTOP The X11IRAF utilities will run under any X desktop. Most people will probably use DEC's default CDE-based desktop, but Motif/mwm, twm, fvwm, and so on may be used as well. As of the time of this writing, the X11IRAF utilities do not run on 24 bit truecolor screens, only 8 bit pseudocolor. Support for 24 bit screens is planned. 3.2 THINGS TO WATCH OUT FOR (IRAF) Please see the release notes for information on what has changed in V2.11, and things to watch out for. 3.3 THINGS TO WATCH OUT FOR (X11) Please see the documentation included with X11IRAF V1.0 or later releases for information on running these utilities, including common problems and how to deal with them. One thing we would like to emphasize here is that we STRONGLY suggest that you use "xgterm", not the standard "xterm" to run IRAF. Xgterm, which is included in X11IRAF, has advanced graphics capabilities developed for use with IRAF. Xterm graphics work, but not terribly well. When you start up the cl in an xgterm window, type "stty xgterm" after the CL starts up to tell it you are using an xgterm window. 4. MAGTAPE INTERFACE The DEV directory contains a default template tapecap file for DU4. If a server is configured to run IRAF for multiple network clients, you can now have multiple tapecap files, one for each host, e.g. "tapecap.foobar" for host "foobar". See the release notes for further information on this capability. 5. PRINTER INTERFACE Local printers are interfaced to IRAF using the dev$termcap file. The default printer, defined by the "printer" environment varilable in hlib$zzsetenv.def, is "lp". This uses the host system lpr with no explicit printer name given, allowing the host environment variable PRINTER to be defined in ther user's environment to direct out to the actual printer. The dev$termcap file may need to be customized to support the printers in use at your site. See the IRAF Site Manager's Guide for detailed instructions on configuration the printer interface. 6. PATCHES 6.1 DUNX/IRAF V2.11.2 - Sat Aug 21 1999 The DUNX/IRAF distribution files have been fully regenerated for V2.11.2, so one way to upgrade IRAF to V2.11.2 is to do a full install and diff/merge selected locally customized files from DEV (tapecap, graphcap, imtoolrc, devices.hlp, etc.) and HLIB (extern.pkg, mkiraf.csh, login.cl, zzsetenv.def). If you have an existing DUNX/IRAF V2.11.1 installation you have the option of installing the patch file. Note that THE V2.11.2 PATCH WILL OVERWRITE CERTAIN SITE SPECIFIC FILES. These are the following: unix/hlib/zzsetenv.def dev/graphcap dev/termcap dev/tapecap You may want to save copies of these files and diff/merge them with the new versions after installing the patch. To install the patch, login as the iraf system manager, go to the $iraf directory, and untar the patch as follows: % cd $iraf cat patch2.tar.Z | uncompress | tar -xpvf - Then diff/merge the files listed above. Next, go to the archives and download and install the IB (IRAF core system) and NB (NOAO package) binaries for the architectures your installation will support. For example, to install IB.DUNX.ALP (the DEC Alpha binaries for the core system, with the IB.DUNX.ALP distribution downloaded to the directory "/ib.dunx.alp" (where is where you created this directory): % cd $iraf/bin.alpha % pwd /iraf/irafbin/bin.alpha # (you should be here, or somewhere similar) % cat /ib.dunx.alp/ib.* | uncompress | tar -xpvf - A similar procedure is followed to install each of the other binaries. See the URL http://iraf.noao.edu/v2112revs.html for a detailed description of what is included in the patch. 6.2 DUNX/IRAF V2.11.3 - Tue Dec 14 1999 The DUNX/IRAF distribution files have been fully regenerated for V2.11.3, so one simple way to upgrade IRAF to V2.11.3 is to do a full install and diff/merge selected locally customized files from DEV (tapecap, graphcap, imtoolrc, devices.hlp, etc.) and HLIB (extern.pkg, mkiraf.csh, login.cl, zzsetenv.def). If you have an existing DUNX/IRAF V2.11.1 or V2.11.2 installation you have the option of installing the patch file. Note that THE V2.11.3 PATCH WILL OVERWRITE CERTAIN SITE SPECIFIC FILES. These are the following: unix/hlib/zzsetenv.def dev/graphcap dev/imtoolrc dev/termcap dev/tapecap You may want to save copies of these files and diff/merge them with the new versions after installing the patch. To install the patch, login as the iraf system manager, go to the $iraf directory, and untar the patch as follows: % cd $iraf cat patch3.tar.Z | uncompress | tar -xvf - Or if you have Gnu tar (e.g. gtar) and downloaded the gzipped patch, % cd $iraf gtar -xvzf patch3.tar.gz Next, go to the archives and download and install the IB (IRAF core system) and NB (NOAO package) binaries for the architectures your installation will support. For example, to install IB.DUNX.ALP (the Digital Unix/Tru64 binaries for the core system, with the IB.DUNX.ALP distribution downloaded to the directory "/ib.dunx.alp" (where is where you created this directory): % cd $iraf/bin.alpha % pwd /iraf/irafbin/bin.alpha # (you should be here, or somewhere similar) % cat /ib.dunx.alp/ib.* | uncompress | tar -xvf - A similar procedure is followed to install each of the other binaries. See the URL http://iraf.noao.edu/v2112revs.html for a detailed description of what is included in the V2.11.2 and V2.11.3 patches. Most of the new features were introduced in V2.11.2. V2.11.3 mostly consists of additional bug fixes, minor changes related to the PC-IRAF upgrades, and a few isolated minor application enhancements. The system notes file (iraf/local/notes.v211) documents these revisions in detail for the core system. 6.3 Patch3a - Feb 10 2000 Patch 3a is a small patch which fixes bugs in several of the V2.11.3 applications, including a serious one affecting onedspec.dispcor (details can be found in the buglogs). The task IMEDIT and the packages APEXTRACT, ONEDSPEC, and RV are affected by the patch. The patch files are as follows: patch3a-dunx.tar.Z patch3a for Digital Unix patch3a-dunx.tar.gz patch3a for Digital Unix (gzip compressed) The patch files contain updated executables for the given architecture. Some source and runtime files are also included; these are duplicated in each patch file, and will be updated correctly no matter which patch files are installed or in what order. To install the patch, merely untar it at the IRAF root. For example, to install the patch for the Digital Unix (Tru64) architecture: % cd $iraf cat patch3a-dunx.tar.Z | uncompress | tar -xvf - *** NOTE *** Patch3a is an incremental patch for the V2.11.3 release only. IRAF must already have been upgraded to V2.11.3 before the patch is installed. The V2.11.3 distribution files DO NOT include patch3a. Patch3a must be installed after upgrading to IRAF V2.11.3. 6.4 Patch3b - September 18, 2000 Patch 3b is a limited patch containing bug fixes to support various external packages (Gemini, PROS, STSDAS, MSCRED). If you don't run into any of the bugs fixed in the patch you don't need to install it, although there is no reason to not do so. The 2.11.3b patch contains all FITS kernel bug fixes through August 2000, assorted buffer size increases, file descriptor leak fixes, error recovery fixes, isolated fixes to MWCS and QPOE, a fix affecting apextract performance when extracting large numbers of spectra, an updated observatory database, and some enhancements to the networking interface to support an upcoming release of Ximtool. Nothing was included which could change the normal behavior or interface of an application. This is a bug fix patch; release of new functionality is being deferred until the V2.11.4 release. The patch files are as follows: patch3b-dunx.tar.Z patch3b for Compaq Tru64/Digital Unix The patch files contain updated executables for the given architecture. Some source and runtime files are also included. To install the patch, merely untar it at the IRAF root. For example, to install the Digital Unix patch: % cd $iraf zcat patch3b-dunx.tar.Z | tar -xvf - *** NOTE *** Patch3b is an incremental patch for the V2.11.3 release only. IRAF must already have been upgraded to V2.11.3 before the patch is installed. The V2.11.3a patch should be installed before installing V2.11.3b. The V2.11.3 distribution files DO NOT include patch3b. ----------------------------------------------------------------------------- NOTES added since the release. Please check this space in the future for notes on any problems or issues arising after the initial release. Feb 3 1998 - IMFORT IMFORT had a bug where the byte-swap flag was not being set for new images. This could cause a image to be created which was either unreadable (floating invalid exception) or for which the data was returned incorrectly. Only byte swapped platforms are affected, such as the DEC Alpha and PCs. The fix is to replace libimfort.a by the version in this directory. The bug will be fixed in V2.11.2. [This patch is obsolete and has been dropped. Just do a full install if you have this problem. 21Aug99]