-
Notifications
You must be signed in to change notification settings - Fork 486
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
Will connecting ZBL affect DP's description of equilibrium states #2647
Comments
I don't understand why you ask this question. In #1932, |
Thank you for your reply In my input.json, 'sw_rmax' is set to 1.2. However, I statically calculated the change in the energy of the two atoms with distance and found that DP without zbl and DP with zbl have different results. |
please provide the input script of your training, and describe how did you generate the training dataset. |
from the description it is not clear to me how the configurations are explored in dpgen |
Thank you for you reply! If I add a new set of configurations and add zbl related parameters in input.json, and finish the whole process of 01.model_devi,02.fp,00.train, can I connect ZBL-Tab? |
Summary
I compared the DP potential of connected ZBL and unconnected ZBL, and found that the energy changes with distance. It was found that the connection of ZBL would change the DP's description of the equilibrium state. What is the method to make ZBL only effective at short distances without affecting the description of the equilibrium state?
DeePMD-kit Version
2.1.5
TensorFlow Version
null
Python Version, CUDA Version, GCC Version, LAMMPS Version, etc
No response
Details
I have seen #1932 and it seems to be the input.json parameter required to connect to ZBL, but I would like to know if connecting to ZBL will affect DP's description of the equilibrium state.
When I connected ZBL, it was possible that I trained ZBL-Tab with other input configurations, which in turn affected the overall energy weight,Is there a way to only add ZBL-Tab in the last step?
The text was updated successfully, but these errors were encountered: