Skip to content
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

4G-HDNNP Prediction and LAMMPS interface #77

Draft
wants to merge 74 commits into
base: master
Choose a base branch
from

Conversation

singraber
Copy link
Member

Implements the predictive capabilities for 4G-HDNNPs (https://arxiv.org/abs/2009.06484)

@singraber singraber added enhancement New feature or request interface Concerns the interface to third-party software core Touches the libnnp core library labels Jan 19, 2021
@singraber singraber self-assigned this Jan 19, 2021
@singraber singraber changed the title 4G-HDNNP Prediction and LAMMPS interface [WIP] 4G-HDNNP Prediction and LAMMPS interface Jan 19, 2021
Result agrees with RuNNer for the AlAuMgO and the carbon chain examples.
@singraber singraber mentioned this pull request Apr 2, 2021
philippmisof and others added 3 commits April 2, 2021 21:30
Forces can now be predicted for periodic and non-periodic case.
Minor change: NL sorting only for 4G-HDNNPs, because it
breaks some tests (numerical accuracy).
@singraber singraber changed the title [WIP] 4G-HDNNP Prediction and LAMMPS interface 4G-HDNNP Prediction and LAMMPS interface Apr 14, 2021
@singraber singraber marked this pull request as draft April 14, 2021 14:49
philippmisof and others added 17 commits April 21, 2021 15:28
Added break condition to avoid loop over unnecessary neighbors. Will be
fixed more elegantely later.
- Fixed invalid read in NN input.
- see "water-test/correct-input-data" for consistent input for
nnp-predict/lammps-nnp.
- Does NOT match yet, further investigation required...
- Reciprocal part still incorrect, k-vectors seem wrong
- Dev version, has unresolved segfaults!
- LAMMPS uses scheme with different cutoff
- With current fix EQeq is now correct
- dEQeq needs to be fixed!
- Maybe that is the limit for double precision?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Touches the libnnp core library enhancement New feature or request interface Concerns the interface to third-party software
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement and test sorted neighbor list
4 participants