Working on Wynton - April 2024

[AlexanderPico]

Issues, feedback and ideas from 4/15/24:

• typo: plog vs plog1
• BeeGFS module was confusing and users disengaged. Takeaway messages didn't stick (too early). Suggestion: save this for "advanced tips and tricks" at end of Day 2
• Demo a small job early on (without them following along) to help illustrate nodes, scratch and storage, before those modules.
• Add cd line to Install samtools code chunk
• Add step 4 for adding samtools to path and testing installation
• Add a slide illustrating multiple log nodes connecting to muliple dev nodes, connecting to one file system to help make the point that it doesn't matter which log or dev node you ssh to, you are working with the same files and folders.
• Run same example container on dev and on compute node.
• Revise definition for container (see below)
• One downside of two-day split is the drop off (~65% retention). If keep two-day, then you really have to "sell" the second day and don't describe it as optional or "if".
• Maybe move all container modules to Day 2 in the context of "more advanced" and move a generic compute example to Day 1
• Typo: S for $ in script

[AlexanderPico]

Suggestion for container definition slide:

Containers: An isolated environment for running software that avoids conflicts with the host system and promotes reuse and reproducibility. Containers are stored, shared and executed as image files with a .sif extension. Images are built from definition files (or Dockerfiles) which are a set of instruction you specify for your project.

Include a link for more details: https://apptainer.org/docs/user/main/introduction.html#why-use-apptainer

An illustration from def file -> image -> container might be helpful, indicating that users compose def files, work with image files and containers are virtually built upon execution of image files.