# Tips and Tricks for JupyterLab

## DX Notebooks Naming

All notebooks saved onto the platform will have a DX prefix in front of them. Here is an example: 

<figure><img src="/files/JQKR4rst9WCjEVn8T5IZ" alt=""><figcaption></figcaption></figure>

## Storage Locations in JupyterLab&#x20;

There is both worker related/ JupyterLab storage, as well as what is present in the Project storage. This is annotated in the figure below:&#x20;

<figure><img src="/files/SM2IZk0xNws7w8QaojTa" alt=""><figcaption></figcaption></figure>

## Code Blocks

1. When you are running code blocks, remember that in JupyterLab you can run them out of order. This means that you need to pay attention to the numbers on the side of the code blocks for the order. This is highlighted in gold below:

<figure><img src="/files/7tNMDjsZsTodnJeqg1WX" alt=""><figcaption></figcaption></figure>

2. If you choose to write in Python or R primarily, you can use the following at the top of your code block to "switch" to bash scripting. Example below

<figure><img src="/files/ismyOHGkPMGQFJJhiygF" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://academy.dnanexus.com/interactivecloudcomputing/jupyterlab/tips-and-tricks-for-jupyterlab.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.