opticks-t reporting of test fails

The opticks-t function ends by listing any failing tests, eg:

FAILS:  4   / 440   :  Wed Jan 27 00:08:47 2021
  9  /51  Test #9  : SysRapTest.SPathTest                          ***Exception: Other            0.25
  22 /32  Test #22 : OptiXRapTest.interpolationTest                ***Failed                      10.87
  32 /32  Test #32 : OptiXRapTest.intersectAnalyticTest.iaConvexpolyhedronTest ***Exception: Other            6.41
  2  /2   Test #2  :                 ***Failed                      2.94

Several tests use python and NumPy

Opticks analysis and debugging is based on numpy as all geometry and event data uses the NPY serialization and .npy files so several tests will fail if numpy is not installed within the python that is used.

Opticks will use the default python from your PATH. You can control this by setting the OPTICKS_PYTHON envvar, eg:

export OPTICKS_PYTHON=python3
export OPTICKS_PYTHON=/usr/bin/python3

Running Tests Individually

When tests fail it is helpful to run tests individually to see the output, for example. Most Opticks tests should already be in your PATH and can be run directly with no arguments, for example:

[blyth@localhost ~]$ which interpolationTest

[blyth@localhost ~]$ which SPathTest

[blyth@localhost ~]$ SPathTest
[blyth@localhost ~]$ echo $? # return code from previous command, will be non-zero after running a failed test

Running simple tests under gdb

Running failing tests in the gdb debugger enables the error site to be found precisely by collecting the backtrace.:

gdb $(which interpolationTest)
gdb > r   # "run"
...       # on reaching the error the debugger will stop
gdb > bt  # "backtrace"

The backtrace provides the call stack of the place where the error occurs. This should be copy/pasted into emails to describe the location of the error.

Running tests which require arguments under gdb


A small number of the over 400 tests require arguments. These tests have triple dotted names such as:


To run these under gdb requires:

[blyth@localhost ~]$ gdb --args $(which intersectAnalyticTest) --cu

To find out what the arguments should be look at the CMakeLists.txt from the tests directory of the subproject and also look for .sh scripts in the tests directory which may have example commandlines.