Getting Started | Documentation | Glish | Learn More | Programming | Contact Us |
![]() | Version 1.9 Build 1556 |
|
AIPS++ (Astronomical Information Processing System, written in the C++ language) is an ambitious project to standardize the processing of (primarily radio) astronomical data, both interferometric and filled aperture. Currently under development by an international consortium of observatories, AIPS++ is now under beta release, with several other 'experimental' releases available to consortium organizations including NRAO-Green Bank.
Most staff computers in Green Bank fulfill the minimum requirements for running AIPS++ but fall short of the canonical system. Currently there is only one such system in Green Bank, rigel, which is designated as the visitor/observer machine in Room 105 of the new wing of the Jansky Lab.
One can setup to run AIPS++ on rigel remotely by doing the following:
For csh,tcsh:
For Bourne-type shells:
There are currently four different versions of AIPS++ available in Green Bank; these are labeled: 1)beta, 2) test, 3) new, and 4) old.
The beta release is a limited package targeted to consortium sites and a few friendly astronomers. It contains only the basic environment, some tools and some synthesis applications. It is intended to provide early exposure and feedback for AIPS++.
The test version is the package currently under development by all of the AIPS++ programmers. As such, it is a highly volatile environment which contains all of the latest tools along with the newest bugs and problems. The new version is designated as the most up to date, stable version of the software. This is currently the version used (linked with) the Monitor and Control software in Green Bank. The old version is intended as a fall back, in case something goes wrong with new (particularly during an update).
The test version of AIPS++ changes weekly (on Fridays at 21:30 lasting until
approximately Saturday 06:00). If you expect to be using AIPS++ during this critical time
please contact Joe McMullin (jmcmulli@nrao.edu) to suspend the crontab
for that week. The evolution of test
new and
new
old occurs less periodically, typically after substantial
changes have stabilized.
Currently, the new version is from Nov-1996 and the old version is from
the Pre-Cambrian Period.
Each of these versions lives under the /aips++ directory (e.g. /aips++/beta, /aips++/test, etc.).
Setting up your environment is covered more thoroughly in the "Getting Started in AIPS++" document. We elaborate here on a specific example appropriate to Green Bank.
In order to setup the environment (paths, etc) for executing AIPS++, only a single command need be invoked.
For C-like shells (csh,tcsh):
> source /aips++/version/aipsinit.csh, where version is beta, test, new, or old.
For Bourne-like shells (sh, bash, ksh, zsh):
. /aips++/version/aipsinit.sh, where version is again, beta, test, new or old.
At this point, you can enter the AIPS++ environment by typing "aips++" (NOTE: This applies only to the beta and test versions currently).
In addition, there are two standard configuration files which can be modified to suit your needs: .aipsrc and .glishrc. These files should live in your home directory.
system.path.include:=". /aips++/engr-scripts /aips++/gb-astro-scripts /aips++/test/sun4sol\_gnu/libexec"; system.print.precision:=9 include "rtools3.g"This sets up the path to include several directories where useful scripts might be found (specifically, in Green Bank, the directories /aips++/engr-scripts and /aips++/gb-astro-scripts, are repositories of local scripts), sets the print precision to 9, and includes the file "rtools3.g" which contains a number of useful functions (rtools3.g will be discussed in more detail later). However, be aware that your personal .glishrc file may override any scripts executed prior to entering AIPS++. For the example above, if you wanted to use the new version of AIPS++ and executed the appropriate aipsinit script for that version, AIPS++ would still then execute your .glishrc script which would tell it to read from the test directory (/aips++/test/sun4sol_gnu/libexec). It is best to avoid adding a version specific directory to this path; the path is set to be correct for the current installation, through the setup scripts.
logger.default: guiDesignates the logger GUI as the default output for logger messages.