realign goals, questions, and content

[tkphd]

Some initial work on streamlining & refactoring hpc-intro.

Closes #388.
Addresses #387.

[bkmgit]

Link to HPC Jargon slides is nice. Some of the wording can be improved. For example:

• https://github.com/tkphd/hpc-intro/blob/lesson-objectives-review/files/jargon.html#L65 should become 'familiar.' as it the level of familiarity can differ quite substantially
• https://github.com/tkphd/hpc-intro/blob/lesson-objectives-review/files/jargon.html#L82 should become 'Computation at larger ...'
• https://github.com/tkphd/hpc-intro/blob/lesson-objectives-review/files/jargon.html#L106 'Oss' -> 'operating systems' minimize use of abbreviations which have not been explained
• https://github.com/tkphd/hpc-intro/blob/lesson-objectives-review/files/jargon.html#L123 is unclear, one can setup a homogeneous cluster in the cloud, and even if infiniband is not available, there are improved network connectivity options. VM is jargon that should be replaced by virtualization and a brief description of that this is and possibly how it might impact performance. Apart from virtualization probably the largest other practical difference is that typically you need to have greater familiarity with software setup in the cloud than you do on an HPC system for science applications. Cloud originally evolved from providing web services, but is now also used for big data workloads.
• https://github.com/tkphd/hpc-intro/blob/lesson-objectives-review/files/jargon.html#L147 should be updated to describe an HPC cluster
  Note that usually for jargon busting exercises, participants each list some terms they have come across on HPC/Supercomputing and then look up more information online and discuss it in small groups.

[bkmgit]

Thanks for this update. Have not reviewed section 16 since it will be replaced.

[tkphd]

Link to HPC Jargon slides is nice. Some of the wording can be improved. For example:

• https://github.com/tkphd/hpc-intro/blob/lesson-objectives-review/files/jargon.html#L65 should become 'familiar.' as it the level of familiarity can differ quite substantially
• https://github.com/tkphd/hpc-intro/blob/lesson-objectives-review/files/jargon.html#L82 should become 'Computation at larger ...'
• https://github.com/tkphd/hpc-intro/blob/lesson-objectives-review/files/jargon.html#L106 'Oss' -> 'operating systems' minimize use of abbreviations which have not been explained
• https://github.com/tkphd/hpc-intro/blob/lesson-objectives-review/files/jargon.html#L123 is unclear, one can setup a homogeneous cluster in the cloud, and even if infiniband is not available, there are improved network connectivity options. VM is jargon that should be replaced by virtualization and a brief description of that this is and possibly how it might impact performance. Apart from virtualization probably the largest other practical difference is that typically you need to have greater familiarity with software setup in the cloud than you do on an HPC system for science applications. Cloud originally evolved from providing web services, but is now also used for big data workloads.
• https://github.com/tkphd/hpc-intro/blob/lesson-objectives-review/files/jargon.html#L147 should be updated to describe an HPC cluster
  Note that usually for jargon busting exercises, participants each list some terms they have come across on HPC/Supercomputing and then look up more information online and discuss it in small groups.

The jargon presentation is not exactly in-scope for this PR, but I've addressed most of these comments in 4089f66. Note that text between ??? and --- represents author notes, which will not be rendered by default.

[tobyhodges]

I mostly limited my review to your learning objectives.

I have made a few suggestions where I think the objectives should be reworded or - in one case - split up. A couple points to set out on my reasoning:

1. Objectives should be written as endings to a sentence that begins "By the end of this episode, learners should be able to ..."
2. The verbs at the beginning of an objective should be active: it is important they are directly measurable/observable because then you can design a formative assessment to evaluate learner attainment during a workshop. Verbs like "understand" and "appreciate" are not directly measurable and should be replaced. (I will submit a separate PR to take care of this in 18-responsibility.)

[ocaisa]

I'll do my review in a few chunks

[ocaisa]

Suggested change

	results are transmitted via text, only. Anything other than text (images, for
	results are transmitted via text only. Anything other than text (images, for

[ocaisa]

local machine is a bit jargon-y I would say, if we are going to use it we should explain early on what is meant by local and remote. Perhaps we can use the picture earlier and introduce local and remote there?

[ocaisa]

I worked on something a bit (in a slide deck), we could introduce it piece by piece

[tkphd]

"Local" machine/device/computer is used a number of times in the first episode. Perhaps create an issue to place this image in there?

[ocaisa]

Lots of effort gone in here, thanks @tkphd!