Skip to main content
With Wherobots Cloud, you can start a Notebook Runtime, a pre-configured JupyterLab environment, with just a few clicks, creating a spatial computing environment to develop your spatial analytics and AI workflows. Notebook Runtimes were previously called Jupyter Runtimes and, before that, notebook instances. With Notebook Runtimes, you can focus on extracting value from your geospatial data without the complexities of managing infrastructure or configuring software.

​
Benefits

The following are some of the key benefits of using Notebook Runtimes:
Start analyzing your data immediately with pre-configured runtime environments.
Leverage distributed computing to analyze massive geospatial datasets with ease.
Share notebooks and collaborate with your team in a centralized environment.
Access a rich set of tools and libraries for geospatial analysis, visualization, and machine learning.
Reduce infrastructure costs with serverless computing and efficient resource utilization.
Supports S3 Storage Integration S3 Paths. Connect directly to your cloud storage and other Wherobots services for a streamlined workflow.

​
Before you start

The following is required to start a Notebook Runtime:

​
Start a Notebook Runtime

To start a Notebook Runtime, do the following:
  1. Log in to Wherobots Cloud and go to the Code page.
  2. Click Start a Notebook Runtime, or click + next to Notebook Runtimes. The New Notebook Runtime dialog opens.
  3. Choose a Size. The size determines the resources allocated to the Notebook Runtime.
    Available Runtimes vary by Organization Edition. If you are interested in additional runtimes, see Add a Payment Method or Compute Requests.
  4. (Optional) Click Environment to choose an Environment Preset or Environment Override.
  5. (Optional) Enter a Name for your Notebook Runtime.
  6. Select a Region. For the best performance, select a region closest to your data. For a full list of Wherobots’ supported cloud regions, see Cloud and Cloud Region Availability section.
  7. Click Advanced Options > Idle Timeout.
    1. Select an Idle Timeout. The default is 45 minutes. You can also choose a timeout of 15 or 120 minutes. While 45 minutes is the default, your last selection will be saved and used for your subsequent sessions, even after logging out. This setting is specific to you and does not change the global default for other members your Wherobots Organization.
    How does the Idle Timeout feature work? Idle Timeout lets you control how long your Notebook Runtime can be inactive before automatically being scaled down to save resources. When your Notebook Runtime exceeds the idle timeout threshold, the Jupyter kernel will terminate. To resume work, restart the kernel and re-execute all cells from the beginning. The Idle Timeout feature only works with Notebook Runtimes, not Job Runs.
    Managing Costs: Releasing Resources vs. Idle Timeout While Idle Timeout can help reduce costs by minimizing resource usage, you’ll still be charged for the minimum resources used while idle. For more information, see Managing Costs.
    To fully release resources and stop incurring related charges, destroy your active Notebook Runtimes.
  8. Click Start. Wherobots Cloud opens the Notebook Runtime in a new browser tab, which shows its progress and opens JupyterLab when the Notebook Runtime is ready. The Notebook Runtime also appears in the Notebook Runtimes list on the Code page. Its status dot is yellow while it starts and turns green 🟢 when it is running. Billing begins when the runtime is provisioned, which is when the dot turns green.
To return to a Notebook Runtime later, click Open next to it in the Notebook Runtimes list.
Before using your Notebook Runtime, familiarize yourself with Jupyter notebooks by reviewing the Jupyter notebook management documentation. This guide provides an overview of managing notebooks, including running code cells.

​
Share a Wherobots Notebook

To share a Wherobots Notebook with your Organization, you can save that Notebook within Wherobots Managed Storage or within an Amazon S3 bucket that has been integrated with Wherobots.

​
Managed Storage

To share your Wherobots Notebook within Wherobots Managed Storage, do the following:
  1. Start a Notebook Runtime.
  2. In JupyterLab:
    1. Add your code and analysis to the notebook.
    2. Click File > Save Notebook.
    3. Click File > Download.
  3. In Wherobots Cloud:
    1. Go to Cloud Storage > data > shared.
    2. Click Upload.
    3. Click + Click to upload a file and upload the Wherobots Notebook that you previously downloaded.

​
S3 Integration

To share your Wherobots Notebook within an Amazon S3 bucket, do the following:
  1. Start a Notebook Runtime.
  2. In JupyterLab:
    1. Add your code and analysis to the Notebook.
    2. Click File > Save Notebook.
    3. Click File > Download.
  3. In Wherobots Cloud:
    1. Go to Cloud Storage.
    2. Click Storage Source dropdown menu.
    3. Select an S3 bucket.
    4. Navigate to your desired folder within the bucket.
    5. Click Upload.
    6. Click + Click to upload a file and upload the Wherobots Notebook that you previously downloaded.
For more details on creating storage integrations, refer to S3 Storage Integration.

​
Destroy a Notebook Runtime

Once you have finished using a Notebook Runtime, go to the Code page and click Destroy (the trash icon) next to it in the Notebook Runtimes list. There is no confirmation step. This shuts down the Notebook Runtime and releases the resources it was using. It is recommended that you destroy Notebook Runtimes when they are no longer needed.
Notebook Runtimes automatically shut down when they reach your Organization’s Runtime TTL. If you need more time, start a new Notebook Runtime.

​
Troubleshooting

​
Notebook Runtime stuck starting

A Notebook Runtime will usually start within 5 minutes of clicking Start. If its status dot stays yellow for longer than that, you can try to destroy the Notebook Runtime and start a new one. If the problem persists, please Contact Support.