-
Notifications
You must be signed in to change notification settings - Fork 26
WIP:gromacs recipe draft with spack 1.x #256
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
base: main
Are you sure you want to change the base?
Conversation
|
cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be great to add a readme.md in repo and describe what has been changed in gromacs and plumed recipes wrt to upstream spack-packages repository.
|
cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025 |
This reverts commit 4dedfdc.
|
cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025 |
| - gromacs@2025.3 +cuda +mpi +hwloc | ||
| - gromacs@2023.5 +plumed +cuda +hwloc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kanduri is there a good way to merge it into one and have a single version of GROMACS with PLUMED?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes there is. Once this one works reliably, I aim to use the post-install script to manually install PLUMED as the spack recipes aren't updated.
But current priority is to deliver a new GROMACS with CUDA 12.9 because some users need the newer CUDA for interfacing with PyTorch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that this is the official GROMACS uenv for all users, I think it would be good to unify the recipe if there is a way to do things cleanly.
Once this one works reliably, I aim to use the post-install script to manually install PLUMED as the spack recipes aren't updated.
Why not just updating the Spack recipe ourselves? (I think I mentioned this before. I can look into it, I'll have to do it anyways for some PLUMED extensions I need to ship as part of PASC.)
But current priority is to deliver a new GROMACS with CUDA 12.9 because some users need the newer CUDA for interfacing with PyTorch
If this is an urgent request, maybe it can be serviced quickly via a uenv build in the service:: namespace, and do the official GROMACS uenv in an unified way?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is an urgent request, maybe it can be serviced quickly via a uenv build in the service:: namespace, and do the official GROMACS uenv in an unified way?
This sounds like a good idea!
the concretization is failing because version |
|
cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025 |
|
cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025 |
|
cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025 |
@kanduri I think this concretization error you mentioned is because you are asking explicitly for |
|
If I understand correctly, it looks like plumed 2.10 (see spack/spack-packages#1990) is compatible with GROMACS |
|
cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025 |
Yes, this has been addressed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The configuration contains modules: false. If that is intended, this file is not necessary.
|
cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs-pytorch:2025 |
|
cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025 |
No description provided.