-
Notifications
You must be signed in to change notification settings - Fork 710
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
{chem}[foss/2024a] GPAW v25.1.0 w/ ASE 3.24.0 #22140
base: develop
Are you sure you want to change the base?
{chem}[foss/2024a] GPAW v25.1.0 w/ ASE 3.24.0 #22140
Conversation
Updated software
|
GPAW is two packages, the code (GPAW) and the PAW setup data files (GPAW-setups). It is done this way so users can easily switch to another GPAW-setups package if they need to - newer or older depending on the scientific project they are running. However, we recently updated the setups, and released a new package which also includes setups for Lanthanides. It would be borderline evil to release the newest GPAW with easybuild packages using the now outdated packages. But this causes the test suite to fail, as two different packages in the same toolchain depends on different versions of the same package. Normally very reasonable, but in this case all involved packages are GPAW packages, and not more than one can be loaded at the same time. Is there some way to overrule the automatic test? |
(created using
eb --new-pr
)