Python’s inbuilt logging module provides a good way to keep track of the progress of programs such as CLOVER. It provides several levels of logging capability (from debug-only information, upto console-output error information), and wouldn’t be that difficult to integrate.
We would need to decide on where the logging calls would be made, and what information we would want contained in the logs, both for successful runs of CLOVER and to document errors that crop up.
Potentially, some of the information currently outputted to the user (such as “single line optimisation” in section 6.2.2) could be transferred to logging depending on how important it is that the user knows this information whilst CLOVER is running.
Python’s inbuilt
loggingmodule provides a good way to keep track of the progress of programs such as CLOVER. It provides several levels of logging capability (from debug-only information, upto console-output error information), and wouldn’t be that difficult to integrate. We would need to decide on where the logging calls would be made, and what information we would want contained in the logs, both for successful runs of CLOVER and to document errors that crop up. Potentially, some of the information currently outputted to the user (such as “single line optimisation” in section 6.2.2) could be transferred to logging depending on how important it is that the user knows this information whilst CLOVER is running.