Description Usage Arguments Value Note See Also Examples
Good logging allows package developers and users to create log files at different
levels to track and debug lengthy or complex calculations. "Python-style" logging is intended
to suggest that users should set up multiple log files for different log severities 
so that the errorLog will contain only log messages at or above the ERROR level while
a debugLog will contain log messages at the DEBUG level as well as all higher
levels.
Python-style log files are set up with logger.setup(). Logs can be set up for any
combination of log levels. Accepting the default NULL setting for any log file
simply means that log file will not be created.
Python-style logging requires the use of logger.debug() style logging statements as seen
in the example below.
1 2  | 
traceLog | 
 file name or full path where   | 
debugLog | 
 file name or full path where   | 
infoLog | 
 file name or full path where   | 
warnLog | 
 file name or full path where   | 
errorLog | 
 file name or full path where   | 
fatalLog | 
 file name or full path where   | 
No return value.
All functionality is built on top of the excellent futile.logger package.
logger.trace logger.debug logger.info
logger.warn logger.error logger.fatal
1 2 3 4 5 6 7 8 9 10 11 12 13 14  | ## Not run: 
# Only save three log files
logger.setup(debugLog='debug.log', infoLog='info.log', errorLog='error.log')
# But allow lot statements at all levels within the code
logger.trace('trace statement #%d', 1)
logger.debug('debug statement')
logger.info('info statement %s %s', "with", "arguments")
logger.warn('warn statement %s', "about to try something dumb")
result <- try(1/"a", silent=TRUE)
logger.error('error message: %s', geterrmessage())
logger.fatal('fatal statement %s', "THE END")
## End(Not run)
 | 
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.