Yes.
-Nathan
On Mon, Jun 08, 2015 at 09:17:17AM -0700, Ralph Castain wrote:
> So how is the user going to specify these? -mca oob_base_verbose debug?
>
> > On Jun 8, 2015, at 9:11 AM, Nathan Hjelm wrote:
> >
> >
> > That would work. The standard verbosity levels could be one of those
> > val
So how is the user going to specify these? -mca oob_base_verbose debug?
> On Jun 8, 2015, at 9:11 AM, Nathan Hjelm wrote:
>
>
> That would work. The standard verbosity levels could be one of those
> values but allow any number in the interval [0,100] or any of none,
> error, warn, info, debug,
That would work. The standard verbosity levels could be one of those
values but allow any number in the interval [0,100] or any of none,
error, warn, info, debug, and trace. The standard levels could be
defined as:
enum {
MCA_BASE_VERBOSE_NONE = 0,
MCA_BASE_VERBOSE_ERROR = 1,
MCA_BAS
> static const char* const priorities[] = {
> "ERROR",
> "WARN",
> "INFO",
> "DEBUG",
> "TRACE"
> };
+1
I usually use these levels.
Typical usage:
ERROR:
Print an error message on returning a value other than
OMPI_SUCCESS (and OMPI_ERR_TEMP_OUT_OF_RESOURCE etc.).
WARN:
so what about :
static const char* const priorities[] = {
"ERROR",
"WARN",
"INFO",
"DEBUG",
"TRACE"
};
and merge debug and trace if there should be only 4
Cheers,
Gilles
On Monday, June 8, 2015, Ralph Castain wrote:
> Could we maybe narrow it down some? If we are going t
Could we maybe narrow it down some? If we are going to do it, let’s not make
the mistake of the MCA param system and create so many levels. Nobody can
figure out the right gradation as it is just too fine grained.
I think Nathan’s proposal is the max that makes sense.
I’d also like to see us ap
Nathan,
i think it is a good idea to use names vs numeric values for verbosity.
what about using "a la" log4c verbosity names ?
http://sourceforge.net/projects/log4c/
static const char* const priorities[] = {
"FATAL",
"ALERT",
"CRIT",
"ERROR",
"WARN",
"NOTICE",
"INFO
At the moment we have a loosely enforced standard for verbosity
values. In general frameworks accept anything in the range 0 - 100 with
few exceptions. I am thinking about adding an enumerator for verbosities
that will accept values in this range and certain named constants which
will match with s
