...
Glossary
Running all parts of the system tests
Configuration file example]
Loading results and setting the default comparison in the database
...
| Panel | ||
|---|---|---|
| ||
Log into a machine with access to the batch farm. |
| Anchor | ||||
|---|---|---|---|---|
|
| Panel | ||
|---|---|---|
| ||
packag GlastRelease |
...
| Panel | ||
|---|---|---|
| ||
> $SYSTESTS/src/exec/runSysTests.sh |
You will see lots of console output, but the jobs are submitted to the batch queue and do not require you to stay logged in to the terminal. You can come back and find top level errors in the version result directory in testerr. The output files and logs will be in the test result directories, e.g., $SYSTESTS/GlastRelease/v17r35p20/<test_name>/linux/
...
Only one set of system tests for each package can run at the same time. You can run a set of system tests for EngModel and GlastRelease simultaneously, but you cannot run two sets for different GlastRelease versions simultaneously because the tests will try to store the output files in the same working directory. (This can be fixed, but needs more work to separate out some directory structure assumptions properly.)
| Anchor | ||||
|---|---|---|---|---|
|
- Rerunning the root analysis on existing Gleam outputs
- Re-running the comparisons/setting the default reference version
| Anchor | ||||
|---|---|---|---|---|
|
Skipping the Gleam step (MC generation, digi, recon, and merit)
If the mc, digi, recon, and merit trees already exist and are populated and you wish to simply regenerate the system test histograms, then adjust the config file to select a root only run.
...
This will access the database to find the locations of the root files that were already produced by Gleam and will regenerate the system test histograms. This is very convenient for testing and updating the RootAnalysis macros.
| Anchor | ||||
|---|---|---|---|---|
|
Re-running the comparisons/setting the default reference version
...