3.1 Getting the default user environment

Step 1 :

Create Your private SGV-directory. The name is not important for SGV.

Step 2 :

Define the SGV environment.

There is a com-file/script to set the values of two symbols used by SGV on the SGV source area. Put Yourself on this area and execute the appropriate file to define SGV_PAM and SGV_LIB :

@SGVENV

on VMS,

source sgvenv.csh

on UNIX if You work within the c-shell family, or

. sgvenv.sh

if You work with within the Bourne-shell family.

On UNIX, note that You must do 'source sgvenv.csh' or '. sgvenv.sh', not eg. 'csh sgvenv.csh'. The latter method only defines the variables in a sub-shell, not the shell You're actually working in. It's a good idea to put the call to the appropriate of these files in Your login file.

Step 3 :

Get Your user PAM-file template.

Go back to the private area. Make a copy there of the file SGVUSER.CAR on SGV_PAM, preferably with a different file-name. Use it as a template for your user PAM-file. If You intend to use other generated event than those produced by JETSET, PYTHIA, SUSYGEN, an external read of pre-generated events, or single particles, also copy SGVEVSIM.CAR, to use as a template for the interface.

Step 4 :

Copy default input files:

SGV needs three input-files : the geometry description, the steering-files, and, optionally, an HBOOK file with empty histograms and ntuples to be filled by the user-code. Examples of the two first are given on SGV_PAM. There is no default hbook-file, but there is an example of a KUMAC file to create it : sgv_ex.kumac. So do the following copies :

        Name on SGV_PAM                   Name on private area
        ---------------                   --------------------

         sgv_ex_jetset.tit                  sgv.tit
         sgv_geo1_ex.inp                    sgv_geo.inp
         sgv_ex.kumac                       (any name)

This completes the creation of the default user environment.