Jupyter notebooks are an open-source analysis environment where you can gain insight into study data in real time with interactive visualizing and analysis. In a notebook, you can import data - including processed genomics, phenotype and transcriptomics data stored in the cloud - and analyze with custom or pre-built libraries using R or Python.
Notebooks combine analysis methods and findings in a single place, in a form that anyone can easily distribute. This is a logical evolution of the traditional scientific paper, and dramatically shortens the path between reading how an analysis was done and actually being able to reproduce it. It's difficult to overstate how powerful this concept is and what a dramatic impact it can have on the reusability and reproducibility of findings in the computational sciences.
Terra's integrated, open-source Jupyter Notebooks environment is accessible to newcomers and enables portability and reproducibility. Read on to learn more about Jupyter notebooks and how to use them in Terra.
Click here for 10 Jupyter notebooks tricks!
- Jupyter notebooks 101
- How to run a notebook on Terra
- Four ways to copy/create a notebook in a workspace
- Code and documentation cells in a Notebook
4.1. How to run code cells in a Notebook
4.2. How to edit content in a Markdown Cell
- Next steps
1. Jupyter notebooks 101
Jupyter notebooks are an open-source app that runs in a browser. They contain rich text commentary as well as code cells. They can execute any Python or R-based commands - including GATK - on real data in real-time.
When you send a copy of a notebook with code cells that have been run to collaborators, they can view your results embedded right in the .jpynb file.
Find a notebook in a public workspace you'd like to play around with? Clone yourself a copy. Need to develop/refine an analysis in tandem with distant collaborators? You can invite them to your workspace, and work directly in the same notebook with them.
New to Jupyter notebooks?
Check out the optional
Intro to Jupyter notebook in the Terra-Notebooks-QuickStart workspace, which explains:
- Why notebooks are used in biomedical research
- The relationship between the notebook and the workspace
- Jupyter Notebook basics: How to use a notebook, install packages, and import modules
- What are common libraries in data analysis and popular tutorial notebooks
Already familiar with Jupyter notebooks ?
The exercise notebooks in the QuickStart offer hands-on practice using notebooks for interactive analysis in Terra. You'll learn how to:
- Browse 1,000 genomes data in the Data Library and define a subset of data (cohort) for analysis
- Import the cohort from the Terra Data Library to the workspace
- Set up a virtual cloud environment to run the notebook
- Analyze the cohort of data interactively
Notebooks resources in Terra
The Terra Notebooks Playground workspace contains Jupyter Notebooks that allow you to explore notebook functionality. These include both R and Python Setup notebooks, and template notebooks for accessing and analyzing data.
The BioData catalyst Collection includes notebooks that are helpful for BioData Catalyst users in Terra. The notebooks in this collection can be copied to a different workspace to aid users in their individual research needs.
2. How to run a notebook on Terra
2.1. Open the notebook in the "Notebooks" tab by clicking on the card.
2.2. Choose "Edit" or "Playground" mode
To avoid overwriting another collaborator working in the same notebook, Terra will only allow you to edit a shared notebook in "Playground" mode.
2.3. Set up your virtual cloud environment
If you have not run an interactive analysis before, you will need to configure the cloud environment that Terra will create for you to run your notebook. You can customize the installed packages and libraries and compute resources of your virtual machine. To learn more about Understanding and Adjusting your Cloud Environment, see this article
3. Four ways to make (clone) your own notebook from a template
3.1. Clone the workspace with a notebook you'd like to explore
Cloning a workspace will automatically create copies of all of the notebooks in that workspace, allowing you to quickly duplicate the notebook analysis in your own secure sand box:
3.2. Clone an individual notebook to your own workspace
This is especially useful when you only want to use a few notebooks in public workspaces that include a large number of sample notebooks:
3.3. Create a new notebook from scratch
If you are an experienced notebook user, you may want to create a notebook from scratch:
3.4. Upload a template notebook from outside the Terra platform
This is similar to creating a new notebook. You need only make sure to upload a JSON file format saved with the
4. Code and markdown cells in a notebook
Cells are the building blocks of a notebook. Each cell has a "type" (Code/Markdown/Raw NBConvert) that determines how the application compute will interpret the instructions in the cell.
The cell type can be seen or changed either in the Cell>Cell Type drop down menu, or on the right of the toolbar of function shortcuts located just below the menu bar:
How to run a code cell
- - Select the cell and press
Enteron your keyboard (your keyboard may say "return" instead of "enter")
- Click the "Run" icon in the menu bar
- Use the appropriate command from the Cell dropdown menu:
How does a code cell run?
When you run a code cell, the application compute kernel interprets the code, passes those instructions to the actual operating system of the machine that the notebook is running on(e.g. Python, R), and retrieves results to display them in the notebook. As the command runs, the output log of the command appears right below the code cell (see the screenshot below):
If the code in the cell doesn't match the kernel's language, the application compute will return an error. If the code is correct but specifies no outputs, the code will run and the result of the computation will be stored in the notebook cloud environment until the kernel is restarted. If no output is specified, you will know the code was successfully executed by noting the number in the square parens [ ] to the left of the cell.
How to know if your code cell has executed
When you launch a notebook for the first time, the square parens to the left of each code cell are empty , indicating these cells have not yet been run during this session. An asterisk inside the parens [*] means the cell is running. Once the command has been executed, the asterisk will be replaced by an integer representing the number of commands executed since the kernel started. There is nothing to stop you from executing the same cell multiple times, as in the screenshot above.
If you clear the outputs by going to the dropdown menu Cell>All Outputs and selecting "Clear", the integer parens will all be replaced by empty parens again. However, the integer count will only reset to zero if you restart the kernel.
How to edit content in a markdown cell
To edit the content of a markdown cell, double click on the cell to edit. See the clip below for example expected behavior. Markdown is a lightweight plain text formatting language. The syntax controls how the text appears - bold/italic, header size, section enumeration, etc.
Markdown cells do not interpret code.
The VM can only interpret Markdown-based syntax in a markdown type cell. Running a Markdown-type cell that contains Python code, for example, will result in the code being reproduced as plain text.
Two examples of Markdown syntax
- Italicizing using a single asterisk on either side (*italics* => italics)
- Modifying text size using hashtags
A more comprehensive listing of Markdown syntax can be found in this helpful Markdown Cheatsheet
To learn more about notebooks, and how to customise your notebook cloud environment in Terra, see this article.