Jim Bosch, may you please review this ticket that removes pex_logging dependency from afw?
I find all loggers of distinct names in afw use no more than one Debug/Trace level, except (lsst.)afw.math, so I convert all debugging/tracing except afw.math to log at lsst.log DEBUG level. For afw.math with multiple tracing levels, I use the prefix (TRACEn.afw.math.component, where n=1-5) as discussed in RFC-203. afw.math loggers use Trace 3,4,5,6 in pex.logging and I converted them into TRACE2, TRACE3, TRACE4, and TRACE5 (one lower in the number).
I tried to group different types of logging usages into different commits; hopefully that makes the conversion clearer.
In some tests and examples there are debugging placeholders such as
lsst::pex::logging::Trace::setVerbosity("afw.component", 5)
|
lsst.pex.logging.Trace_setVerbosity("afw.component", 0)
|
lsst.pex.logging.Debug("afw.componrnt", 0)
|
Some of them seem outdated in the master because they set logging levels for non-existent loggers. I manually ran some tests and examples to see where the logging messages came from and updated the debugging placeholders if I was able to guess what the author meant originally.
Jenkins passed.
Besides afw, minor changes are done in the following packages for correcting the dependency.
- shapelet, meas_base, meas_extensions_simpleShape, obs_subaru: Removing the pex_logging dependency in swig files.
- pipe_base, meas_algorithms: correct the hidden pex_logging dependency in ups.
Ran a Jenkins just to double-check some pex_logging includes can be removed regardless of the logging framework migration:
https://ci.lsst.codes/job/stack-os-matrix/label=centos-7,python=py2/14894//console