Current code uses logging in a limited way. It is in particular not using standard declaration of a logger which would allow to configure the logging level more easily.
An implementation of such a functionality is available in PR #15 .
A more in depth usage, could also be considered. Current messages in INFO level would probably be more adapted to DEBUG level. The possibility to implement more levels, e.g. MOREINFO between INFO and DEBUG could also be considered but this is not standard.
Also, we should decide if the log level should be configurable as an input to the classes (like ctapipe tools) or externally with a line like this logging.getLogger('acceptance_modelisation').setLevel(logging.INFO).
List of open items :
Current code uses logging in a limited way. It is in particular not using standard declaration of a logger which would allow to configure the logging level more easily.
An implementation of such a functionality is available in PR #15 .
A more in depth usage, could also be considered. Current messages in INFO level would probably be more adapted to DEBUG level. The possibility to implement more levels, e.g. MOREINFO between INFO and DEBUG could also be considered but this is not standard.
Also, we should decide if the log level should be configurable as an input to the classes (like ctapipe tools) or externally with a line like this
logging.getLogger('acceptance_modelisation').setLevel(logging.INFO).List of open items :