Technical issues with ipython notebook while teaching (restart kernel)

[chendaniely]

@gvwilson has asked me to document technical issues with the ipython notebook while teaching.

Since there isn't enough time to thoroughly find the root cause of problems while teaching sometimes a 'quick fix' is to restart the ipython notebook. If restarting the kernel becomes a systematic means to fix a notebook issue, it should be addressed as novices would most likely not know why their code does not work.

I've had 2 experiences where restarting the kernel solved some problem with the ipython notebook.

During the Rockefeller session

• from my blog post: Because of the guest wireless system, students were being knocked offline during an ipython notebook session, and this affected the actual notebook being able to run the code blocks. Running a kernel interrupt, kernel restart, and run all cells brought students back to a working state.
• this might not be the actual cause of the problem (since the notebook should be run on a local server and the internet connection should not affect the state of the notebook), but this is an example of when restarting the kernel solved some issue with the notebook

During the St. Louis session

• During one of the for loop challenges. 2 students had identical code blocks of code where restarting fixed the issue. I will try to remember and post the exact situation, but I do remember the outputs were not the same and all the variables were cleared at the beginning of the cell block so nothing was being carried over from previous cell blocks.

[rgaiacs]

From UFRGS session (maybe @acviana remember others issues):

• Request long loops. You can't kill one cell and because of it you will need to kill IPython kernel.
• Install package with IPython kernel running will not make it available after installation. You must restart IPython kernel.

[gvwilson]

Please add to teaching notes in the bc repository, and file tickets against IPython. Thanks!