Replies: 1 comment 19 replies
-
You need to run a few hundred maybe a thousand steps to get a good sense of speed, because the neighbour list calculation is not done on every step. |
Beta Was this translation helpful? Give feedback.
19 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I am running the mace LAMMPS gpu , but the computation speed seems unusually low. I am using an RTX 3090 GPU, and I will attach the log file and the file I used for compilation.
The structure I used contains only 12 atoms, so I am wondering if this is the expected performance.
For the MACE model, I downloaded and used the one named "2024-01-07-mace-128-L2_epoch-199.model-lammps" from MACE-MP.
And this is my input file
####input#####
units metal
boundary p p p
atom_style atomic
atom_modify map yes
newton on
read_data ./dat.lammps
pair_style mace no_domain_decomposition
#pair_coeff * * ./2023-12-03-mace-mp.model-lammps.pt Zr O
pair_coeff * * ./2024-01-07-mace-128-L2_epoch-199.model-lammps.pt Zr O
dump myDump all custom 10 xyz.lammpstrj id element x y z
dump_modify myDump sort id element Zr O
thermo_style custom step time cpu pe ke etotal temp press vol density
thermo 10
velocity all create 300.0 12345
fix myEnse all npt temp 300.0 300.0 0.1 aniso 1.0 1.0 1.0
timestep 0.002
run 10
################
lammps.log
lammps-mace compile.txt
Beta Was this translation helpful? Give feedback.
All reactions