Describe the task
Refactor the inconsistent logging and debugging statements throughout the data/src pipeline to create a unified, configurable, and efficient logging system. Currently, a mix of logging calls and print statements are scattered across the codebase with inconsistent implementation, making terminal output verbose and difficult to manage during pipeline execution. While config.py contains some logging configuration functionality, it is not properly integrated throughout the pipeline. This task involves consolidating all output statements into a standardized logging system that is both parsimonious for normal operation and helpful for debugging, with particular attention to managing verbose geometry debugging output.
Acceptance Criteria
Additional context
- Preserve existing
config.py logging functionality where possible, but refactor as needed for consistency
- Pay special attention to geometry processing modules where debug output can become extremely verbose
- Consider both development and production use cases when designing the logging system
- Ensure the solution is maintainable and follows Python logging best practices
Describe the task
Refactor the inconsistent logging and debugging statements throughout the
data/srcpipeline to create a unified, configurable, and efficient logging system. Currently, a mix ofloggingcalls andprintstatements are scattered across the codebase with inconsistent implementation, making terminal output verbose and difficult to manage during pipeline execution. Whileconfig.pycontains some logging configuration functionality, it is not properly integrated throughout the pipeline. This task involves consolidating all output statements into a standardized logging system that is both parsimonious for normal operation and helpful for debugging, with particular attention to managing verbose geometry debugging output.Acceptance Criteria
data/srcdirectory and subdirectoriesprintstatements with appropriateloggingcalls using standard log levelsconfig.pylogging functionalityAdditional context
config.pylogging functionality where possible, but refactor as needed for consistency