Multi-level logging

[argiopetech]

Support multiple levels of logging, in addition to the standard output to data files.

Logging levels should include:

1. No output
2. Information messages (start, stop, cholesky decomp matrix) to stdout
3. Diagnostic messages (-Inf posteriors, wd bounds, interp/extrap pins, other pre-existing loggable diagnostics from 9.2.1) to stderr and baseName.log
4. Debug messages (output of proposed cluster data with accept/reject column) to basename.res.debug and basename.res.burnin.debug.

All levels shall include the levels below them. Levels shall be set with a verbosity flag --verbose=, -v. -q and --quiet shall be synonymous with -v0.

[tedvh]

good idea!

On 7/20/13 4:10 PM, Elliot Robinson wrote:

Support multiple levels of logging, in addition to the standard output to data
files.

Logging levels should include:
0. No output

1. Information messages (start, stop, cholesky decomp matrix) to stdout
2. Diagnostic messages (-Inf posteriors, wd bounds, interp/extrap pins, other
   pre-existing loggable diagnostics from 9.2.1) to stderr and baseName.log
3. Debug messages (output of proposed cluster data with accept/reject column) to
   basename.res.debug and basename.res.burnin.debug.

All levels shall include the levels below them. Levels shall be set with a
verbosity flag --verbose=, -v. -q and --quiet shall be synonymous with -v0.

—
Reply to this email directly or view it on GitHub
#34.

Ted von Hippel

Department of Physical Sciences
Embry-Riddle Aeronautical University
600 S. Clyde Morris Boulevard
Daytona Beach, FL 32114-3900
386-226-7751