If GSvit is started with “test” as an argument, followed by test number, it can run an automated test. For key tests even a precomputed value is installed, so result can be compared to it automatically. If a GPU is present in the computer and GSvit is translated with GPU support, it is recognized, reported and used for comparison to CPU.
Tests can be useful namely when installing GSvit on a new system or in doubts whether a concrete algorithm does not do what is expected.
Automated tests available are as follows (run gsvit with no arguments for a list of them):
is more precise regarding peak GSvit performance estimation.
The “AAABCDEF” naming is used also to store the precomputed data that are compared with tests results. The precomputed data for comparison are typically single near field or far field point time dependence.
There are two more tests designed for benchmarking HPC systems:
One more special command line argument is implemented. Parameter “–killer filename” defines special condition for stopping calculation if the specified file in working directory exists and its content (ASCII) is a number 1. This specific workaround could be useful only very rarely, at present its main use is to prevent wrong process termination in Windows version of XSvit.