General

The code is written in FORTRAN. Since version 308 the code manager PATCHY has been discontinued, and instead the normal C preprocessor commands are used. The code is organised in a CVS based module Brahms. Its directory structure is shown in figure .

Figure: of directory structure of the CVS module Brahms.

brinstall	the installation scripts for Brahms;
brincludes	the common blocks and global definitions used in Brahms;
brsimu	routines for the simulation part;
brreco	routines for the reconstruction;
brutil	some utilities;
brmainb	the main program for batch running;
brmaini	the main program for interactive running;
brrecob	the main program for the reconstuction only batch running;
brrecoi	the main program for the reconstuction only interactive running;
brdata	example data files for Brahms;
brgeom	routines to define the geometry;
	brbeamv1: definitions of the beam line and other machine elements
	as defined in the CDR;
	brbeamv2: definitions of the beam line and other machine elements
	for the new beamline designs 1999;
tracking	the track fitting code;
calorimetry	calorimeter code;
bruser	example code for the users interface (event generation);

All required GEANT include files used in Brahms are incorporated in the brincludes/brfram directory.

The reconstruction code used in the tracking and in the calorimeter detectors is now kept in separte directories and files. The subdirectory tracking contains the tracking code, the directory calorimetry the calorimeter code.

The program can be run in interactive mode or in batch mode. For debugging it is useful to store the positions along particle tracks; this also produces interesting event displays during the interactive mode and is facilitated via a call of GSXYZ in GUSTEP. You can select the interactive and batch mode by using running the executables brmaini.bin or brmainb.bin and doing so will also automatically set the program up in such a way that GSXYZ is called when the interactive mode is chosen.

The simulation and the reconstruction code is maintained in different directories. The reconstruction code can be run independently from the simulation code. The simulation code always contains the reconstruction code, though through use of a control card it can be switched on or off at execution time. The corresponding executables brrecoi.bin or brrecob.bin will be also created by the installation.