next up previous contents
Next: Printing/Reading the Manual Up: Introduction Previous: Introduction   Contents

The Purpose of GRASP

0 The analysis and modeling of data from gravitational wave detectors requires specialized numerical techniques. GRASP was developed in collaboration with the Laser Interferometer Gravitational Wave Observatory (LIGO) project in the United States, and contains a collection of software tools for this purpose. The first release of GRASP was in early 1997; since that time many individuals have made extensive contributions.

In order that it be of the most use to the physics community, this package (including all source code) is being released in the public domain. It may be freely used for any purpose, although we do ask that GRASP and its author be acknowledged or referenced in any work or publications to which GRASP made a contribution. If possible this reference should include a link to the GRASP distribution web site:
http://www.lsc-group.phys.uwm.edu/$\sim$ballen/grasp-distribution/ http://www.lsc-group.phys.uwm.edu/ ballen/grasp-distribution. The citation should specify the version number (for example, 1.9.1) of GRASP. In addition, if the code has been modified please state this. We suggest that if GRASP is installed at a site, one person at the institution should be designated as the ``responsible party" in charge of the GRASP package.

GRASP is intended for a broad audience, including those users whose main interest is in running simulations and analyzing data, and those users whose main interest is in testing new data analysis techniques or incorporating searches for new types of gravitational wave sources. The GRASP package includes a ``cookbook" of documented and tested low-level routines which may be incorporated in user code, and simple example programs illustrating the use of these routines. GRASP also includes a number of high level user applications built from these routines.

We are always interested in extending the capabilities of GRASP. Suggestions for changes or additions, including reports of bugs or corrections, improvements, or extensions to the source code, should be communicated directly to the author.


next up previous contents
Next: Printing/Reading the Manual Up: Introduction Previous: Introduction   Contents
Bruce Allen 2000-11-19