New user self-registration is currently disabled. Please email eigen-core-team @ lists.tuxfamily.org if you need an account.
Bug 1148 - PaStiX support: impossible to get rid of the welcome message
PaStiX support: impossible to get rid of the welcome message
Status: RESOLVED FIXED
Product: Eigen
Classification: Unclassified
Component: Sparse
3.3 (current stable)
All All
: Normal Unknown
Assigned To: Nobody
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-01-20 13:56 UTC by fabien chêne
Modified: 2016-01-20 17:56 UTC (History)
2 users (show)



Attachments

Description fabien chêne 2016-01-20 13:56:23 UTC
Quite annoying, it is not possible to get rid of the PaStix welcome message when declaring a solver.

#include <Eigen/PaStiXSupport>

template <class SOLVER>
void f()
{
    SOLVER solver; // gossip
    solver.iparm(IPARM_VERBOSE) = API_VERBOSE_NOT; // too late
    // next actions are silent
}

int main()
{
    f<PastixSolverLDLT>();
    f<PastixSolverLLT>();
    f<PastixSolverLU>();
}

The code above displays the welcome message three times. This is annoying when one need to create a solver frequently, and causes a performance issue as well.

Here is the welcome message I am talking about:

AUTOSPLIT_COMM : global rank : 0, inter node rank 0, intra node rank 0, threads 1
 +--------------------------------------------------------------------+
 +              PaStiX : Parallel Sparse matriX package               +
 +--------------------------------------------------------------------+
 +--------------------------------------------------------------------+
 +  Options                                                           +
 +--------------------------------------------------------------------+
... etc

Could the default verbosity be set to API_VERBOSE_NOT ? Or provide a mecanism to silent it ?
Comment 1 Gael Guennebaud 2016-01-20 17:56:54 UTC
Indeed, the default should be API_VERBOSE_NOT!

https://bitbucket.org/eigen/eigen/commits/6a1f6c421685/

Note You need to log in before you can comment on or make changes to this bug.