-
Notifications
You must be signed in to change notification settings - Fork 19
test: Dissolve2 AtomShake unit test #2282
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
test: Dissolve2 AtomShake unit test #2282
Conversation
46bc26f to
3ce285f
Compare
trisyoungs
left a comment
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.
One other general comment - for consistence with writing these sorts of tests in code we should use atom indices from 0 - (N-1) and avoid having to subtract one (this might be irrelevant, assuming that the data blocks disappear....)
c2150b4 to
6ae5e40
Compare
1c90d75 to
30b9452
Compare
c58d191 to
6adda51
Compare
trisyoungs
left a comment
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.
Two minor suggestions (first one might break the formatting, so best check if you include it) but looks good to go!
2210cd9 to
244acb6
Compare
This PR will probably need to encompass a few developments in order to get a successful porting of the
atomShaketest into Dissolve2 node-graph framework.ConfigurationNode,InsertNode) to ensure that downstream changes such as resetting the temperature of the configuration do not result in the generator steps re-runningatomShakeusing a combination ofSpeciesNode, andAtomicMCNodeinside aLoopGraph