Skip to content

add GROMACS v4.6 easyconfigs#165

Merged
boegel merged 12 commits intoeasybuilders:developfrom
fgeorgatos:contrib_GROMACS
Apr 27, 2013
Merged

add GROMACS v4.6 easyconfigs#165
boegel merged 12 commits intoeasybuilders:developfrom
fgeorgatos:contrib_GROMACS

Conversation

@fgeorgatos
Copy link
Copy Markdown
Contributor

highlights:

  • 2 versions supplied, one with CUDA, one without
  • FFTWsp dependency exists, but not included, since we may opt for an FFT-jumbo build
  • easyblock must also be provided later, otherwise there we have no sanity_checks etc.

Ref:

fyi. the current initial code is a synthesis of all these bits (reflected in "authors"):
https://github.com/fgeorgatos/easybuild.experimental/tree/master/users/georgets/g/GROMACS
https://github.com/fgeorgatos/easybuild.experimental/tree/master/users/wiktor/GROMACS
https://github.com/fgeorgatos/easybuild.experimental/blob/master/contrib/pkgsrc/20121109/g/gromacs-4.5.5.eb
I took the freedom to add Kenneth, since I know his magic hand will touch this...

Progress is pending now on the FFT/CUDA business.

Signed-off-by: Fotis Georgatos [email protected]

Signed-off-by: Fotis Georgatos <[email protected]>
Signed-off-by: Fotis Georgatos <[email protected]>
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please break this line, 120 chars is the max

@boegel
Copy link
Copy Markdown
Member

boegel commented Mar 20, 2013

It's worth noting that GROMACS provided a set of regression tests, see http://www.gromacs.org/Downloads .

An easyblock for GROMACS should include a decent sanity check, support for building GROMACS with CUDA, relying on the upcoming CUDA support in the framework, and should also try and build and run the regression tests as part of the build, ideally.

@wjurkowski
Copy link
Copy Markdown
Contributor

I didn't test it myself but according to documentation one can provide -DREGRESSIONTEST_DOWNLOAD to cmake configuration in order to download the regression tests during the installation procedure. This could be in principle added to easyconfig file as one of cmake options.
Then your system would be ready to run
make check
And sanity check would be then done depending on the output of all tests

@fgeorgatos
Copy link
Copy Markdown
Contributor Author

I have no "sane" way to do this, in the sense that going for the
regressions would imply risking a failure at configure time (eg. due to
external network down at that moment). Also, it does not map well with the
idea of "prefetching" all the source tarballs from ftp.hpcbios.org in one
go, nor with situations in which the fetch and configure step have to
happen in a very distinct way (I have met HPC sites where this is the case
due to node access policies).

So, AFAIK unless we hack the cmake configuration we have two ways to go
from here:

  • add -DREGRESSIONTEST_DOWNLOAD anyway, suffering the above situations
  • ignore it all together for now, until we can satisfy the feature request
    in a better way

What do you suggest?

Also, related: should we rewire the CUDA enabled version for goolfc? let's
finalize this...

On Fri, Apr 19, 2013 at 5:01 PM, wjurkowski [email protected]:

I didn't test it myself but according to documentation one can provide
-DREGRESSIONTEST_DOWNLOAD to cmake configuration in order to download the
regression tests during the installation procedure. This could be in
principle added to easyconfig file as one of cmake options.
Then your system would be ready to run
make check
And sanity check would be then done depending on the output of all tests


Reply to this email directly or view it on GitHubhttps://github.com//pull/165#issuecomment-16658188
.

@boegel
Copy link
Copy Markdown
Member

boegel commented Apr 24, 2013

This depends on #191 (after @fgeorgatos merges in fgeorgatos#12).

@boegel
Copy link
Copy Markdown
Member

boegel commented Apr 24, 2013

@wjurkowski: The GROMACS easyconfigs now include running the regression test, so it seems like this is ready to merge in (after #191).

I did notice that the CUDA-enabled build (on top of GCC 4.6.4) required 130s for running the 5 tests, while the non-CUDA build (with GCC 4.7.2) required something like 50s. Does that make any sense to you? Have you seen this?

@boegel
Copy link
Copy Markdown
Member

boegel commented Apr 27, 2013

Required toolchain support (easybuilders/easybuild-framework#603 and #191) is there, so this is ready to be merged in.
The first CUDA-enabled build with EasyBuild! \o/

boegel added a commit that referenced this pull request Apr 27, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants