|
1 | 1 | What if there was a way to avoid having to install a broad range of scientific software from scratch on every HPC |
2 | 2 | cluster or cloud instance you use or maintain, without compromising on performance? |
3 | 3 |
|
4 | | -Installing scientific software for supercomputers is known to be a tedious and time-consuming task. Especially as the |
5 | | -HPC user community becomes more diverse, computational science expands rapidly, the diversity of system architectures |
6 | | -increases the application software stack continues to deepen. Simultaneously, we see a surge in interest in cloud |
7 | | -computing for scientific computing. Delivering optimised software installations and providing access to these |
| 4 | +Installing scientific software for supercomputers is known to be a tedious and time-consuming task. The application |
| 5 | +software stack continues to deepen as the |
| 6 | +HPC user community becomes more diverse, computational science expands rapidly, and the diversity of system architectures |
| 7 | +increases. Simultaneously, we see a surge in interest in public cloud |
| 8 | +infrastructures for scientific computing. Delivering optimised software installations and providing access to these |
8 | 9 | installations in a reliable, user-friendly, and reproducible way is a highly non-trivial task that affects application |
9 | 10 | developers, HPC user support teams, and the users themselves. |
10 | 11 |
|
11 | | -This tutorial aims to address these challenges by providing the attendees with the knowledge to stream optimised |
12 | | -scientific software. For this, the tutorial introduces European Environment for Scientific Software Installations |
| 12 | +This tutorial aims to address these challenges by providing the attendees with the tools to \emph{stream} the optimised |
| 13 | +scientific software they need. The tutorial introduces European Environment for Scientific Software Installations |
13 | 14 | (\emph{EESSI}), a collaboration between various European HPC sites \& industry partners, with the common goal of |
14 | | -creating a shared repository of scientific software installations that can be used on a variety of systems, regardless |
15 | | -of which flavor/version of Linux distribution or processor architecture is used, or whether it’s a full size HPC |
| 15 | +creating a shared repository of scientific software installations (\emph{not} recipes) that can be used on a variety of |
| 16 | +systems, regardless |
| 17 | +of which flavor/version of Linux distribution or processor architecture is used, or whether it's a full size HPC |
16 | 18 | cluster, a cloud environment or a personal workstation. |
17 | 19 |
|
18 | 20 | We cover the usage of EESSI, different ways to accessing EESSI, how to add software to EESSI, and highlight some more |
19 | | -advanced features. We will also show how to engage with the community and contribute to the project. |
| 21 | +advanced features. We will also show attendees how to engage with the community and contribute to the project. |
0 commit comments