Testing the default user environment

We suggest You first go through all the steps below. Then run the program produced. This should yield an histogram file containig some plots of 1000 full hadronic $WW$ events in ILD. Study these plots, and the event listing on the screen (should contain one event), to see if the results seem reasonable. If so, SGV has been correctly instaled, and You can go on with the customisation, chapter 3.3 .

Step 1 :

Create the executable program.

Run the script cresgvexe on SGV_DIR. SGV_DIR is in your path, if you have followed the instructions. First run it without arguments. That gives You the explanation of the parameters bellow. Then run it with Your user program as an argument (without the .F95 extension). If there were no errors, You are ready to run.

The help in cresgvexe :

    cresgvexe : script to run create an executable image of SGV.

    Parameters :

      1  : merge   -  start by merge
           comp    -  start by compiling
           link    -  start by linking
      2  : Input file : if it is merge : user-code name; if it is comp : full fortran-file;
             if it is link : object file.
           This name will be used for all the files created at later steps,
           with their appropriate extensions.
      3  : options for compile, including pre-processor defines.
           (The defines are used to select the wanted program version.)
           Enclose it in quotes.
           Default is "-fno-automatic -ffree-line-length-none"
           If You give the value "debug",
           suitable options for debug compilation will be
           added, ie. "-g -O0 -fcheck=bounds ". -O3 is always included,
           except if either "debug" or an explict oprimisation
           level is given (-O1 ...)
      4  : options for link. Enclose it in quotes.
      5  : Area to store temporary files on.
      6  : nocomp    -  stop before compiling
           nolink    -  stop before linking
      7  : list of object files and/or libraries to put BEFORE the
           default set
      8  : (not used)
      9  : list of libraries to be searched AFTER all other libraries. By default
           lapack and blas are used. P9 will be added before these.
      10 : fortran compiler with style-options. default:
              gfortran

Hence, normally one would type

cresgvexe merge "the name of your user program (by default sgvuser)"

(If You didn't execute $SGV_DIR/sgvenv.sh (or .csh), the path to cresgvexe would need to be prepended).

Step 2 :

Do the assignments of input and output files.

You now need to assign input and output files for SGV. This is done by a shell-script sgvass.sh, which can be found on the SGV_DIR area as well, but should be copied to your private area already. It takes the following arguments :

arg 1 :

generic_name, identifier to be prepended to the names of the standard output files

arg 2 :

sgv_scratch, directory to put these files on (Default is the current directory)

When executed it will do the following assignments for You:

     OUTPUT files (all on the directory sgv_scratch (arg 2)) :

         name                    unit

      'generic_name'_hlis.dat     3       ( Histo statistics and
                                            errors, if any.)
      'generic_name'_events.lis   4       ( event-listings,
                                            including error reports)
      'generic_name'_lund.dat    30       ( JETSET random seed backup)
      'generic_name'_ranmar.dat  31       ( RANMAR random seed backup)
      'generic_name'_evnb.dat    32       ( Event number at last seed backup)

    INPUT/OUTPUT files ( on the directory sgv_scratch (arg 2)) :)

         name                    unit

      'generic_name'_sgv.root    99 ( Histogram input and output root-file)

    INPUT files ( all on the current directory) :

         name                    unit

      sgv.steer                  17       ( SGV steering file)
      sgv_geo.inp                51       ( Detector description)

If XX is the unit-number, then the files are soft-linked to fort.XX in the current directory.

Of the output-files, it's only unit 4 and the histogram-file that is normally of interest. If an SGV-run completed without errors the other ones can be deleted without further ado.

Step 3 :

Create the input histogram-file. SGV reads in an root-file from the file pointed to by the softlink fort.99, so You do NOT need to define You histograms in the program. To create the histogram file, simply execute the macro copied in step 4 chapter 3.1 ,

root -b sgv_ex.C.

assuming You called the macro sgv_ex.C

Step 4 :

Run the program.

One thousand WW events at 500 GeV centre-of-mass energy with full hadronic final states should have been produced. Check that there was no error-messages, and the event-listing on the screen seemed reasonable. The event should be listed twice: after generation, and after jet-clustering. The former contains true values, the latter seen ones. There is also a statistics print-out produced at the end.

Step 5 :

Check the histograms

Enter root, and open the file sgv.root. Check that the plots seems reasonable.

If these steps where completed successfully, SGV works on Your site.