solaris icon indicating copy to clipboard operation
solaris copied to clipboard

Add more thorough text logging output throughout

Open nrweir opened this issue 5 years ago • 1 comments

At present, there's limited text output generated by solaris throughout the pipeline. There's some scattered verbose argument options for text output, but these are limited. Two steps should be taken:

  1. Come up with a systematic plan for text output. Should this be done using the logging python module, or just through verbosity arguments to various elements of the pipeline? Do we want to try to systematically implement tqdm?

  2. Implement whatever is decided in (1).

nrweir avatar May 21 '19 14:05 nrweir

FYI: I'm going to start implementing this. I'll try to write guidelines as I do so for future logging. Resources that I'm using to guide implementation:

https://docs.python-guide.org/writing/logging/

Will get the root logger at the top level, check and see if it already has a handler associated, and if not it'll generate a "default" handler that sets output level to warning and outputs to stdout. Child loggers will be created at submodules, but no new handlers will be created, so they'll inherit the root handler and formatter. They'll also inherit root reporting level (unless it's set differently within a function or class, which is an option that can be configured).

nrweir avatar Sep 11 '19 18:09 nrweir