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

Fail to run MD simulation with DP (pytorch backend) #3907

Closed
ZhihaoXu0313 opened this issue Jun 25, 2024 · 3 comments
Closed

Fail to run MD simulation with DP (pytorch backend) #3907

ZhihaoXu0313 opened this issue Jun 25, 2024 · 3 comments

Comments

@ZhihaoXu0313
Copy link

Summary

Hi,

I encountered an issue when I was using DP for MD simulation (.pth model, from pytorch backend). The model can be successfully loaded but following the error:

image
image

(sorry for the screen photo)

I wonder where could this issue coming from? Since the model seems to be good since it can be normally used for inference with Python API and there's no error occurs when using dp commands.

Best

DeePMD-kit Version

DeePMD-kit v3.0.0a0

Backend and its version

PyTorch

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

No response

Details

See above

@CaRoLZhangxy
Copy link
Collaborator

MD simulation for dpa2 model is supported at 2024Q1 branch and multiprocess MD is supported at devel branch. Note that your model should be freeze with the same code version with your c++ inference code version. (Sometimes model trained with old version can not be freezed by a newer one )

@ZhihaoXu0313
Copy link
Author

Thank you so much for the response!

All of the works are under the same code (train, freeze, test, etc), so I guess there's no version issue at all. I'm now using the devel branch (I'll double check it later), so according to your information, it will be fine to use use that for MD simulation, right? What is the multiprocess MD simulation you meant?

Thanks again for your further explanation!

@njzjz
Copy link
Member

njzjz commented Jun 26, 2024

Duplicate of #3428

@njzjz njzjz marked this as a duplicate of #3428 Jun 26, 2024
@njzjz njzjz closed this as not planned Won't fix, can't repro, duplicate, stale Jun 26, 2024
@njzjz njzjz added duplicate and removed wontfix labels Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants