Merge pull request #6 from EESSI/aoc

AOC updates for EESSI user tutorial

isc24/EESSI/abstract.tex

@@ -1,9 +1,22 @@
 \comment{sell it first, wouldn't life be easy if...}
 
-What if there was a way to avoid having to install a broad range of scientific software from scratch on every HPC cluster or cloud instance you use or maintain, without compromising on performance?
+What if there was a way to avoid having to install a broad range of scientific software from scratch on every HPC
+cluster or cloud instance you use or maintain, without compromising on performance?
 
-Installing scientific software for supercomputers is known to be a tedious and time-consuming task. Especially as the HPC user community becomes more diverse, computational science expands rapidly, the diversity of system architectures increases the application software stack continues to deepen. On the other hand, a growing interest in cloud computing for scientific computing can be observed. Delivering optimised software installations and providing access to these installations in a reliable, user-friendly way is a highly non-trivial task that affects application developers, HPC user support teams, and the users themselves.
+Installing scientific software for supercomputers is known to be a tedious and time-consuming task. Especially as the
+HPC user community becomes more diverse, computational science expands rapidly, the diversity of system architectures
+increases the application software stack continues to deepen. Simultaneaously, we see a surge in interest in cloud
+computing for scientific computing. Delivering optimised software installations and providing access to these
+installations in a reliable, user-friendly, and reproducible way is a highly non-trivial task that affects application
+developers, HPC user support teams, and the users themselves.
 
-This tutorial aims to address these challenges by providing the attendees with the knowledge to stream optimised scientific software. For this, the tutorial introduces European Environment for Scientific Software Instalations (\emph{EESSI}), a collaboration between various European HPC sites \& industry partners, with the common goal of creating a shared repository of scientific software installations that can be used on a variety of systems, regardless of which flavor/version of Linux distribution or processor architecture is used, or whether it’s a full size HPC cluster, a cloud environment or a personal workstation.
+This tutorial aims to address these challenges by providing the attendees with the knowledge to stream optimised
+scientific software. For this, the tutorial introduces European Environment for Scientific Software Instalations
+(\emph{EESSI}), a collaboration between various European HPC sites \& industry partners, with the common goal of
+creating a shared repository of scientific software installations that can be used on a variety of systems, regardless
+of which flavor/version of Linux distribution or processor architecture is used, or whether it’s a full size HPC
+cluster, a cloud environment or a personal workstation.
 
-We cover the usage of EESSI, different ways to accessing EESSI how to add software to EESSI, troubleshooting, performance evaluation and highlight some more advanced features. We will also show how to engage with the community and contribute to the project.
+We cover the usage of EESSI, different ways to accessing EESSI how to add software to EESSI, troubleshooting,
+performance evaluation and highlight some more advanced features. We will also show how to engage with the community
+and contribute to the project.

isc24/EESSI/attendance.tex

@@ -1,9 +1,9 @@
-\comment{Kenneth: check head count EUM'23}
-
-Based on attendance at previous EESSI and EasyBuild events, including the yearly EasyBuild User Meetings (over 30 attendees in the last physical edition in 2023, close to 100 in 2021 and 2022 in an online setting) and previous tutorials (PRACE-VI-SEEM 2017 Spring School with 25-30 attendees, a free online EasyBuild tutorial in June'20 with about 100 attendees, the half-day ISC'21 tutorial with over 25 attendees, and the in-person (half-day) ISC'22 tutorial with about 20 attendees, we anticipate this EESSI tutorial to be well attended (20-50 attendees).
-
-
-\comment{online EESSI tutorial in Dec'23 had over 130 registrations}
+Based on attendance at previous EESSI and EasyBuild events, including the yearly EasyBuild User Meetings (over 30
+attendees in the last physical edition in 2023, close to 100 in 2021 and 2022 in an online setting) and previous
+related tutorials (PRACE-VI-SEEM 2017 Spring School with 25-30 attendees, a free online EasyBuild tutorial in June'20
+with about 100 attendees, the half-day ISC'21 tutorial with over 25 attendees, and the in-person (half-day) ISC'22
+EasyBuild tutorial with about 20 attendees, and an online EESSI tutorial in Dec'23 had over 130 registrations), we
+anticipate this EESSI tutorial to be well attended with 20-50 attendees.
 
 %KH I would've gone with 50/25/25, but this works too (maybe better even)
 % MG: This was just a blind guess ;)

isc24/EESSI/audience.tex

@@ -1,8 +1,12 @@
 This tutorial is intended for
 \begin{itemize}
-    \item system managers and administrators, responsible for the operational aspects of HPC systems and concerned about hardware optimised scientific software installations;
-    \item user support teams who need to provide a consistent central software stack for end users, and want to do so in a reproducible way;
-    \item end users who want to empower themselves to use a software stack they require without compromising on performance, on top of what is provided centrally by the HPC support team;
+    \item end users who want to empower themselves to use a software stack they require without compromising on
+          performance, on top of what is provided centrally by the HPC support team;
+    \item system managers and administrators, responsible for the operational aspects of HPC systems and concerned about
+          hardware optimised scientific software installations;
+    \item user support teams who need to provide a consistent central software stack for end users, and want to do so in
+          a reproducible way;
     \item cloud and CI users, that want to use a common stack of optimised scientific software installations;
-    \item system manufacturers and integrators interested in state-of-the-art software installation tools, who want to leverage the collective expertise incorporated in EasyBuild.
+    \item system manufacturers and integrators interested in state-of-the-art software installation tools, who want to
+          leverage the collective expertise incorporated in EasyBuild.
 \end{itemize}