The Jupyter Notebook is a web application that enables you to create and share documents (called "notebooks") that can contain a mix of live code, equations, visualizations, and explanatory text.
This is an introduction to using these notebooks on Savio. Before getting started, make sure you have access to the Savio cluster, as you will need your BRC username and one-time password to log in.
As described next, you can start a Jupyter notebook via the Open OnDemand service, which allows you to operate completely via your web browser on your local computer (e.g., your laptop). Open OnDemand replaces our old (much more limited) JupyterHub service. You can also run Jupyter notebooks via the Savio visualization node as described below.
Using Jupyter notebooks via the interactive Open OnDemand service¶
Running a notebook via Open OnDemand¶
- Connect to https://ood.brc.berkeley.edu
- Just after logging in with your BRC username and one-time password (OTP), the initial OnDemand screen presents a welcome screen. Click the "Interactive Apps" pulldown.
- Choose the appropriate Jupyter Server option to either run as part of a Slurm batch job ("compute in batch queues") or (for non-intensive computations) on our standalone Open OnDemand server.
- Fill out the form presented to you and click on "Launch". For batch-based work, you'll need to provide the information that you would usually supply when submitting a Slurm job. Once the server is ready, you'll be able to click no the "Connect to Jupyter" button.
- After clicking on "Connect to Jupyter", the home directory will be displayed. From the "New" dropdown menu (next to 'Upload' near the top right of the screen) select one of the following options:
- Select "Python 3.6" under "Notebooks" for a Notebook with full access to Python 3.6.4 and the system-installed Python 3.6 packages (Python 3.6.4 and its packages are also available through the python/3.6 module when logging into Savio in the usual way).
- Select "Python 3" under "Notebooks" for a Notebook with full access to Python 3.5.4 and the system-installed Python 3.5 packages (Python 3.5.4 and its packages are also available through the python/3.5 module when logging into Savio in the usual way).
- Select "Python 2" under “Notebooks” for a Notebook with full access to Python 2.7.14 and the system-installed Python 2.7 packages (Python 2.7.14 and its packages are also available through the python/2.7 module when logging into Savio in the usual way).
- Select “Terminal” to open a UNIX terminal session instead, so that you can work at the command line, rather than in a Notebook. (You might select this option if you need to set up IPython Clusters or add kernels, as described further below.)
- To move between your Notebook and the control page that allows you to see your files and select any running Notebooks, clusters and terminals, simply click on the ‘jupyter’ banner in the upper left corner of your Notebook. (Or alternately, select “Control Panel” and then click “My Server”.)
- You can have your session continue to operate in the background by selecting the “Logout” button. Note that, when doing so, you will continue to be charged for FCA use or, if using a Condo node, you will prevent others in your group from accessing the relevant resource on which the job is running.
- To terminate a running Notebook, select the “My Interactive Sessions” tab and delete the session.
At this point you should already have a fully working Jupyter environment. To start working with Jupyter Notebooks, please see the Jupyter Documentation.
To use parallelization capabilities via your notebook, please see Running Parallel Python Code in Jupyter Notebooks on Savio.
Installing Python packages¶
A variety of standard Python packages (such as numpy, scipy, matplotlib and pandas) are available automatically. To see what packages are available, open a Terminal notebook (see item 5c above) or open a Terminal on Savio in the usual fashion. Then load the Python version of interest (here Python 3.7) and list the installed packages:
module load python/3.7
There should be no issues using pip to install or upgrade packages and then use them in a Jupyter notebook, but you will need to make sure to install the new versions or additional packages in your home or scratch directories because you do not have write permissions to the module directories. You can use
pip install --user $MODULENAME to install the module to
$HOME/.local. So, if you need to install additional packages, simply load the desired Python module in the usual way and then use pip to install in your home directory. For example for Python 3, you can install the rpy2 package (needed in the next section) with:
module load python/3.7
pip install --user rpy2
If you'd like to install packages with
conda install you'll need to create a Conda environment in which to install packages and then create a kernel associated with your Conda environment as discussed in the next section.
Adding new kernels¶
Jupyter supports notebooks in dozens of languages, including IPython, R, Julia, Torch, etc.
If you’d like to use a language not indicated in the drop-down menu discussed in step 6 above, you’ll need to create your own kernel. You may also need to create your own kernel for a language already supported if you want to customize your environment. For example, to set UNIX environment variables (such as
$PYTHONPATH if you have packages installed in non-standard locations) or source a script in advance of running your notebook, you can do this by creating your own kernel. Or if you'd like to work within a Conda environment when using your notebook, you'll also need to create a kernel.
Manually creating a new kernel¶
To add a new kernel to your Jupyter environment, you’ll need to create a subdirectory within
$HOME/.ipython/kernels. Within the subdirectory, you’ll need a configuration file, “kernel.json”. Each new kernel should have its own subdirectory containing a configuration file.
Here we’ll illustrate how to create your own IPython kernel, in this case a kernel that allows you to call out to R via the rpy2 python package. We'll name the subdirectory for this kernel as “python3-rpy2”. Here’s an example “kernel.json” file that you can use as a template for your own configuration files. This file would be placed in
$HOME/.ipython/kernels/python3-rpy2. (Note that for this to work you also need to install the rpy2 package for Python 3.6 within your account as discussed just above.
"display_name": "Special Python 3 with rpy2",
"PATH" : "/global/software/sl-7.x86_64/modules/langs/r/3.4.2/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/global/home/groups/allhands/bin",
Please review the IPython Kernel Specs for more details regarding the format and contents of this configuration file. In particular, please make sure
$PYTHONPATH, and all other environment variables that you use in the kernel are properly populated with the correct values.
Using a Conda environment¶
Another approach to adding a new (Python) kernel to your Jupyter environment is to create a conda environment and add it as a kernel to Jupyter. When in Jupyter, you will then be able to select the name from the kernel list, and it will be using the packages you installed. Follow these steps to do this (replacing
$ENV_NAME with the name you want to give your conda environment):
module load python/3.7
conda create --name=$ENV_NAME ipykernel
source activate $ENV_NAME
python -m ipykernel install --user --name $ENV_NAME
# Then from here you can do pip install or conda install
Here we’ll illustrate how to create your own Tensorflow kernel within a Python Jupyter environment, so that you can import and utilize the python tensorflow package from within a Jupyter notebook:
module load python/3.7
conda create --name=tf ipykernel
source activate tf
python -m ipykernel install --user --name tf --display-name="Tensorflow"
conda install tensorflow
Now you can choose the Tensorflow kernel you just created from the kernel list in your Jupyter environment, and you can verify that you can utilize and access the Python Tensorflow package from within a cell in a Jupyter notebook as follows:
If you want to create or use notebooks with interactive widgets, a table of contents, or collapsible code blocks, you need to enable Nbextensions. From the “New” dropdown menu (same as in step 4), select “Terminal”. Copy and paste the code below into the terminal prompt, and hit enter.
module load python/3.7
jupyter contrib nbextension install --user
After stopping and restarting your server as well as logging out and back in, when you return to the JupyterHub page, you should see a new tab for Nbextensions, where you can enable or disable individual extensions. Shut down and relaunch any running notebooks, and the extensions will be present.
Using Jupyter notebooks via the Savio visualization node¶
An alternative to Open OnDemand for using Jupyter notebooks on Savio is to interact with Jupyter via a browser running on the Savio visualization node. Note that all of the information above about installing Python packages and creating your own kernels also works in this context. In particular, once you create a new kernel, it will be available to you via a Jupyter session either running via Open OnDemand or via the visualization node.
Here are the steps to use a notebook through the visualization node.
1. Submit a SLURM job asking for the nodes in interactive mode, using the
srun --pty method documented here.
2. Once you get an interactive shell on the compute node, load the python/3.5 or python/3.6 module and run our script for starting a Jupyter notebook:
$ module load python/3.6
3. That will print out a URL. Copy that URL and leave the SLURM interactive job running.
4. Next follow our visualization node instructions to start a VNC session (i.e., a remote desktop session on our visualization node).
5. After you see the xterm (terminal) window inside the VNC Viewer, start the firefox browser in the xterm window of the VNC session:
6. Once the browser starts running, paste the URL from Step 3 and then you should be able to see the notebook.
7. When you are done, end the VNC session and cancel your SLURM job (e.g., by simply exiting the terminal where your interactive srun session is running).
Using the Jupyter Lab interface¶
Once you've started the Jupyter interface and see the main Jupyter page, which should show a list of files in your working directory, modify the URL in your browser so it ends in "/lab" rather than "/tree?". That will change to the Jupyter Lab interface.
Note that to exit your session you'll need to switch back to "/tree" and stop your server as described in the relevant previous section.