-------------------------------------------------------------------------
	Release Notes

October 29, 1999: V2.1
    QUADPROC was generalize to work on different image types instead of
    only "imh".

-------------------------------------------------------------------------
	Instructions to ftp the ARED IRAF External Package

The Arcon reduction software is packaged as an IRAF add-on package
called ARED, and it's available via anonymous ftp from iraf.noao.edu.
The compressed tar file is located in iraf/contrib and it is called
ared.tar.Z.  The binaries for some architectures are also provided as
ared-bin.<arch>.[Z|gz], so people don't have to recompile the package
if they already have this configuration.  Be sure to transfer the files
in binary mode.  The installation instructions follow this section.
Please contact iraf@noao.edu if you have any problems.

-------------------------------------------------------------------------
	Installation Instructions for the ARED IRAF External Package

These installation instructions assume that you have successfully
obtained the ared 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 ARED 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 Pedro Gigoux (pgigoux@noao.edu).

[1] Create a directory to contain the ARED 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:[ared] (VMS) or  /local/ared/ (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 ared to be the pathname to the ared
    root directory.  The '$' character must be escaped in the VMS pathname;
    UNIX pathnames must be terminated with a '/'.  Edit extern.pkg to include:

	reset ared     = usr\$1:[ared]   # VMS example
	reset ared     = /local/ared/    # UNIX example

	task  ared.pkg = ared$ared.cl

   Near the end of the hlib$extern.pkg file, update the definition of helpdb
   so it includes the ared help database, copying the syntax already used in
   the string.  Add this line before the line containing a closing quote:
	
		,ared$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 ARED root directory created above and use 'rtar':

	cl> cd ared
	cl> softools
	cl> rtar -xrf <archive>  where <archive> 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 [ared.bin] can be
   deleted.  UNIX sites should leave the symbolic link 'bin' in the ARED
   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 ARED package executable:

   The compilation and linking of the ARED package is done using the 
   following command:

	cl> mkpkg -p ared update >& ared.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 ared ffpa
	cl> mkpkg -p ared update >& ared.ffpa &

	cl> mkpkg -p ared f68881
	cl> mkpkg -p ared update >& ared.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 ared$bin.vax which is symbolically linked to ared$bin.  This can 
    be done with the following UNIX commands:

	% cd /local/ared/	
	% 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.  

[5] Copy the CCDRED executable into the package binary. A copy of this
    executable is needed to have a different parameter file for CCDPROC.

	cl> ared				# load the package
	ar> cd aredbin$				# go to the bin directory
	ar> copy noaobin$x_ccdred.e .		# copy executable