...
To run the system tests from scratch, i.e. runing Gleam to create the full root trees, RootAnalysis to create the histograms and finally a step to set the standard version, threshold and calculate the metadata, do (from the exec directory):
./runSystest.pl <configfile>
Where <configfile> is the name of your configuration file. If you do not supply a config file name, the code will look for a file called Config.txt by default. It is important that only one set of system tests for each package is running at any given time. You can run a set of system tests for EngModel and GlastRelease simultaneously, but you cannot run two sets for different GlastRelease versions. After you start the system tests it is usually a good idea to look at the file test_error (also in the exec directory). We fairly often get a sporadic error when connecting to the Oracle database. If this happens, I usually just kill the jobs with bkill 0 and start them again.
Skipping the Gleam step
If the full root trees already exist and are stored in the systests db and you wish to regenerate the histograms you can do:
./runRootOnly.pl <configfile>
This will access the database to find the locations of the files containing the root trees and will regenerate the histograms. This is very convenient if the RootAnalysis macros have been altered.