Version 1.9 Build 1556

News	FAQ
Search	Home

Next: Data Repository Up: Setting up Previous: Setting up

Subsections

Setting up your account to use AIPS++

General AIPS++ setup

The AIPS++ environment is defined via a once-only modification to your shell's startup script.

Assuming that AIPS++ has been installed under /aips++, users of Bourne-like shells (sh, ksh, bash) must add the following to their .profile file at a point after PATH (and MANPATH) are defined:

   # Get the AIPS++ environment.
     [ -f /aips++/aipsinit.sh ] && . /aips++/aipsinit.sh

The equivalent entry in .login for C-like shells (csh, tcsh) is:

   # Get the AIPS++ environment.
     if (-f /aips++/aipsinit.csh) source /aips++/aipsinit.csh

Users of the rc shell might use

   # Get the AIPS++ environment.
     if (test -f /aips++/aipsinit.rc) . /aips++/aipsinit.rc

in .rcrc, or in .esrc for the es shell:

   # Get the AIPS++ environment.
     if {test -f /aips++/aipsinit.es} {. /aips++/aipsinit.es}

The aipsinit (p) scripts define a single environment variable called AIPSPATH (§1.2) and add the AIPS++ bin area to the PATH environment variable and the AIPS++ man directory to the MANPATH environment variable.

For more detailed information, see aipsinit (p). This contains an explanation of AIPSPATH and a mechanism for controlling the point where the AIPS++ bin areas are added to PATH.

AIPS++ programmer setup

Normally, AIPS++ programmers must belong to the AIPS++ programmer group in order to have permission to write to the AIPS++ source directories. The conventional name for this group is aips2prg (see §1.4), but it may be different at your site. Type

   yourhost% groups

to list all groups that you are a member of, and consult your local AIPS++ manager if in doubt.

Apart from invoking aipsinit (p), AIPS++ programmers need to create a shadow copy of the AIPS++ code directory tree to serve as their AIPS++ workspace. The mktree (p) utility does this:

   yourhost% mkdir $HOME/aips++
yourhost% cd $HOME/aips++
yourhost% mktree

Apart from creating a shadow copy of the AIPS++ code directory tree, mktree creates symbolic links into the AIPS++ rcs directory tree thereby linking the programmer's workspace to the local copy of the AIPS++ RCS repository (see §1.1.4).

mktree works incrementally so that if any workspace directories or RCS symbolic links are accidently deleted, or if new AIPS++ directories are created, mktree will recreate only what is necessary. For a more detailed description, see mktree (p).

Once the programmer workspace has been created by mktree AIPS++ sources can be checked in and out, updated, renamed, or deleted by the ai (p), ao (p), au (p), amv (p), and ax (p) utilities. Native RCS utilities such as rlog and rcsdiff may also be used. For a more detailed description see chapter 9.

Next: Data Repository Up: Setting up Previous: Setting up Contents Index