Docs/tutorial solutions/exercises

[jlnav]

experimenting with adding drop-down boxes for tutorial exercises/solutions

[jlnav]

Decided to leave exercises for only the first two tutorials for now, since the last two tutorials don't especially involve writing functions, only demonstrating capabilities

edit: modifying parameters or settings is covered in earlier tutorials, but doing that (or just saying to read the example regression tests) is all I can imagine for the last two tutorials.

[shuds13]

I'm okay with python/pip without the 3. But we should be consistent. Later python3 is used in a couple of places (when running the calling script). We should decide generally for the docs whether we want to drop the 3.

[shuds13]

Perhaps have this above the enumerated part?

[jlnav]

As in, list everything, then say: "Write a Calling Script with the above specifications?"

[shuds13]

I misinterpreted this line as saying instead do the following lines. Perhaps say something like use the functions from the answers to the exercises.

[shuds13]

What do people think about introducing parse_args here somewhere?

[shuds13]

Checking here - I think somewhere the tutorials should have a link/location where to find example in the repo. Maybe at bottom of first section. "This example can be found in the repository at...."

[jlnav]

Links to example python files and a parse_args item for exercises added. Once this is pulled in I'll work on updating the jupyter notebooks

(branched off and starting work, actually)

[shuds13]

Open to views but we may want to standardise the H argument coming in and the out as H_in and H_out maybe?

[shuds13]

Optional:
"Our simulator function is called by a worker for every value in its batch from the generator function." could maybe be
"Our simulator function is called by a worker for every work item produced by the generator function"

[shuds13]

I made a few comments. All optional.