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


next up previous contents index
Next: aipsview - Tool Up: aipsrcdata - Module Previous: aipsrcdata - Module


initialization - Tool



Package utility
Module aipsrcdata


Postscript file available

Startup customization - user/site



Description
The variables in this group are used to determine which Glishfiles are loaded at startup. This is determined by the variables system.packages and user.initfiles



Example
system.packages: aips synthesis
user.initfiles: myfile.g
Note that packages do not end in .g, but initfiles do.

If no system.packages are specified, the aips package is assumed. Note that many sites may want to customize which packages are loaded (for example, the NFRA site manager may want to add the nfra package), and some users may want to customize the list.

Note that the user.initfiles are loaded after the standard package .g files. If for some reason you want to execute Glishcode before the standard files, you can put that code in your .glishrc file.



Aipsrc Variables

system.packages   List of packages
    Allowed: any valid packages
    Default: aips
user.initfiles   List of which .g files to load on startup for the user
    Allowed: any .g files
    Default: none





next up previous contents index
Next: aipsview - Tool Up: aipsrcdata - Module Previous: aipsrcdata - Module   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
2006-10-15