Defining the "common workflow" for our lesson

[ocaisa]

Defining the "common workflow" for our lesson

[ocaisa]

The "common workflow" identified in 01-introduction.md is

1. Read a data file.
2. Perform an analysis on this data file.
3. Write the analysis results to a new file.
4. Plot a graph of the analysis results.
5. Save the graph as an image, so we can put it in a paper.
6. Make a summary table of the analyses, which requires aggregation of all previous results.

Can we cover the same points? I think the last point is the hardest (and unnecessary for us). Order could be changed though to

1. Create data files (Run slurm job using job template we provide, store output in well-defined filename)
2. Perform an analysis on the data files. (extract our timings convert into speedup)
3. Write the analysis results to a new file.
4. Plot a graph of the analysis results (could consider doing this locally or remotely).
5. Save the graph as an image.
6. Pull the results (in this case an image) from the cluster and review it.

[reid-a]

This could build off what was done in the HPC Intro lesson -- call back to that lesson, show a job script, and look at the output of the job script. This could live in first episode. Induces HPC Intro as a pretty hard pre-requisite for this lesson.

[bkmgit]

The current format with the job submission script at the end seems ok. However, one may wish to enable attendees to practice using SLURM, in which case one could introduce the job submission script at the beginning. The lesson seems independent of HPC intro, but does allow practice using a scheduler.