Preface

This document should describe the Cactus flesh. In particular it should describe

• The philosophy of the flesh
• The coding style used
• The make system
• The various source directories and all their files
• The perl scripts

In addition it should contain ideas for future enhancements.

Overview of documentation

This guide covers the following topics

Part A: Philosphy and Style.

The philosophy behind the flesh and the coding style used.

Part B: The Make System.

The nitty-gritty of the make system.

Part C: The CST.

The nitty-gritty of the CST.

Part D: General.

General miscellaneous things used all over the flesh.

Part E: Main.

Everything you never wanted to know about the files in the Main subdirectory of the flesh.

Part F: Comm.

Everything you never wanted to know about the files in the Comm subdirectory of the flesh.

Part G: IO.

Everything you never wanted to know about the files in the IO subdirectory of the flesh.

Part H: Util.

Everything you never wanted to know about the various utility files.

Part I: Schedule.

Everything you never wanted to know about the Schedule system.

Part J: Appendices.

I’m sure we’ll need something here.

Other topics to be discussed in separate documents include:

Computational Thorn Guide

This will contain details about the arrangements and thorns making up the standard Cactus Computation Tool Kit

Relativity Thorn Guide

This will contain details about the arrangements and thorns making up the Cactus Relativity Tool Kit, one of the major motivators, and still the driving force, for the Cactus Code.

Users’ Guide

The stuff users need to know. This in particular documents the functions the flesh needs to make available to the thorns.

Typographical Conventions

Typewriter

Is currently used for everything you type, for program names, and code extracts.

< ... >

Indicates a compulsory argument.

[ ... ]

Indicates an optional argument.

How to Contact Us

Please let us know of any errors or omissions in this guide, as well as suggestions for future editions. These can be reported via our bug tracking system at http://www.cactuscode.org, or via email to cactusmaint@cactuscode.org. Alternatively, write to us at

The Cactus Team
Center for Computation & Technology
216 Johnston Hall
Louisiana State University
Baton Rouge, LA 70803
USA

Acknowledgements

Hearty thanks to all those who have helped with documentation for the Cactus Code.