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
Provide popular PRACE packages, ensure they are available as a meta-module #82
Comments
|
Moved from easybuilders/easybuild-framework#333 |
|
Updating status as of v2.2.0: Required ComponentsApplication name and remarks follow:
Python moduleThere is also an apparent need for an extended Python module, covering
PRACE CPE Compatibility - issue objectiveFinally, the PRACE CPE is the compatibility layer centers strive to be compliant against:
As per the following, some aliasing work will be required (or it can be done via alt. namespace): [1] provide an alias to the recommended, highest performance, library or utility, supporting the platform recommended compiler. In case of a library, this might be fully contained in another product. If a recommended vendor library does not fully contain the module file library (including its API), separate libraries must be provided (e.g. IBM ESSL). btw. sources to bootstrap some easyconfigs needed above - some are working alreadyMockup -untested- versions for some of the missing small items above can be found at: Default PRACE module dependencies and variablesThe PRACE module should automatically bring up as dependencies (ie. behave as an extended toolchain): PRACE Applications - this is fyi. onlyFinally, these apps have to be available as modules, too:
PRACE Benchmarks - this is fyi. onlyFor completeness -but not a prerequisite to resolve this issue-, here are the applications selected for the PRACE application benchmark suite:
Ref: http://www.hpcwire.com/hpcwire/2010-02-15/prace_benchmark_suite_finalised.html |
|
Hoi *, Getting ready to contribute the first iteration of the PRACE environment during the hackathon @ Cyprus: Toolchains tested: We still have some way to go as regards minor tools and also variables, as defined here: Overall, it's looking good but gives some errors with the The upcoming hackathon in Nicosia next week is a prime opportunity to follow up on the issues, Don't be dismayed to give it a try, its status is already pretty good for the majority of users; enjoy, |
|
Progress report: |
|
this feels like necroposting, nevertheless here is some newer information in relation to $subject: It basically has explicit instructions/info about the PRACE benchmark suite's components:
|
|
Oh they even added Now it's getting interesting... I've been looking for a decent TensorFlow benchmark for a while now. |
(originally by @fgeorgatos)
most of the content on this has been shamelessly copied^H^H^H^H^H^H borrowed from:
https://openwiki.uninett.no/metacenter:reference:noturcpe
The text was updated successfully, but these errors were encountered: