Running

Notice

Before reading this Wiki, it is assumed rocALUTION with the client applications has been successfully built as described in Build rocALUTION libraries and verification code

Samples

cd [BUILD_DIR]/example
./cg <matrix.mtx>

Example code that calls a CG solver.

Unit tests

Run tests with the following:

cd [BUILD_DIR]/clients/tests
./rocalution-test

To run specific tests, use --gtest_filter=match where match is a ':'-separated list of wildcard patterns (called the positive patterns) optionally followed by a '-' and another ':'-separated pattern list (called the negative patterns). For example, run FGMRES tests with the following commands:

cd [BUILD_DIR]/clients/tests
./rocalution-test --gtest_filter=*fgmres*

Benchmarks

NOT YET IMPLEMENTED

Verbose Output

rocALUTION provides different levels of output messages. They can be set in the file src/utils/def.hpp before the compilation of the library. By setting a higher level, the user will obtain more detailed information about the internal calls and data transfers to and from the accelerators.

To avoid all MPI processes to print information on the screen the default configuration is that only RANK 0 outputs information on the screen. The user can change the RANK or allow all RANK to print by modifying src/utils/def.hpp. If file logging is enabled, all ranks write into corresponding log files.

Debug Output

Debug output will print almost every detail in the program, including object constructor/destructor, address of the object, memory allocation, data transfers, all function calls for matrices, vectors, solvers and preconditioners. The debug flag can be set in src/utils/def.hpp. When enabled, additional assert()s are being checked during the computation. This might decrease the performance of some operations significantly.

File Logging

All output can be logged into a file, the file name will be rocalution-XXXX.log, where XXX will be a counter in milliseconds. To enable file logging you need to edit src/utils/def.hpp.