Skip to content

Conversation

@kanduri
Copy link
Collaborator

@kanduri kanduri commented Oct 13, 2025

No description provided.

@kanduri kanduri requested a review from RMeli as a code owner October 13, 2025 21:22
@simonpintarelli
Copy link
Member

cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025

Copy link
Member

@simonpintarelli simonpintarelli left a 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.

@simonpintarelli
Copy link
Member

cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025

@simonpintarelli
Copy link
Member

cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025

Comment on lines 14 to 15
- gromacs@2025.3 +cuda +mpi +hwloc
- gromacs@2023.5 +plumed +cuda +hwloc
Copy link
Member

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?

Copy link
Collaborator Author

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

Copy link
Member

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?

Copy link
Collaborator Author

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!

@simonpintarelli
Copy link
Member

simonpintarelli commented Oct 14, 2025

https://gitlab.com/cscs-ci/ci-testing/webhook-ci/mirrors/551234120955960/1440398897047560/-/jobs/11703142778#L766

==> Error: failed to concretize `gromacs@2023.5+cuda+hwloc+plumed` for the following reasons:
     1. Cannot satisfy 'gromacs@2023.5'
        required because gromacs@2023.5+cuda+hwloc+plumed requested explicitly 
     2. Cannot satisfy 'gromacs@2023.5'

the concretization is failing because version 2023.5 isn't provided by the gromacs package.py.

@kanduri
Copy link
Collaborator Author

kanduri commented Oct 15, 2025

cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025

@kanduri
Copy link
Collaborator Author

kanduri commented Oct 20, 2025

cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025

@kanduri
Copy link
Collaborator Author

kanduri commented Oct 22, 2025

cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025

@RMeli
Copy link
Member

RMeli commented Oct 22, 2025

==> Error: failed to concretize `gromacs@2023+cuda+hwloc+plumed` for the following reasons:
     1. Cannot satisfy 'gromacs@2023'
        required because gromacs@2023+cuda+hwloc+plumed requested explicitly 
     2. Cannot satisfy 'gromacs@2023'

@kanduri I think this concretization error you mentioned is because you are asking explicitly for gromacs@2023, but this version no longer exists in the latest Spack package for GROMACS.

@RMeli
Copy link
Member

RMeli commented Oct 22, 2025

If I understand correctly, it looks like plumed 2.10 (see spack/spack-packages#1990) is compatible with GROMACS 2025.0 (already available in Spack).

@kanduri
Copy link
Collaborator Author

kanduri commented Oct 22, 2025

cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025

@kanduri
Copy link
Collaborator Author

kanduri commented Oct 22, 2025

@kanduri I think this concretization error you mentioned is because you are asking explicitly for gromacs@2023, but this version no longer exists in the latest Spack package for GROMACS.

Yes, this has been addressed

Copy link
Member

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.

@kanduri
Copy link
Collaborator Author

kanduri commented Nov 18, 2025

cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs-pytorch:2025

@kanduri
Copy link
Collaborator Author

kanduri commented Nov 18, 2025

cscs-ci run alps;system=daint;uarch=gh200;uenv=gromacs:2025

@RMeli RMeli mentioned this pull request Dec 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants