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

Using the DP model to predict the energy of each frame structure in the LAMMPS trajectory #609

Open
XuFanffei opened this issue Feb 22, 2024 · 1 comment
Labels
enhancement New feature or request lammps

Comments

@XuFanffei
Copy link

Summary

I now have a lambps trajectory that contains many structures, but these structures are not the original lambps trajectory structure, but some extracted molecular clusters. Therefore, the number of atoms or types of elements in each frame may be different, but overall they are several elements contained in the original trajectory. But for this manually spliced lambps trajectory, the model's predicted code will report an error. One method is for me to extract each molecular cluster into a separate lambps trajectory, write a script to read each file, and achieve energy prediction, but the efficiency is too slow because I have tens of thousands of molecular cluster structures.

DeePMD-kit Version

2.1.5

TensorFlow Version

2.8.0

Python Version, CUDA Version, GCC Version, LAMMPS Version, etc

No response

Details

1091706144749_ pic
1101706144789_ pic

@XuFanffei XuFanffei added the wontfix This will not be worked on label Feb 22, 2024
@njzjz njzjz transferred this issue from deepmodeling/deepmd-kit Feb 22, 2024
@njzjz njzjz added enhancement New feature or request lammps and removed wontfix This will not be worked on labels Feb 22, 2024
@wanghan-iapcm
Copy link
Contributor

better to write py script who calls the dp's python interface to inference different data frames.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request lammps
Projects
None yet
Development

No branches or pull requests

3 participants