IRAF information and quick reference

• Basic structure
  • IRAF "wrapper" directory
    • extern directory
      • external packages
    • iraf main directory
      • All IRAF config and support files
        • Important: iraf/unix/hlib/extern.pkg tells Iraf where the external packages are.
    • irafbin directory
      • iraf "base" packages. "iraf" and "noao iraf" packages live here.
• Installation overview
  • Get the iraf installation guide from iraf.noao.edu.
  • Download files from iraf.noao.edu
    • as.pcix.gz
      • This is the x86 version. There's also a sparc version, but it's the same except for the name and the banner.
    • ib.[arch].gz "iraf" executables
    • nb.[arch].gz "noao iraf" executables
    • x11iraf if you need xgterm
  • Create directory structure
    • 
    • The directories under iraf/iraf are created by the as.pcix.gen tarball.
  • Unpack files
    • as.pcix.gen into iraf/iraf
    • ib.[arch] into iraf/irafbin/bin.[arch]
    • nb.[arch] inot iraf/irafbin/noao.bin.[arch]
  • Run setup program
    • Must use tcsh as root
    • cd iraf/iraf/unix/hlib
    • source irafuser.csh
    • ./install
    • Use the default answer for most of the questions. We do not need a tapecap file or iraf networking. You may strip the sources and get rid of unneeded bin directories.
  • Download external packages
    • From the iraf ftp archive:
      • ared
      • color (old, I don't think we need it anymore)
      • ctio
      • fitsutil
      • focas
      • gmisc
      • guiapps
      • mscdb
      • mscred
      • nmisc
    • From the IRAF contrib directory:
      • xray
      • mtools
    • gemini
    • STSDAS and TABLES
    • Cosmopack
    • rvsao
    • ingird_ql. Actually, this appears to be an updated package that includes ingrid_ql.
  • Install external packages
    • Expand the package's tarball into its directory in iraf/extern.
    • I have decided to add the package's version number to its directory. The package maintaners are bad about making that info available.
    • If you have precompiled binaries for all of your architectures, great! You're probably done with this step.
    • If you don't, you'll have to compile the package. I set up a whole, working iraf tree on rupert for this purpose.
      • First, edit the iraf/iraf/unix/hlib/extern.pkg file to tell iraf where the new package is.
        • They are all in this format:
          
        • Add the help file to the last line of the file, again following the format of the other packages.
      • Make sure you're using tcsh
      • setenv IRAF /astro/depot/iraf/iraf/
      • setenv hlib $IRAF/unix/hlib
      • cd packagedir
      • mkarch [arch]
      • cd ~/iraf
      • cl
      • Type the name of the package
      • cd [fully-qualified-package-directory]
      • mkpkg -p [package] update
      • wait. get coffee.
      • Hopefully it compiles properly and you get .e files in the bin.[arch] directory.
      • Copy the new external package directory to woodstock and edit woodstock's extern.pkg file.
    • Run IRAF
      • It should now be ready to run.
      • Users should cd to ~/iraf and mkiraf if it's a new iraf version.
      • Run cl. Hooray!
  
  

  Installing IRAF on a user's laptop

  
  If the user has a recent version of SuSE, you can just copy the whole IRAF tree to the notebook. You'll need to edit the extern.pkg and /iraf/iraf/unix/hlib/libc/iraf.h files to remove references to /astro/depot. Once that's done, run the install script as described above. This will set up symlinks for easy execution.
  You should probably also install SAOimage DS9 and X11IRAF.