Re-number episodes about hpc-intro HOT 8 CLOSED

I think the error is the inflexibility of 'make check' here rather than the numbering scheme we have chosen.

@tkphd It is not a case of losing focus on a topic; there may be extra information that needs to be inserted for a particular run of the lesson (specific to the system or the community) and this gives the flexibility to re-use the material with your own custom bits added if you want. I think we need this flexibility here.

from hpc-intro.

can you elaborate on this in light of the repo split into hpc-shell and hpc-intro?

from hpc-intro.

Doing so would cause make lesson-check to consistently throw errors, e.g.

Missing or non-consecutive episode numbers [0, 11, 12, 13, 14, 15, 16]

IMO, firming up the lesson plan and re-numbering consecutively from one, with placeholders for content under development, would be more helpful.

from hpc-intro.

but in our case, that is quite needed. We want the HPC carpentry lessons be ready to mix and match. In other words, the episodes here would go with numbers in [10,20]. the lessons in hpc-shell go with numbers in [0,10). We should play with lesson-check to make it pass and yet keep the freedom that people can easily copy over the episodes from one repo to another. Any suggestions anyone?

from hpc-intro.

It seems to me that "mix & match" is handled in the other Carpentries curricula by having coupled sessions, rather than shuffled ones: we start with UNIX Shell in the morning, then cover Version Control in the afternoon, for example, rather than injecting Bash lessons into the Git material. This helps to focus attention on just one complex concept.

Dividing the workshop into 1) a subset of hpc-shell followed by 2) a subset of hpc-intro makes sense, but as delineated mini-workshops rather than an integrated jumble.

from hpc-intro.

I guess I'm okay with letting that error happen and/or turning that check off, but the way things are now, I'd also be okay if the lessons start from 01 and are consistently numbered.

from hpc-intro.

I am reopening this issue to hear what others think: @jstaf @ocaisa @aturner-epcc et al ? Can you please comment.

from hpc-intro.

Closed, superseded by #230.

from hpc-intro.