Notebook Instance Management

With Wherobots Cloud, you can start a pre-configured JupyterLab instance with just a few clicks, creating a spatial computing environment to develop your spatial analytics and AI workflows.

With Wherobots Notebooks, you can focus on extracting value from your geospatial data without the complexities of managing infrastructure or configuring software.

Benefits

• No installation necessary: Start analyzing your data immediately with pre-configured runtime environments.
• Scalable Processing: Leverage distributed computing to analyze massive geospatial datasets with ease.
• Enhanced Collaboration: Share notebooks and collaborate with your team in a centralized environment.
• Pre-built Tools: Access a rich set of tools and libraries for geospatial analysis, visualization, and machine learning.
• Cost-Effectiveness: Reduce infrastructure costs with serverless computing and efficient resource utilization.
• Ease of access to data: 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 Wherobots Notebook:

• An account within a Community, Professional, or Enterprise Edition Organization. For more information, see Create an Account.

Open a Wherobots Notebook

To start a Wherobots Notebook, do the following:

1. Login to Wherobots Cloud.

2. (Optional) Choose a runtime.

   The runtime size determines the resources allocated to the notebook instance.

   Note

   Some runtimes are reserved for our Professional or Enterprise Edition Organizations. By default, Community Edition Organizations can only use the Tiny runtime. If you are interested in additional runtimes, see Upgrade Organization or Compute Requests.

3. Click Start to initiate the runtime.

4. Click Open to open the Notebook.

   Reference

   Before using your notebook instance, 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 an Amazon S3 bucket, do the following:

1. Start a Wherobots Notebook.
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 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 Wherobots Notebook.
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 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.

Environment Presets

Environment Presets allow you to customize infrequently changed configurations for your notebook instance. These currently include:

• Wherobots version
• Whether Wherobots AI is on or off by default
• Spark configuration
• Dependencies

To create a custom preset, do the following:

1. Click Default.
2. Click + next to Environment Preset.

3. Fill in the required information.

   

4. Click Save.

Change Wherobots Version

You can customize the Wherobots version for your notebook instance. The default Wherobots version is the latest version.

Change Spark Configuration

Add any custom spark configurations you want before starting the notebook instance.

Adding Dependencies

We support both file and PYPI as sources for dependencies inside Wherobots Notebooks. Below you will find the directions for adding dependencies from each source.

Adding Dependencies from a File

Wherobots Cloud allows you to add dependencies from the Wherobots File system.

Note

Only Python Wheel (.whl), .jar, and .zip files are supported.

Reference

Please refer to storage layer management page to upload the files in the correct directory.

Click "Browse" and select the file from the Wherobots File Browser. The selected file must have a valid file extension (.whl, .jar, or .zip).

PYPI Source

You can add dependencies from the PYPI source by providing the library name and version.

When the notebook instance starts, it will fetch and install listed packages from PYPI.

Environment Override Presets

Note

Configurations present in Environment Override Presets are subject to change. Configurations may be added or removed as the product evolves.

Environment Overrides allow you to customize the most commonly updated values for your notebook instance. These currently include:

• Driver disk size
• Executor disk size
• Spark configuration

To access the Environment Overrides, do the following:

1. Go to Start a Notebook

2. Click Default.

   

3. Click Show Environment Overrides.

4. Click a previously created override from the dropdown.

To create custom Environment Overrides, do the following:

1. Click Default.

2. Click Show Environment Overrides.

   

3. Click +.

4. Enter the necessary information.
5. Click Save.

Change Disk Size

You can customize the default disk size for your notebook instance. The default disk size for driver and executor nodes is based on the runtime size and is listed below:

Runtime Size	Disk Size
Tiny	20 GB
All others	200 GB

Spark Configuration

Refer to the Spark configuration section in the Environment Presets for more information.

Destroying Notebook Instance

Once you have finished using the notebook instance, you can click Destroy.

This will shut down the Notebook instance and release the resources it was using. It is recommended that you destroy notebook instances when they are no longer needed.

Note

Community Edition Organizations can expect Notebook instances to automatically shut down after 4 hours. Community Edition Organizations can restart the Notebook instance if additional time is required beyond the 4 limit.

Troubleshooting

Notebook stuck in STARTING status

The notebook instance will usually start within 5 minutes of clicking Start. If you observe the notebook stuck in STARTING status, you can try to destroy and re-create the notebook instance. If the problem persists, please contact support@wherobots.com.