Getting Started Documentation Glish Learn More Programming Contact Us
Version 1.9 Build 874
News FAQ
Search Home


next up previous contents index
Next: Makefiles Up: Repository Conventions Previous: Organization

Using Scripts

In many cases, an AIPS++ table is simply copied from the data source tree to the repository. There are, however, instances where an AIPS++ table is created (and updated) from files retrieved from remote sites. During the build, all of the tools available in an AIPS++ installation will be available for the makefiles and scripts to use. However, the plan is that no compilation, e.g. of C++ code, should be necessary to build the data repository. It should all be done with scripts. Currently, it is done with Glish scripts. Should there be cases where this is impossible this rule can be revisited.

When using scripts which build a piece of data, the exit status of the script indicates the result. In particular, an exit status of 0 indicates that the script completed successfully and that the data item was updated, an exit status of 1 indicates that the script completed successfully but the data item was not updated, and finally, an exit status of -1 indicates that an error occurred during the execution of the script. The exit status of the scripts is used to generate logs containing only a list of the updates or errors which can then be used to keep tabs on the system without getting daily email messages.


next up previous contents index
Next: Makefiles Up: Repository Conventions Previous: Organization   Contents   Index
Please send questions or comments about AIPS++ to aips2-request@nrao.edu.
Copyright © 1995-2000 Associated Universities Inc., Washington, D.C.

Return to AIPS++ Home Page
2004-11-13