View Source

{tip}
HPC-BC is an effort to setup a common well-documented environment across multiple HPC sites.

HPC Baseline Configuration (BC) is an effort to define a common set of capabilities and functions so that users can work more productively and collaboratively when using the HPC resources at multiple computing centers within the LinkSCEEM-2 project context. This will be accomplished by defining and developing a common set of capabilities and functions so that users can focus energy on their research as opposed to wrestling with center-specific policies and procedures.

It is modeled after a similar effort taking place elsewhere among 6 HPC sites and in effect it is an extension upon it: [HPC-BC|http://www.ccac.hpc.mil/consolidated/bc]
The effort of that BC team keeps marching on helping users work more productivity by updating existing policies to accommodate new users, integrating new capabilities that must be consistent across the enterprise, or just providing a sounding board for users experiencing difficulties with an HPC environment.
{tip}

{info}
Keywords like MUST, MAY, SHOULD, RECOMMENDED are used in accordance with [RFC2119|http://www.ietf.org/rfc/rfc2119.txt]
{info}

{toc}

h1. About the Baseline Configuration

There is a growing community of LinkSCEEM-2 users who need to work on data\- and computation-intensive problems spread across multiple computing centers and services. Recent discussions show that over half of users may need accounts at more than one center.

The main goal of the HPC Baseline Configuration activity is to define and establish a common set of capabilities and functions so that users can compute productively and collaboratively when using the HPC resources at multiple computing centers.



h1. Compliance Matrix

Use [notation help|http://eniac.cyi.ac.cy/renderer/notationhelp.action?section=misc] for (/)(x)(y)(n)(i)(!) (respectively standing for: yes, no, agree, disagree, information notice, attention notice)

|| || Participating Shared Resource Centers are BA, CyI, NARSS || || || ||
|| Policy tag # || Policy Topics || BA || CyI || NARSS ||
|| [LS2_05-01|LS2_05-01] | Multiple-Version Software | (/) | (/) | (y) ||
|| [LS2_05-05|LS2_05-05] | Queue Names | (/)\\ | (/) | ||
|| [LS2_05-06|LS2_05-06] | Login Shells | (/) | (/) | (y) ||
|| [LS2_06-01|LS2_06-01] | Open Source Math Libraries | (/) | (/) | (y) ||
|| [LS2_06-04|LS2_06-04] | Editors and Scripting Tools | (/)\\ | (/) | (y) ||
|| [LS2_06-05|LS2_06-05] | Set of Debuggers | (/) | (/) | ||
|| [LS2_06-15|LS2_06-15] | Sample Code Repository | (/) | (/) | (y) ||
|| [LS2_06-17|LS2_06-17] | Multiple-Version Software Access via Modules | (/) | (/) | (y) ||
|| [LS2_06-19|LS2_06-19] | Open Source Utilities | (/) | (/) | (y) ||
|| [LS2_07-02|LS2_07-02] | Open Source Performance and Profiling Tools | (/) | (/) | (y) ||
|| [LS2_07-03|LS2_07-03] | Common Set of Open Source Compilers | (/) | (/) | (y) ||
|| [LS2_10-01|LS2_10-01] | New/Returning User Welcome Letter | (/) | (/) | (y) ||
|| [LS2_10-02|LS2_10-02] | Common Open Source High Productivity Languages | (/) | (/) | (y) ||
|| [LS2_11-99|LS2_11-99] | GPU Productivity Environment | N/A | (/) | N/A ||
|| [LS2_11-98|LS2_11-98] | Common Set of Environment Variables | (/) | (/) | ||
|| [LS2_11-97|LS2_11-97] | Climate Science Productivity Environment |(/) | (/) | ||
|| [LS2_11-96|LS2_11-96] | Common Set of Commercial Compilers | (/) | (/) | ||
|| [LS2_11-95|LS2_11-95] | Molecular Dynamics Productivity Environment |(/) | (/) | ||

{note}
Non-Compliance Disclaimer

Site compliance assures that the minimum guidelines of the policy have been met by the Center.
Centers may, at their discretion, exceed the minimum guidelines and still remain in compliance.
Periodic checks will be performed to ensure compliance is maintained.

Note, there may be valid reasons for not being compliant with a policy. For example, non-compliance may be acceptable if it prevents removal of an existing capability or function from the Center's systems or if the HPC system affected is scheduled for decommissioning in the near future.

*Non-compliance is fine, as long as the documentation above is correct and the users are informed.*
{note}