You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The KokkosKernelsHandle has a bool option for verbose output that can be set with set_verbose(bool) and checked with get_verbose(). We should use this consistently throughout the library, instead of the macro VERBOSE. Right now, SpGEMM is using the general handle version. The SpTRSV handle has its own verbose flag, and Gauss-Seidel and D1/D2 coloring are using the macro. But all of these take the general handle so that flag is available.
For smaller/simpler features that don't use the handle, I don't think there's much need for enabling verbose output at runtime. We can just push detailed output for those things into the unit tests/perf tests.
The text was updated successfully, but these errors were encountered:
The KokkosKernelsHandle has a bool option for verbose output that can be set with
set_verbose(bool)
and checked withget_verbose()
. We should use this consistently throughout the library, instead of the macroVERBOSE
. Right now, SpGEMM is using the general handle version. The SpTRSV handle has its own verbose flag, and Gauss-Seidel and D1/D2 coloring are using the macro. But all of these take the general handle so that flag is available.For smaller/simpler features that don't use the handle, I don't think there's much need for enabling verbose output at runtime. We can just push detailed output for those things into the unit tests/perf tests.
The text was updated successfully, but these errors were encountered: