You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we were considering overhauling the logging of EB anyway, it might be interesting to consider yaml output for EB logging. This approach is used, for example, by BigDFT.
This would potentially allow us to use log files as input to allow reproduction of bugs, and also facilitate post-processing of log files (different views:minimal, detailed, debug,...).
BigDFT have tips for how to still allow the output to be human readable and grep-able and said they'd be happy to share them
The text was updated successfully, but these errors were encountered:
Is there a reason to use YAML over JSON for logging? https://www.structlog.org/en/stable/ is very nice to work with, and integrates very smoothly into python.
If we were considering overhauling the logging of EB anyway, it might be interesting to consider yaml output for EB logging. This approach is used, for example, by BigDFT.
This would potentially allow us to use log files as input to allow reproduction of bugs, and also facilitate post-processing of log files (different views:minimal, detailed, debug,...).
BigDFT have tips for how to still allow the output to be human readable and grep-able and said they'd be happy to share them
The text was updated successfully, but these errors were encountered: