[Change Request] addressing episode 3 dry-run comments

[hcadavid]

• the "which concept applies here" slide actually mentions "study" at the top of the slide: ask the question without mentioning the word
  "Getting familiar with UI slide" – give a tinyurl with the website
• Align the v6 setup with the presentation slides (number of nodes, names of studies, etc). try to align example on slide to what people actually see when they run their example on their own system (reduces confusion with students): align number of studies. (Number of nodes depicted on the diagrams was updated to match the exercise. Names used on the slides can't be made consistent with the ones on the exercise as each participant will be part of a collaboration with different organization names)
• I like that people had an exercise to translate the federated avg component to v6, but ppl still seem to be a little puzzled by the partial vs. central avg, I think a diagram would help: check episode 2
• The format of headers of the example data are not consistent with that in the csv file. The headers should use camelCase format.
• Handling problems through the UI exercise: don't select boolean column either because it won't fail (now the exercise explicitly asks to include a text column).
• The gui part is aimed to people that don't know how to code, so I don't know if ppl should be asked to look at the source code I guess peole that don't know python will be scared. this depends on who the target audience of the workshop is (not necessarily target audience of GUI). If participants are coders, then the GUI is still a nice way to quickly demonstrate v6, even though they are not necessarily scared off by the code: add pseudo-code (check with episode 2)
• We should instruct participants to give their own name in the task name so they can find it back
• I think it would be good if you would demo the UI live on the screen (carpentries style is that you do all this stuff live instead of giving presentation) / Maybe good to already have users log in to the UI while explaining the menus. Some people prefer to explore by clicking as well. <- I'll do it that way, but will keep the slides in case they are needed.
• vantage6 server is hanging
• I like that we are going through what happens when a node is offline
• I thought the UI was clicking a little bit but you manage to map the stuff to the underlying concepts so that is nice
• we are really going into troubleshooting which is nice
• Hector was exactly on schedule. Second part after lunch was 30 mins