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

LAMMPS fix dplr issue #3679

Open
cesaremalosso opened this issue Apr 17, 2024 · 6 comments · May be fixed by #4084
Open

LAMMPS fix dplr issue #3679

cesaremalosso opened this issue Apr 17, 2024 · 6 comments · May be fixed by #4084
Assignees
Labels
bug reproduced This bug has been reproduced by developers

Comments

@cesaremalosso
Copy link

Summary

ERROR: find a bonded pair that is not on the same processor, something should not happen (../fix_dplr.cpp:345) when restart from a previous simulation run.

DeePMD-kit Version

2.2.3

Backend and its version

2.13.0

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

No response

Details

Hi,

I'm encountering the following error:
ERROR: find a bonded pair that is not on the same processor, something should not happen (../fix_dplr.cpp:345)

when I try to restart a LAMMPS run from the previous ended one. I'm using a DPLR model and I'm running it just with 1 MPI process (mpirun -np 1) for the LAMMPS lmp_mpi. I attach the input file for LAMMPS as well as the two restart file from the previous run

files.zip

@njzjz njzjz added bug reproduced This bug has been reproduced by developers and removed wontfix labels Apr 17, 2024
@cesaremalosso
Copy link
Author

Hi, has this issue been fixed?

@Yi-FanLi
Copy link
Collaborator

Hi, has this issue been fixed?

Hi @cesaremalosso, I am sorry that I was so overwhelmed in the past few weeks. In the recent days I have more time. I am working on this issue. Thanks for your patience.

@cesaremalosso
Copy link
Author

cesaremalosso commented Aug 24, 2024

Thank you very much @Yi-FanLi ! I have another related question. It seems that the kspace_style pppm/dplr, which is used to account for the long-range interactions, is quite slow in LAMMPS, significantly slowing down the MD simulation. Do you think it would be beneficial to implement OpenMP thread parallelization to speed this up? Perhaps using GPUs for both the short-range NNP and the Wannier NN, while using CPU processes for the particle-particle particle-mesh solver?

@njzjz
Copy link
Member

njzjz commented Aug 26, 2024

Perhaps using GPUs for both the short-range NNP and the Wannier NN, while using CPU processes for the particle-particle particle-mesh solver

This is the current implementation. pppm/dplr is based on pppm and the pppm solver is implemented in LAMMPS.

I know pppm has some variants, such as pppm/gpu, pppm/omp, pppm/intel, but they need to be tested.

Could you raise a separate issue?

@cesaremalosso
Copy link
Author

cesaremalosso commented Aug 26, 2024

Hi @njzjz , I raised a separate issue here: #4078

@Yi-FanLi
Copy link
Collaborator

Thank you very much @Yi-FanLi ! I have another related question. It seems that the kspace_style pppm/dplr, which is used to account for the long-range interactions, is quite slow in LAMMPS, significantly slowing down the MD simulation. Do you think it would be beneficial to implement OpenMP thread parallelization to speed this up? Perhaps using GPUs for both the short-range NNP and the Wannier NN, while using CPU processes for the particle-particle particle-mesh solver?

Hi @cesaremalosso, I am replying to you in #4078 : )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug reproduced This bug has been reproduced by developers
Projects
Development

Successfully merging a pull request may close this issue.

3 participants