Open wusatosi opened 5 months ago
Yes, I think there is an issue with using kokkos version with the CPU device. Does it work if you do not use the kokkos suffixes?
I think your suggested fix 1 prevents LAMMPS from having local atomic energy assignments. I think your suggested fix 2 works on kokkos, but breaks non-kokkos. Can you confirm?
I believe the a better fix would be to uniformize how the local energy is written back to the MLIAPData, similar to the update_pair_forces
which works the same in Kokkos and non-kokkos.
Hi lubbersnick, thanks for replying to this issue and pointing out the effects of both suggestions.
Sorry we are only using hippynn to run the MLMD benchmark, and I don't really have a lot of understanding into testing this without kokkos. If you can provide more instruction on how to attempt to debug this I might be able to help out.
I believe that you can do this by removing the command -sf kk -k on -pk kokkos
options from the command line call to lmp
to run lammps without kokkos.
Hi @wusatosi , were the directions above helpful at all?
I believe that you can do this by removing the command
-sf kk -k on -pk kokkos
options from the command line call tolmp
to run lammps without kokkos.
will attempt, sorry I didn't have to look at this yet
Using hippynn via mliap causes script to fail:
Which points to this if-else branch: https://github.com/lanl/hippynn/blob/f8ed7390beb8261c8eec75580c683f5121226b30/hippynn/interfaces/lammps_interface/mliap_interface.py#L84-L89
Known fixes (which we are unsure if is correct) is:
eatoms = atom_energy.numpy().astype(np.double)
if return_device=='cpu'
branch.