...
The purpose of the GLAST SAS system tests is to provide and end to end test of the offline software. They are typically run for each tagged release of the GlastRelease and EngineeringModel packages.
The components are outlined in the following diagram.
TBC
The main executive script (runSystests.pl) is run manually at the moment. It runs the suite of shell scripts that it finds in the EMtests and GRtests subdirectories, tracks results and updates database tables. Each of the shell scripts that it runs consists of at least two parts, it first runs either a Gleam.exe or LatIntegration job then runs a RootAnalysis macro which reads the output files produced in the Gleam step and fills a collection of histograms. Once the histograms have been created, the executive script sets the standard and threshold for each histogram, that is, the version that this release is to be compared against, and the statistical threshold that defines whether the test has passed or failed. Finally the executive script runs a root macro which calculates several quantities from each histogram (number or entries, rms, KS probability that the histogram differs from its standard etc) and updates the database.
The system tests code can be found in u17/systests/src. The EMtests and GRtests directories contain one directory for each test type used for the EngineeringModel and GlastRelease packages respectively.