-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config fix #737
Config fix #737
Conversation
Codecov ReportAttention: Patch coverage is
|
"Detected old config, converting to new format. Consider updating to avoid potential incompatibilities." | ||
) | ||
|
||
# do we need a copy? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lbluque I think we might, otherwise the underlying config can change. I think i might have seen this somewhere were a notebook or someone was using this directly, without a call through main.py
* config fix * config compatibility in ase calc * check if eval_metrics is present * handle existing empty loss_functions dicts
* config fix * config compatibility in ase calc * check if eval_metrics is present * handle existing empty loss_functions dicts Former-commit-id: 2dcec1ac42caadd73a59ba862a28d3e08b72fcf5
* config fix * config compatibility in ase calc * check if eval_metrics is present * handle existing empty loss_functions dicts Former-commit-id: a53a950b73ce03051cb0a1084c9740ad0f30230f
Handle updating checkpoints with new format configs that were saved with 'loss_fns' and 'eval_metrics' according to #724