Getting Started

Documentation

Glish

Learn More

Programming

Contact Us

Version 1.9 Build 874

News	FAQ
Search	Home

Step 3. Run sneeze

At this point your AIPS++ installation has been bootstrapped to a state where sneeze (p) can be run.

You should also have a C++ compiler, and a TEX installation which includes L^ATEX, dvips, METAFONT and LATEX2HTML. Unset the DOCSYS variable in makedefs if you don't have TEX, it will prevent compilation of the AIPS++ documentation. The documentation may be downloaded using the aupdate command.

Users of SysV based systems such as Solaris should be warned that inhale (p) requires the BSD version of sum for computing checksums. You must ensure that the BSD version will be found ahead of the SysV version in aips2mgr's PATH. The GNU version of sum (in the GNU ``fileutils'' kit) provides both algorithms and uses BSD by default. Less salubrious possibilities are to put /usr/ucb (Solaris) or /usr/bsd (IRIX) ahead of /usr/bin in aips2mgr's PATH, or to create a symlink to the BSD version of sum in the AIPS++ bin area.

First invoke aipsinit (p) to add the AIPS++ bin directory to your PATH. If your interactive shell is a C-like shell (csh, tcsh) you would use

   yourhost% source /aips++/aipsinit.csh

whereas for Bourne-like shells (sh, bash, ksh) you would use

   yourhost% . /aips++/aipsinit.sh

If you use some other shell you'll have to revert to one of the above for the remainder of the installation. Now invoke sneeze (p)

   yourhost% sneeze -l -m cumulative&

This will build and install the latest version of the sources which are under active development. If you made any mistakes in your aipsrc or makedefs definitions some of these may become apparent during the installations. After fixing them you can recover via

   yourhost% gmake -C /aips++/code allsys

The allsys target will compile all AIPS++ sources, including documentation (assuming of course that you have the compilers). If you just wanted to compile the documentation alone you could use

   yourhost% gmake -C /aips++/code docsys

If everything has gone properly you should now have an up-to-date AIPS++ installation. However, in order to keep it up-to-date you must define a cron job to run inhale (p) on a regular basis. The normal procedure is to do a cumulative update every Saturday evening. However, you may wish to maintain a (possibly separate) system which is updated on a daily basis. Half-daily updates are also possible, but note that 12 hours may not be sufficient time to rebuild the system.

The exact timing depends on your timezone with respect to the master. New updates are produced by 0700 and 1900 Socorro time (MST or MDT) but you should allow at least an hour's grace before collecting them. An example crontab file might resemble the following:

   # Cumulative update of the AIPS++ directories each Saturday evening.
   00 22 * * 6   (. $HOME/.profile ; inhale.cvs -c) 2>&1 | \
      mail aips2mgr aips2-inhale@nrao.edu

(Note that all cron entries must be one-liners but they are broken here for clarity.) You may need to add the -n option to inhale (p) accordingly. Note that, as in the above example, the log produced by inhale is generally forwarded to aips2-inhale@nrao.edu. These logs are archived for about 10 days and are accessible via the AIPS++ home page http://aips2.nrao.edu/aips++/docs/html/aips++.html. This is particularly useful for verifying code portability, especially on platforms that a programmer doesn't have ready access to. You should also add the email address of a local person who will monitor the inhale logs (aips2mgr in the above example).