-
Notifications
You must be signed in to change notification settings - Fork 3
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
added uncertainty checks to jax md #328
Conversation
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.
Great 🎉 one small comment. Also - any chance we can have tests for this? Probably not great without a pre-trained available ensemble model?
apax/md/simulate.py
Outdated
log.info( | ||
f"One or more dynamics checks failed at step: {step+1}" | ||
) |
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.
A failed check is not log.info
but more log.warning
or even log.critical
or log.error
?
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.
Yeah fair. in IPS it is log.critical, I'll change it to that.
pre-commit.ci autofix |
for more information, see https://pre-commit.ci
it would be possible to test, but it takes a long time in the CI to train some model for this |
pre-commit.ci autofix |
yeah ok I can cook up a reasonable test for this. |
pre-commit.ci autofix |
for more information, see https://pre-commit.ci
Now that jaxmd supports tracking uncertainties, we can also use stopping criterions for the simulation loop.
Here I've implemented simple energy and force uncertainty stopping criterions.
closes #319