<commit_before># The Community of Supercomputer Facilities and their Users

Many computational scientists and engineers access high-performance computing resources through one or more centralized supercomputing facilities, which serve many users.

Although the details of the systems, tools, and support resources available can vary greatly from one facility to another, there are many high-level aspects that are common across them.  Due to inherent lifetimes and technoligical change, supercomputer systems must be changed periodically (5 years is typical for supercomputers).  Also, with limited resources available for support and training, facilities must typically focus first and foremost on the systems, tools, and environments that they're fielding at any given moment.  This can pose a challenge for users, who are in many cases using multiple supercomputer facilities simultaneously.  The goal of BSSw in supporting supercomputer facilities and users is to provide a place for information that spans facilities and specific computer architectures, complementing local facility resources, and helps users deal wtih multiple environments in a productive and sustainable way.

There are a vast number of supercomputing facilities around the world, and it is impossible to list them all, but some of used by BSSw contributors include:
<!---
       These could point to the facility pages proper, or to a BSSw "sub-community" page that makes more specific connections between that facility and BSSw content
--->
- [Argonne Leadership Computing Facility](http://www.alcf.anl.gov/)
- [National Energy Research Scientific Computing Center](http://www.nersc.gov/)
- [Oak Ridge Leadership Computing Facility](https://www.olcf.ornl.gov/)

## Software challenges for supercomputer facilities and their users

Performance portablity is often a significant concern for users of multiple facilities. Many facilities offer support to improve the performance of an application of the platform(s) they field, but it is hard for them to speak definitively about an application they are not deeply familiar with on platforms they don't have deep familiarity with either.  Thus, the onus for performance portability is on the users.  In the course of working with facility staff on performance, debugging, or other issues, it is best for everyone when such issues can be quickly isolted and addressed.  This can be greatly facilitated by emphasizing software quality, documentation, and testing during the development process.

## Next steps
- **Explore** the resources below.
- **Get oriented and investigate** all of BSSw's offerings [BSSw Homepage](../Homepage.md).
- **Share your ideas and experiences** about X,Y,Z, and other concerns. See [What To Contribute](../WhatToContribute.md) and [How To Contribute](../HowToContribute.md).

<!--
Featured resources for the Community of Supercomputer Facilities and their Users
Edit this list to change resources that appear on the front-end site.
-->
<commit_msg>Replace XYZ with something concrete.<commit_after># The Community of Supercomputer Facilities and their Users

Many computational scientists and engineers access high-performance computing resources through one or more centralized supercomputing facilities, which serve many users.

Although the details of the systems, tools, and support resources available can vary greatly from one facility to another, there are many high-level aspects that are common across them.  Due to inherent lifetimes and technoligical change, supercomputer systems must be changed periodically (5 years is typical for supercomputers).  Also, with limited resources available for support and training, facilities must typically focus first and foremost on the systems, tools, and environments that they're fielding at any given moment.  This can pose a challenge for users, who are in many cases using multiple supercomputer facilities simultaneously.  The goal of BSSw in supporting supercomputer facilities and users is to provide a place for information that spans facilities and specific computer architectures, complementing local facility resources, and helps users deal wtih multiple environments in a productive and sustainable way.

There are a vast number of supercomputing facilities around the world, and it is impossible to list them all, but some of used by BSSw contributors include:
<!---
       These could point to the facility pages proper, or to a BSSw "sub-community" page that makes more specific connections between that facility and BSSw content
--->
- [Argonne Leadership Computing Facility](http://www.alcf.anl.gov/)
- [National Energy Research Scientific Computing Center](http://www.nersc.gov/)
- [Oak Ridge Leadership Computing Facility](https://www.olcf.ornl.gov/)

## Software challenges for supercomputer facilities and their users

Performance portablity is often a significant concern for users of multiple facilities. Many facilities offer support to improve the performance of an application of the platform(s) they field, but it is hard for them to speak definitively about an application they are not deeply familiar with on platforms they don't have deep familiarity with either.  Thus, the onus for performance portability is on the users.  In the course of working with facility staff on performance, debugging, or other issues, it is best for everyone when such issues can be quickly isolted and addressed.  This can be greatly facilitated by emphasizing software quality, documentation, and testing during the development process.

## Next steps
- **Explore** the resources below.
- **Get oriented and investigate** all of BSSw's offerings [BSSw Homepage](../Homepage.md).
- **Share your ideas and experiences** about making software better across facilities, and how to more productively engage with facility staff. See [What To Contribute](../WhatToContribute.md) and [How To Contribute](../HowToContribute.md).

<!--
Featured resources for the Community of Supercomputer Facilities and their Users
Edit this list to change resources that appear on the front-end site.
-->

{'fraction_non_alphanumeric': 0.050024602263408234, 'fraction_numerical': 0.0003280301787764474, 'mean_word_length': 4.966731898238748, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 2, 'lorem ipsum': 0, 'www.': 6, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2000740', 'n_tokens_mistral': 1372, 'n_tokens_neox': 1292, 'n_words': 824}