This sounds fantastic. In what context would the students be creating the notebooks -- as part of one of your existing ME courses, as a for-credit project, as a supervised but non-credit project?
What were your thoughts on submission workflow? You review initially, then the student directly submits a PR? Suppose several students want to create a notebook on the same topic. Would you steer them to another topic, allow them to work independently and both submit (and we merge best of both), urge them to collaborate? Were you planning to keep the mechanical engineering context for these problems, or present abstractly? (I myself would like to see the application left intact. It doesn't obscure the steps, and I love the brothers-and-sisters-under-the-skin glimpse of how other domains make use of the same tools I do.) > easier to organize and...write I agree. Pedagogical soundness is also a plus. Procida says "what you ask the beginner to do [in a tutorial] must work" (https://documentation.divio.com/tutorials/). That means, among other things, that we need to specify a single environment to run the tutorial in. Notebook is the all-around win for this. _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
