Is your feature request related to a problem? Please describe.
Debugging information from the system is currently limited, and when Marius is installed with pip, the full c++ stack trace is hidden from users and only the error message will be output, as in #55.
We currently have a debug log level, which needs to be better utilized to print out useful debug information at reasonable spots in the code.
Describe the solution you'd like
Detailed debug logs should be created for major checkpoints in the code: reading the config, creating storage objects, initializing the model, ...
A python script based on the above torch script should be added as separate python tool marius_environment.
JasonMoho
commented
2 years ago
Is your feature request related to a problem? Please describe. Debugging information from the system is currently limited, and when Marius is installed with pip, the full c++ stack trace is hidden from users and only the error message will be output, as in #55.
We currently have a debug log level, which needs to be better utilized to print out useful debug information at reasonable spots in the code.
Also, we should make it easier for users to report their environment, like PyTorch does with this script: https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
Describe the solution you'd like Detailed debug logs should be created for major checkpoints in the code: reading the config, creating storage objects, initializing the model, ...
A python script based on the above torch script should be added as separate python tool
marius_environment.