You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After deploying an initial spec into production for testing, another user found that OpenMP support is not included. This ticket can be found here: https://sdsc.zendesk.com/agent/tickets/31048
I was able to confirm the issue with OpenMP for both recently installed versions in expanse/0.17.3/gpu/b.
LAMMPS (10 Mar 2021)
using 10 OpenMP thread(s) per MPI task
ERROR: Using suffix omp without USER-OMP package installed (src/src/lammps.cpp:843)
Last command: (unknown)
real 1.10
user 0.11
sys 0.16
LAMMPS (2 Aug 2023)
using 10 OpenMP thread(s) per MPI task
ERROR: Package omp command without OPENMP package installed (src/src/input.cpp:1700)
Last command: package omp 10
real 0.88
user 0.07
sys 0.14
It seems like maybe both the +openmp and +user-openmp variants need to be enabled for OpenMP to be enabled. These are effectively the same codebase, so it's unclear why the Spack package does not properly account for this in its implementation. Something that may need to be fixed. For reference, here are the starting specs for both builds.
Original request can be found here: https://sdsc.zendesk.com/agent/tickets/30304
After deploying an initial spec into production for testing, another user found that OpenMP support is not included. This ticket can be found here: https://sdsc.zendesk.com/agent/tickets/31048
I was able to confirm the issue with OpenMP for both recently installed versions in
expanse/0.17.3/gpu/b
.It seems like maybe both the
+openmp
and+user-openmp
variants need to be enabled for OpenMP to be enabled. These are effectively the same codebase, so it's unclear why the Spack package does not properly account for this in its implementation. Something that may need to be fixed. For reference, here are the starting specs for both builds.I will attempt to enable OpenMP by rebuilding lammps@20230802 with
+user-omp
enabled, keeping+openmp
on as well.The text was updated successfully, but these errors were encountered: