-
Notifications
You must be signed in to change notification settings - Fork 5
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
ATS-2095/ZEN-30304 - expanse/0.17.3/gpu/b - Missing LAMMPS GPU (example application) #56
Comments
I'm still having runtime problems with the GPU-enabled version(s) of LAMMPS. |
User request now. Changed issue subject line to include ACCESS ticket. |
Reconfirming that we currently only have LAMMPS deployed in the
|
Documenting the complete spec for both versions currently available in
|
Again, reconfirming there is currently no LAMMPS package installed within
|
This is the last spec build script configuration built and tested, which suffered from a persistent runtime error on the standard LJ benchmark.
|
TSCC2 has a deployed LAMMPS build.
Its complete spec is as follows:
|
It is difficult to tell at a glance what the custom changes are in the
|
|
I find no difference between
|
|
|
Attempting to change
|
Starting build process with
|
|
Next running
|
Build succeeded.
|
Finally, running new
|
Initial build failed. Investigating ...
|
Related to the
|
The answer appears to be YES. Removing the
|
Build ready for testing.
|
Previous runtime error.
|
Built and deployed a new install of lammps@20210310 within the new [email protected] package dependency chain added to expanse/0.17.3/gpu/b to support amber@22.
|
@nwolter - Ready for testing. |
|
Interesting. Spider command does not show version you have listed above on login nodes on Expanse for me. The openmpi version you show above is not available?
gpu]$ module spider lammps/20210310/a6zspha-omp lammps/20210310: lammps/20210310/a6zspha-omp
|
to fix issue I deleted the lmod.d, but this is the official explanation. If your site adds a new modulefile to the site’s $MODULEPATH but are unable to see it with module avail? It is likely that your site is having an spider cache issue. If you see different results from the following commands then that is the problem: $ module --ignore_cache avail If you see a difference between the above two commands, delete (if it exists) the user’s spider cache: $ rm -rf ~/.cache/lmod ~/.lmod.d/cache |
Build spec script and standard output committed back to deployment branch. |
@nwolter @mahidhar - We still need to create an updated example for expanse/0.17.3/gpu/b.
We have this version ...
... and this version now.
I think the only major difference is PLUMED is supported for
|
I'll get on this |
No description provided.
The text was updated successfully, but these errors were encountered: