-
Notifications
You must be signed in to change notification settings - Fork 41
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
ForceLJ::compute_fullneigh #3
Comments
The full neighbor list by design doesn't need atomics because work is duplicated to avoid write conflicts. |
jasonsewall-intel
pushed a commit
to jasonsewall-intel/miniMD
that referenced
this issue
Feb 19, 2019
Should have been part of Mantevo#3.
jasonsewall-intel
pushed a commit
to jasonsewall-intel/miniMD
that referenced
this issue
Feb 19, 2019
Bug introduced in Mantevo#3 but was hidden by clang.
jasonsewall-intel
pushed a commit
to jasonsewall-intel/miniMD
that referenced
this issue
Feb 19, 2019
Should have been part of Mantevo#3.
jasonsewall-intel
pushed a commit
to jasonsewall-intel/miniMD
that referenced
this issue
Feb 19, 2019
Bug introduced in Mantevo#3 but was hidden by clang.
nmm0
added a commit
to nmm0/miniMD
that referenced
this issue
Dec 17, 2020
Resolve "mismatched resilience defines" Closes Mantevo#3 See merge request kokkos-resilience/minimd!4
nmm0
pushed a commit
to nmm0/miniMD
that referenced
this issue
Dec 17, 2020
Should have been part of Mantevo#3.
nmm0
pushed a commit
to nmm0/miniMD
that referenced
this issue
Dec 17, 2020
Bug introduced in Mantevo#3 but was hidden by clang.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there ,,,
It may there is an issue with the ForceLJ::compute_fullneigh function in computing on the following lines
f[iPAD+0]+=fix
f[iPAD+1]+=fiy
f[i*PAD+2]+=fiz
they are should be protected similarly to half neighbour list force computation by using
#pragma omp atomic
f[iPAD+0]+=fix
#pragma omp atomic
f[iPAD+1]+=fiy
#pragma omp atomic
f[i*PAD+2]+=fiz
I know this have been highlighted as non-threaded function but still with mpi one processor it shows the different results for the same physical configuration ... you may compare the results between threaded halfneighbor and the fullneighbor results are different ...
the other option ofcourse to create threaded function for fullneighbor as have been done for halfneighbor.
please confirm if should be fixed or you have another opinion on this point.
The text was updated successfully, but these errors were encountered: