Ase dynamics update #33
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- add function that identifies the ASE version of the user and calls `Dynamics.run()` appropriately based on that version - update all calls to `Dynamics.run()` within the NFF `nvt.py` file
The test checks that the dynamics run properly (creating the output files correctly) and within a short period of time (to ensure that the default 100-million steps that the ASE dynamics uses by default does not occur).
recisic
previously approved these changes
Apr 19, 2025
Contributor
Author
|
I just removed the references to |
xiaochendu
approved these changes
Apr 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request addresses (or partly addresses) #25 , where recent changes to the ASE package was breaking the calls to
Dynamics.run()in many of our MD calculators in NFF. I added a function that catches the ASE version and callsDynamics.run()appropriately depending on the user's version of ASE. Hopefully, this addition should ease the transition from v. <3.22.0 to >=3.23.0. I also added a test that checks that dynamics run correctly (to produce the output trajectory) and within a reasonable amount of time (i.e., does not run for the now-default 100 million steps in the ASE calculator and instead runs for the 40 steps that are requested).