Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Goals:

  • Provide the other side of jupyter so users know what to look out for.



Some people hate Jupyter!

shouting-development.gif


But why?

  • If you only learn to program in Jupyter notebooks, it’s possible that you’ll develop bad coding practices.

  • It’s somewhat counterintuitive to object oriented programming and can discourage OOP practices.

    • As part of that, it can discourage

  • Most jupyter notebooks and their output are not easily reproducible. Even if you don’t have cells that use randomization, if the original creator only ran some cell a few times and then just kept the state without running it in subsequent runs, the next person who runs it won’t be able to reproduce it running it from scratch.

    • You may run a notebook always skipping a cell, while the next person to run it doesn’t skip that cell. You’ll end up with different output.

    • Cells executed in different orders give you different output. You can override the linear run of cells in jupyter.


There are great things about Jupyter

  1. Encourages well documented/commented code

  2. Great visualization


It’s not really meant for use on an HPC

HPC computations and Jupyter notebooks don’t really go together naturally.


Next Steps

Use the following link to provide feedback on this training: https://forms.gle/qBBwXpKeTNqSR5516 or use the QR code below.

  • No labels