A new version of the ctio package was made available in the NOAO ftp archive Feb 22, 1994: -rw-rw-r-- 1 sjacoby 922696 Feb 22 11:23 /u1/ftp/iraf.old/ctio.tar.Z The old version will remain for a while as ctio.tar.ZOLD. Pedro Gigoux has these comments on the new version of CTIO: > I have a new version of the CTIO package ready for > distribution. The compressed tar file is available via anonumous ftp > from ctios1, and is located in pub/iraf. > The new version contains mostly bugs fixes to already existing > tasks, decomisioning of old tasks that have been superseeded by another > standard IRAF tasks (ezimtool, printf), two new tasks (imspace, > iraf2bin), and updated versions of the CTIO manuals. I have not > rewritten tasks to make use of MWCS (e.g. spcombine), but I'll try to > do this as time permits. > - IMSPACE: Tells you how much disk space is being used by an image > (header and pixel file). The only problem is that you have to specify > the image with the extension, since I'm using FIO to open the header to > determine its size. > - IRAF2BIN: Converts an IRAF image into a binary file. This is almost > the same as the BINFIL task, except that it does not have a scaling > parameter, it has an output data type parameter, and it has a parameter > to specify whether to write a header or not. The header length (in > bytes) is four times the number of columns, and it contains the image > dimension in the first two integer words. This header is used by > programs written by Claude Roddier, used by some people working in > telescope optics down here. [ShJ 22FEB94] ------------------------------------------------------------------------------- Installation Instructions for the CTIO IRAF External Package These installation instructions assume that you have successfully obtained the ctio tar archive, either using anonymous ftp or on a magnetic tape. If you retrieved a compressed version of the tar file over ftp, uncompress it before proceeding. These instructions describe how to install the CTIO software as a layered (external) package to IRAF versions V2.8 and beyond. Documentation on layered software is found in the Site Manager's Guide that accompanied your IRAF distribution. SUN/IRAF sites will also want to read up on "Multiple Architecture Support" in section 3.1 of the SUN/IRAF Site Manager's Guide. Further help is available from the IRAF HOTLINE (602-323-4160) or by email (iraf@noao.edu or noao::iraf). [1] Create a directory to contain the CTIO 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:[ctiolocal] (VMS) or /local/ctiolocal/ (UNIX). Make the appropriate file name substitutions for your site. [2] 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 ctio to be the pathname to the ctio root directory. The '$' character must be escaped in the VMS pathname; UNIX pathnames must be terminated with a '/'. Edit extern.pkg to include: reset ctio = usr\$1:[ctiolocal] # VMS example reset ctio = /local/ctiolocal/ # UNIX example task ctio.pkg = ctio$ctio.cl Near the end of the hlib$extern.pkg file, update the definition of helpdb so it includes the ctio help database, copying the syntax already used in the string. Add this line before the line containing a closing quote: ,ctio$lib/helpdb.mip\ NOTE: In IRAF V2.8 the length of the helpdb string cannot exceede 160 characters. A helpdb string longer than 160 characters will cause the CL startup process to fail. This restriction does not exist IRAF versions after V2.8. [3] Log into the CL from the IRAF account and unpack the archive file. Change directories to the CTIO root directory created above and use 'rtar': cl> cd ctio cl> softools cl> rtar -xrf where is the host name of the archive file. 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 [ctiolocal.bin] can be deleted. UNIX sites should leave the symbolic link 'bin' in the CTIO root directory pointing to 'bin.generic' but can delete any of the bin.`mach' directories that won't be used. [4] When the archive has been unpacked, build the CTIO package executable: The compilation and linking of the CTIO package is done using the following command: cl> mkpkg -p ctio update >& ctio.spool & NOTE: SUN/IRAF sites will have to configure their IRAF systems for the desired architecture before issuing the above command. SUN/IRAF sites must execute a pair of 'mkpkg' commands for each supported architecture type. For example: cl> mkpkg -p ctio ffpa cl> mkpkg -p ctio update >& ctio.ffpa & cl> mkpkg -p ctio f68881 cl> mkpkg -p ctio update >& ctio.f68881 & NOTE: BSD/IRAF sites will have to modify the bin directory structure before issuing the above mkpkg command. There should be a directory named ctio$bin.vax which is symbolically linked to ctio$bin. This can be done with the following UNIX commands: % cd /local/ctiolocal/ % rm bin % mkdir bin.vax # if it doesn't already exist % ln -s bin.vax bin The spool file(s) should be reviewed upon completion to make sure there were no errors.