README FOR SUN/IRAF VERSION 2.12 Updated Thu July 15, 2004 Current Patch Level V2.12.2a-EXPORT ############################################################################## 15-Jul-2004 *** V2.12.2 Patch-2a Release 06-Feb-2004 *** V2.12.2 Patch-2 Release 15-Jul-2002 *** V2.12.1 Patch-1 Release 08-May-2002 *** Initial V2.12 EXPORT Release (SunOS, Solaris) IRAF V2.12 is a major update to the system and requires a FULL INSTALLATION of IRAF, even if you have an existing V2.11 system. The Installation Guide (suniraf.ps.Z) contains a detailed description of the installation process for both first-time installations and updates to existing systems. Installation will require downloading the AS, IB, and NB distribution files from this directory. The AS distribution is common to both SunOS and Solaris host systems and is required for any installation. There are separate sets of binaries (the IB and NB distributions) for SunOS and Solaris and only those binaries required for a particular architecture need to be downloaded. Sun/IRAF V2.12 supports SunOS 4.X and Solaris 2.5.1 thru Solaris 2.9. All versions are supported with a single IRAF installation, although you need to install separate binaries for SunOS and Solaris to support both platforms. The IRAF distribution does not itself include graphics and image visualization tools; these are distributed separately. XGterm is required for any IRAF task which does vector graphics or which has a GUI. Any of the XImtool, SAOtng, SAOimage, and DS9 image display servers may be used for image interaction. See ftp://iraf.noao.edu/iraf/x11iraf/ for the latest X11IRAF tools (XGterm/XImtool) and /contrib for additional display servers (DS9, SAOtng, and SAOimage). See also the post-distribution notes at the end of this file. These are continually updated after the release as any problems are encountered. ############################################################################## Contents -------- 1. Introduction 1.1 The Sun/IRAF V2.12 Release 1.2 Who Should Upgrade? 2. Highlights of this Release 3. Installing Sun/IRAF 3.1 Things to Watch Out For (IRAF) 4. X11/GUI Support 4.1 The GUIAPPS External Package 4.2 The X11 Desktop 4.3 Things to Watch Out For (X11IRAF) 5. Magtape Interface 6. Printer Interface 7. Patch Instructions <--- READ THIS!! 7.1 V2.12.2 Patch Instructions <--- READ THIS!! 7.1 V2.12.2a Patch Instructions <--- READ THIS!! 8. Notes Added Since the Last Release ----------------------------------------------------------------------------- 1. INTRODUCTION ----------------------------------------------------------------------------- 1.1. THE SUN/IRAF V2.12 RELEASE Sun/IRAF V2.12 is a port of IRAF to Sun/Sparc platforms running either SunOS or Solaris. Beginning with IRAF V2.11, a single version of Sun/IRAF installed on a central server can simultaneously support IRAF sessions running on any combination of SunOS or Solaris workstations or servers. README This file (29 Kb) as.ssol.gen.Z All-Sources (main IRAF distribution) (31 Mb) ib.sos4.sun.Z Core system binaries for SunOS (18 Mb) ib.ssol.sun.Z Core system binaries for Solaris (32 Mb) nb.sos4.sun.Z NOAO package binaries for SunOS (17 Mb) nb.ssol.sun.Z NOAO package binaries for Solaris (19 Mb) splits/* Split distribution files for the above distributions patch2a/ IRAF V2.12.2a patch release files suniraf.ps.Z Sun/IRAF Installation Guide (Postscript) suniraf.ms.Z Sun/IRAF Installation Guide (source) unixsmg.ps.Z IRAF V2.12 Site Manager's Guide (Postscript) unixsmg.ms.Z IRAF V2.12 Site Manager's Guide (source) guiapps.readme GUIAPPS installation instructions ( 7 kb) guiapps.tar.Z GUI applications package (54 Mb) Beginning with V2.12 each of the AS, IB, and NB distribution files will be available as a single file for more convenient downloading over high-bandwidth Internet connections. For sites with slow or unreliable network connectivity where the transfer may not finish successfully, the "splits" directory contains copies of the distribution files which have been split into a number of modest size (e.g. 512KB) chunks. The Installation Guide provides detailed instructions on how to use these files to install IRAF. A complete installation requires that the user obtain the AS source distribution (in this case the 'as.ssol.gen.Z' file or the contents of 'splits/as.ssol.gen') and at least one set of IB and NB binary distribution (e.g. 'ib.sos4.sun.Z' and 'nb.sos4.sun.Z' for a SunOS system, and 'ib.ssol.sun.Z' and 'nb.ssol.sun.Z' for a Solaris platform). GUIAPPS. The guiapps.tar.gz file is an OPTIONAL external package containing prototype IRAF applications with GUIs. Use of these tasks requires that XGterm be used for the IRAF session. Unlike other external packages, guiapps is being distributed with prebuilt binaries to simplify the installation - all you have to do is unpack the distribution and edit the hlib$extern.pkg file. Please see below for detailed information on this package. 1.2 WHO SHOULD UPGRADE? IRAF V2.12 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.12 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.12, and "irafo" will bring up the older V2.11.3 release). ----------------------------------------------------------------------------- 2. HIGHLIGHTS OF THIS RELEASE ----------------------------------------------------------------------------- ************************************************************************* # See also the 'v2122revs.txt' file in the PC-IRAF distribution # # directory for additional changes in the V2.12.2 patch release. # * Users wishing to install V2.12.2a should consult the README file in # * the 'patch2a' subdirectory. # ************************************************************************* o Pixel Mask Support Added to FITS Kernel The FITS kernel was modified to add support for storing pixel masks in FITS extensions as compressed images using the binary table extension. These masks appear as images to the system and may be accessed like any other image. Storing the pixel masks directly in a FITS MEF file makes it possible to store all the data for one observation in a single file, simplifying data management. o New Pixel Mask Tasks Several new tasks have been added to the system PROTO package for manipulating pixel masks: o MIMSTATISTICS allows image statistics to be computed while rejecting pixels specified by an input mask. o MSKEXPR task is a general-purpose mask expression evaluator similar to IMEXPR for images, but has builtin boolean region functions which can be used to set values inside or outside of certain geometric shapes. o MSKREGIONS creates an output mask based on an input text de- scription. Region descriptions can be composed of geometric shapes and logical operation on mask regions. o OBJMASKS in the NPROTO package is a new task for detecting objects in an image and creating an output catalog or pixel mask of found objects. o Shared Memory Limitations Eased The IMAGES and DAOPHOT packages executables are now linked statically to remove per-process memory limitations imposed by the IRAF shared library on Sun and Dec Alpha systems. Previously tasks such as DAOFIND and IMCOMBINE were limited to 268Mb on Sun systems. These tasks can now use up to the machine memory limits. o Image I/O Buffer Sizes Increased Image I/O performance for very large images was improved by changes to the internal buffer sizes. By default the system will now automatically adjust the size of the image buffers to optimize i/o for the size of the image being accessed. Additional control over i/o is possibly by tuning environment variables. In addition, some applications will now (memory permitting) adjust the IMIO buffers to hold the entire image in memory, where usage warrants it. o Simplified Installation Script The IRAF install script was rewritten to clarify the output, provide more extensive checking of the IRAF system setup prior to installation, and to do some of the most common post-install configuration. The script will print an explanation of any errors it finds and suggest corrective action. The hope is this will lead the user past some of the more common installation errors. In addition, the SYSINFO diagnostic script which does more extensive checking of the system is also now part of the distribution. This script can be used to verify the system once the install is complete, or to generate a report of the system configuration if needed by site support. An UNINSTALL script to remove iraf command links and files created by the INSTALL script is also available to remove IRAF from a machine. All scripts are now installed in the hlib$ directory. o New HELP GUI and Output Options The HELP task was enhanced to provide a new GUI option (XGterm is required). This is essentially the XHELP task which has been available in the GUIAPPS external package for some time, however this version of the task is fully backwards compatible with old HELP task, and text-mode output is still the default. In addition, help pages may now be output in either HTML or Postscript format for Web presentation or pretty-printing to a hardcopy device. The LROFF task was similarly modified to provide direct conversion of Lroff format text. o DISPLAY Task Changes As part of the recent X11IRAF enhancements, the DISPLAY task and others such as IMEXAMINE which interact with the display server were modified to take advantage of the new features in XImtool V1.3. These include support for up to 16 frame buffers (increased from 4 in previous versions), and enhanced real-time WCS readout capabilities. The changes are fully backwards compatible for use with older XImtool versions or display servers such as SAOimage, SAOtng, or DS9 which have not yet been updated. X11IRAF V1.3 is being released simultaneously with IRAF V2.12. While IRAF V2.12 is fully compatible with older versions of X11IRAF, users will need to upgrade both systems to the latest versions to take full advantage of all the new features. Please see the X11IRAF Release Notes for details on what has changed. o New Packages Several new packages are available in this release (see the NOAO package change notes below for details): - A new ASTCAT package for extracting astrometric and photometric calibration data from remote or local catalogs was added to NOAO. - A new CRUTIL package for doing cosmic ray detection and removal package was installed in the IMRED package. - A new QUADRED reduction package for QUAD format data was installed in the IMRED package. This is a generalized replacement for the ARED.QUAD and XCCDRED external packages for processing CTIO and ESO FORS1 multi-amplifier data. - A new OBSUTIL package was installed in NOAO. This is a collection of tasks from various external packages which are useful to plan or carry out observations. o New Developer Libraries. Several new libraries are available for SPP developers: - PSIO is a new Postscript text generation library installed in sys$psio. - CATQUERY is a remote astrometric/photometric catalog access lib installed in the XTOOLS utility library. - SKYWCS is a sky coordinate transformation library installed in the XTOOLS utility library. ----------------------------------------------------------------------------- 3. INSTALLING SUN/IRAF ----------------------------------------------------------------------------- The procedure for installing Sun/IRAF is unchanged from earlier versions of Sun/IRAF. Refer to the Sun/IRAF Installation Guide (suniraf.ps.Z) for detailed installation instructions. A full installation, as for any 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.ssun Solaris binaries for core system /iraf/irafbin/noao.bin.ssun Solaris binaries for noao packages /iraf/irafbin/bin.sparc SunOS binaries for core system /iraf/irafbin/noao.bin.sparc SunOS 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, and agrees with the default configuration used in the distribution files. Having such a link when IRAF is served from a central NFS system also allows all clients in the network to use a common "/iraf/iraf" root directory regardless of the NFS mount points. Graphically such a tree would look something like (for a Solaris-only system) /iraf / \ (AS) /iraf /irafbin / \ (IB) bin.ssun noao.bin.ssun (NB) The graph indicates where each of the three distribution sets should be unpacked. The "iraf root directory" in this case is /iraf/iraf, this is the value you enter to the install script. See the installation guide for details, specifically the Appendices which gives a complete examples. The V2.12 Sun/IRAF release supports two architectures. "ssun" is the Solaris-Sun architecture for Sparc platforms running Solaris. "sparc" is the SunOS architecture for Sparc platforms running SunOS. A separate set of CORE and NOAO binaries is provided for each architecture. The all-sources (AS) distribution supports both architectures. 3.1 THINGS TO WATCH OUT FOR (IRAF) Please see the release notes (iraf$doc/v212revs.hlp or just type 'news' when you first log into the system) for information on what has changed in V2.12, and things to watch out for. As with any major release we STRONGLY recommend that each user reinitialize their 'uparm' directory to pick up the numerous task and package parameter changes in this release. IRAF V2.12 does not require this if you are upgrading from V2.11, but it is still strongly recommended. The uparm directory may be reinitialized by issuing a new MKIRAF command prior to logging into the system. ----------------------------------------------------------------------------- 4. X11/GUI SUPPORT ----------------------------------------------------------------------------- IRAF V2.12 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). This software is continually under development and new versions appear on a timetable independent of that for the main IRAF distribution. Note that a major new X11IRAF V1.3 release is timed to coincide with the IRAF V2.12 system. XImtool users especially should upgrade to take advantage of the many new features and bug fixes. See the README file in the /iraf/x11iraf archive directory and the X11IRAF V1.3 release notes for details on what has changed. Other IRAF-compatible GUIs can also be used with IRAF, e.g. DS9, SAOtng, and SAOimage. This software is available from the archive /contrib directory as a convenience but may not always be the most recent release. 4.1 THE GUIAPPS EXTERNAL PACKAGE Some time ago we started a project to develop prototype IRAF applications with integral GUIs (graphical user interfaces). These applications have since served their purpose in prototyping new technology for science GUIs and component-based applications in IRAF. The GUI applications are much more than just technology prototypes however: these are very useful science applications with many new features, with a nice graphical user interface to boot. With the release of IRAF V2.11.3 and X11IRAF V1.2 several years ago, it became possible to wrap up work on the GUI prototypes and get them out for people to use. The prototype GUI applications are contained in the package GUIAPPS available from the /iraf/extern directory of the IRAF archive, and contain the following tasks: demo - GUI Demo Task spt - SPECTOOL Package xhelp - GUI Help Browser Task xrv - GUI Version of the RV Package xapphot - GUI Aperture Photometry Package Note that with V2.12 the XHELP task is included as part of the core system as a special device type (e.g. "help implot dev=gui" will run HELP as a GUI task). The GUI tasks require that the user be running an XGterm graphics window (from X11IRAF) in order to display the GUI: Xterm users WILL NOT be able to use the GUIs presently. To install the package users should download the 'guiapps.tar.Z' file from the IRAF archive directory and uncompress/untar it in the local external package directory (typically /iraf/extern). Detailed installation inst- ructions are 'guiapps.readme' file in the same directory. More information of the GUIAPPS package is available from the project page at http://iraf.noao.edu/iraf/web/projects/guiapps/. 4.2 THE X11 DESKTOP The X11IRAF utilities will run under any X desktop. Most people will probably use Sun's CDE or OpenWindows desktops, 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. New users of X11 who are not sure how to configure the window system might want to look at the .Xdefaults, .xinitrc, .openwin-menu, etc. files in the IRAF system manager login directory ($iraf/local, or ~iraf). These files will set up a working IRAF desktop under OpenWindows and should serve as an example or starting point for an IRAF desktop under OpenWindows. Logging in as "iraf" and then typing "win" or "openwin" will start up the windows. 4.3 THINGS TO WATCH OUT FOR (X11IRAF) Please see the documentation included with X11IRAF V1.2 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. The default terminal type may be set with the MKIRAF command to make the change more permanent. ----------------------------------------------------------------------------- 5. MAGTAPE INTERFACE ----------------------------------------------------------------------------- The DEV directory contains default template tapecap files for both SunOS (dev$tapecap.sunos) and Solaris (dev$tapecap.solaris). 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". If a node-specific tapecap file is not found the fallback will be to use the 'dev$tapecap' file. User should copy one of the template tapecap files provided to the fallback dev$tapecap file to take advantage of several common predefined tape device entries, however the new install script in V2.12 will do this automatically if you proceed with the post-install configuration. See the release notes for further information on this capability, and the IRAF Site Manager's Guide for more information on configuring tape devices. ----------------------------------------------------------------------------- 6. PRINTER INTERFACE ----------------------------------------------------------------------------- Solaris, since it is Unix SysV based, uses lp/lpsched as the native printer interface rather than the Berkeley lpr/lpq. SunOS uses the Berkely lpr. Depending upon how Solaris is configured this may be available for Solaris as well. The dev$graphcap (for hardcopy graphics) and dev$termcap (for text output) files 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. ----------------------------------------------------------------------------- 7. PATCH INSTRUCTIONS ----------------------------------------------------------------------------- 7.1 Sun/IRAF V2.12.2 - Fri February 6, 2004 The Sun/IRAF distribution files have been fully regenerated for V2.12.2, so one way to upgrade IRAF to V2.12.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 Sun/IRAF V2.12 installation you have the option of installing the patch file. Note that THE V2.12.2 PATCH WILL OVERWRITE CERTAIN SITE SPECIFIC FILES. These are the following: unix/hlib/extern.pkg unix/hlib/zzsetenv.def dev/termcap dev/graphcap dev/imtoolrc dev/hosts 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.SSOL.SUN (the sparc/Solaris binaries for the core system, with the IB.SSOL.SUN distribution downloaded to the directory "/ib.ssol.sun" (where is where you created this directory): % cd $iraf/bin.ssun % pwd /iraf/irafbin/bin.ssun # (you should be here, or somewhere similar) % cat /ib.ssol.sun.Z | uncompress | tar -xpvf - A similar procedure is followed to install each of the other binaries. See the URL http://iraf.noao.edu/v212/v212-patch2.html for a detailed desc- ription of what is included in the patch and platform-specific notes. 7.2 Sun/IRAF V2.12.2a - Thu July 15, 2004 Details of the V2.12.2a patch release may be found in the file ftp://iraf.noao.edu/iraf/v212/SSOL/patch2a/README ----------------------------------------------------------------------------- 8. NOTES ADDED SINCE THE LAST RELEASE. ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- Install Script Bug -- Sun/IRAF tapecap configuration (10 May 2002) Two small typos were found in the new install script during the post-install configuration of the tapecap files: o The first is simply a typo in the output message where it refers to 'tapecap.sunos' rather than 'tapecap.solaris' when the script is run on Solaris systems. This is harmless since the links are in fact created with respect to the proper file when executed. o The second problem is another small typo in a variable name that would prevent an existing tapecap file from being properly deleted, the script next tries to create a symlink of the same name resulting in an error message. Both problems have been fixed and a new version of the install script is available from: ftp://iraf.noao.edu/pub/install ----------------------------------------------------------------------------- IRAF V2.12 Install Script Bug -- "Badly formed number" Error on Sun/IRAF (15 May 2002) The post-install configuration of the tapecap files can sometimes fail on Sun/IRAF systems with a "Badly formed number" error similar to: : Create a default tapecap file? (yes): Creating default file 'tapecap.foobar' from tapecap.sunos... if: Badly formed number The cause is a check for a tapecap being a symbolic link using the "-l" csh directive which isn't portable, the solution is to simply use a "-e" to check for the existance of the file/link. Both problems have been fixed and a new version of the install script is available from: ftp://iraf.noao.edu/pub/install ----------------------------------------------------------------------------- IRAF V2.12 Install Script Bug -- More syntax errors (17 May 2002) Several more problems have been reported with the new install script on Mac OS X and Sun systems: o On some Mac OS X systems there is no /usr/include directory where the Developer's Tools haven't been installed. The script was modified to check for the existance of this directory and create it if needed. o The install script uses the C-shell builtin 'which' command in some cases to determine when commands might exist on the system. The script however was assuming that this command would fail with a "command not found" message but on some systems the error would be "no cmd found in ....". The script was modified to handle either case. Both problems have been fixed and a new version of the install script is available from: ftp://iraf.noao.edu/pub/install ----------------------------------------------------------------------------- IRAF V2.12 Install Script Bug -- More changes (24 May 2002) On some systems the detection of an 'iraf' user account may fail since it relies either on the 'id' command or an entry in the local /etc/passwd file. An iraf user account may exist under DNS but still not show up in the install script. The verification was changed from a fatal error to a warning to allow the installation to proceed. This problem has been fixed and a new version of the install script is available from: ftp://iraf.noao.edu/pub/install ----------------------------------------------------------------------------- IRAF V2.12 Install Script Bug -- More changes (28 May 2002) In some user environments the "which" command may not be the shell-builtin command but and Open Source application. When this application fails to find the command the message is written to the stderr stream which was not properly being checked in all cases, usually resulting in a "syntax error". This problem has been fixed and a new version of the install script is available from: ftp://iraf.noao.edu/pub/install ----------------------------------------------------------------------------- IRAF V2.12.1 PHOTCAL -- FITPARAMS task not finding catalogs (20 July 2002) The FITPARAMS task may fail to find catalogs due to a invalid 'catdir' package parameter introduced in the V2.12.1 update. This problems affects all systems. This can be fixed at the user level by resetting the PHOTCAL package parameters to the correct value (before loading the PHOTCAL package), i.e. cl> photcal.catdir = "photcal$catalogs/" Site managers can make the fix system-wide by editing the file iraf$noao/digiphot/photcal/photcal.par to change the default value for the 'catdir' parameter to remove the 'x' from 'photcalx'.