Welcome to E781 Monte Carlo simulation

Code development

Version 6.1 (Sept. 16, 1999)

- contribution: Too many people have contributed to list it here.

- This version is a result of long development process , and fine

tuning at MPI.

- No OCS database is used directly. Only ADAMO database is used. All tables

need to simulate detector response were ported to ADAMO. Synchronization of

the OCS and ADAMO databases is made for any particular run with help

of OSA.

- OSA was updated and tuned to work with latest version of master file

and CON781 tables.

- This version was tested on following platforms: ALFA OSF, IRIX6.5, LINUX

- This version is currently installed for users on fsgi03 under IRIX6.5.

- See below how to start using the package.

Work status

Email of MC group: e781-mc@fn781a

GE781: Geant Based Detector Simulation of E781

Information on GE781, the experiment's MC, is indexed on this page. The MC coordinator is Renata Zukanovich Funchal from Sao Paulo. (zukanov@uspif.if.usp.br).

If you have questions about the E781 Monte Carlo, send mail to the Monte Carlo mailing list .

Monte Carlo Documentation

GE781 Quick User's Guide
GE781 User's Guide V4.0

How to Run GE781 on fsgi03.

============================================================================

User Installation (do it once)

prompt> setup ocs781
prompt> setup con781
prompt> setup -d off781
prompt> setup adamo
prompt> setup -z $E781PROD ge781
prompt> user_config (do this just the first time)
prompt> source ~/.bashrc
prompt> . $MY_MC_DIR/input/ge781_b.run (batch)
or prompt> . $MY_MC_DIR/input/ge781_i.run (interactive)

to build the database for a certain run just go :

prompt> OSA_B runnumber ALL
e.g. prompt> OSA_B 7588 ALL

Before to run

prompt> setup ocs781
prompt> setup con781
prompt> setup -d off781
prompt> setup adamo
prompt> setup -z $E781PROG ge781
prompt> . $MY_MC_DIR/input/ge781_b.run (batch)
or prompt> . $MY_MC_DIR/input/ge781_i.run (interactive)

============================================================================

READ THIS FOR MORE INFORMATION:

To build your own version of GE781 you should copy to your directory the following files :

GNUmakefile (this is automatically done for you by the script user_config)
the source files you want to change
the include files you want to change

these are in $GE781_DIR corresponding directories. They are accessible by $GEXXXX_SRC or $XXXX_INC. eg. $GEBSSD_SRC will point to the source files for the beamsilicon detector description and $GEBSSD_INC to its include files. After you are done with your changes you can modify the line user_obj += in your GNUmakefile to include your object files. After that justgmake or gmake DEB=1 (debug). To run this code you need to copy the following files that are in$GE781_IN (this is done automatically by the script user_config):

ge781.tit : title file
partab : particle table file
ge781_b.run : file for batch run
ge781_i.run : file for interactive run

The LUND event generator data can be found in: $GE781_DAT Some environmental variables are set by default but they can be overwritten by the user, these are:

$BEAMFILE : real beam phase space input filecurrently you can find following files in $GE781_DAT that can be used here : pbm11000.IN - proton beam for run 11000pbm11004.IN - proton beam for run 11004pibm10288.IN - pion beam for run 10288pibm10305.IN - pion beam for run 10305
$GE781_GAF : ADAMO database input file
$LUNDEVT : LUND event file
$PARTAB : partab file
$GE781TIT : title file

We provide three user scripts that are available to you after you have setup -z $E781PROD ge781 these are:

user_config : this will automatically build in your directory the minimum structure you need in order to run GE781 Use this only to configure your system for the first time.
check_env : this will check the set environmental variables the program uses and allow you to change them if needed. This will be called automatically in ge781_b.run/ge781_i.run
get_doc : this will automatically fetch the available documentation on GE781 or OSA. Usage : get_doc GE781 or get_doc OSA

We recommend you try them and report to us any possible mistakes you find.

If you do not want to change anything in the code, but just runge781 as it is, you will have to change ge781_b.run to point to theofficial executable $GE781_BIN/ge781_b.

=======================================================================

Special notes on GE781 LINUX distribution CD.

A CD distribution now avilable for GE781. You can request and we will send to you a copy of the CD.

On this CD you will find all packages need to run SELEX Geant Monte Carlo.

The directory "products" contains FTT, DAFT, CON781 and ADAMO packages.

The directory "generator" contains LUND generator developed for use with GE781.

The directory V6_1 contains the whole tree of subdirectories of GE781 itself.

Finally the directory "cern2000" contains a cernlib thatwas developed for use on RedHat 6.1 Linux.

There is a file mysetup.sh that contains definitions of packages typical for the distribution, and reflects where things are on my computer.
One will need to copy the file to his/her working directory edit it and source it if need to reinstall or develop the package. Subdirectory ups contains setup and unsetup shells that will install the ge781 package on your computer in a similar way as the user distribution at Fermilab. To run the shell you need to define an environment variable GE781_DIR first
(e.g. export GE781_DIR=/cdrom/v6_1 ). Then you can proceed as for user distribution ( user_config, source ~/.bashrc, OSA_B , get_doc ... )

As mysetup.sh contain definitions of con781, adamo, daft and ftt you need not to setup those packages as at Fermilab, just source mysetup.sh before to use ge781. Most of relevant information you can find on monte_carlo page of SELEX, and from the avilable documentation that can be recalled by the "get_doc" command.

Do not try to run LUND generator from CDROM. This package is not as developed as GE781. You have to copy
contents of the "generator" directory in a directory on your hard disk, go to src subdirectory, and examine the Makefile.

Running "make INFILE=run102" will compile run102.f and build executable in bin/ directory. Examples of fortran files, data files run102.in run102.out , output data file for use with GE781 run102.dat.gz are available in corresponding subdirectories.

Some usefull information how to work with CD distribution one can find on SOAP CD rom .

The package was build and tested on RedHat 6.2 with kernel 2.2.14 and cernlib 2000, so no guarantee that everything will be OK on other flavors. I would like to know if it runs on your platform. Comments and error reports are welcome.
1/6/2000 N.Kuropatkin (kuropat@fnal.gov)
=======================================================================

Some example files.

There are five input files for the Monte Carlo:

The titles file contains commands that affect how the Monte Carlo runs. You will supply this. An example titles file is available. The Monte Carlo looks for the name GE781TIT for its titles file.
The batch run script you will need to modify for your job. An example of the run script. is available. The file is self documented.
The database direction files lists which database files should be read. Normally you should not need to change this. It is expected to called GE781GAF and can be found here.
The particles definition file defines which particles GEANT knows about. Normally you should not need to change this. It is called PARTAB and can be found here.
The generated event file contains PYTHIA or FRITIOF output that GE781 will simulate in our detector. It is expected to be called LUNDEVT. A sample of such events can be found in $E781MC_DIR/data. A description of these files is given by run.info.

There are two output files:

The histogram file will be written to GEHIST (normally no histograms are collected).
The output file containing hits and digitization is written to the file given by the environment variable VIRTAP.

Last Update 27 June 2000

kuropat@fnal.gov