MAAP-Project · grallewellyn · Oct 6, 2025 · Oct 6, 2025 · Oct 7, 2025 · Oct 13, 2025
diff --git a/docs/source/_static/ogc/build_app_pack/algo_catalog_card.png b/docs/source/_static/ogc/build_app_pack/algo_catalog_card.png
diff --git a/docs/source/_static/ogc/build_app_pack/algo_reg_form.png b/docs/source/_static/ogc/build_app_pack/algo_reg_form.png
diff --git a/docs/source/_static/ogc/build_app_pack/build_deploy_ui.png b/docs/source/_static/ogc/build_app_pack/build_deploy_ui.png
diff --git a/docs/source/_static/ogc/build_app_pack/register_algo_btn.png b/docs/source/_static/ogc/build_app_pack/register_algo_btn.png
diff --git a/docs/source/_static/ogc/build_app_pack/scihub_env.png b/docs/source/_static/ogc/build_app_pack/scihub_env.png
diff --git a/docs/source/_static/ogc/build_app_pack/submit_reg_btn.png b/docs/source/_static/ogc/build_app_pack/submit_reg_btn.png
diff --git a/docs/source/_static/ogc/build_app_pack/toasts.png b/docs/source/_static/ogc/build_app_pack/toasts.png
diff --git a/docs/source/conf.py b/docs/source/conf.py
@@ -16,6 +16,21 @@
 
 def setup(app):
     app.add_css_file('custom.css')
+    # Add Leaflet CSS and JS for R htmlwidgets
+    app.add_css_file('https://unpkg.com/leaflet@1.9.4/dist/leaflet.css',
+                     integrity='sha256-p4NxAoJBhIIN+hmNHrzRCf9tD/miZyoHS5obTRR9BMY=',
+                     crossorigin='anonymous')
+    app.add_js_file('https://unpkg.com/leaflet@1.9.4/dist/leaflet.js',
+                    integrity='sha256-20nQCchB9co0qIjJZRGuk2/Z9VM+kNiyxNV1lvTlZBo=',
+                    crossorigin='anonymous')
+    # Add Proj4js and Leaflet.Proj for coordinate transformations
+    app.add_js_file('https://cdnjs.cloudflare.com/ajax/libs/proj4js/2.9.0/proj4.js',
+                    crossorigin='anonymous')
+    app.add_js_file('https://cdn.jsdelivr.net/npm/proj4leaflet@1.0.2/src/proj4leaflet.js',
+                    crossorigin='anonymous')
+    # Add Leaflet providers for base maps
+    app.add_js_file('https://unpkg.com/leaflet-providers@1.13.0/leaflet-providers.js',
+                    crossorigin='anonymous')
 
 
 # -- Project information -----------------------------------------------------
@@ -38,6 +53,12 @@ def setup(app):
 
 nbsphinx_execute = 'never'
 
+# Enable RequireJS for HTML widgets (needed for R leaflet maps)
+nbsphinx_requirejs_path = 'https://cdnjs.cloudflare.com/ajax/libs/require.js/2.3.6/require.min.js'
+nbsphinx_requirejs_options = {
+    'crossorigin': 'anonymous',
+}
+
 # Add any paths that contain templates here, relative to this directory.
 templates_path = ['_templates']
 
@@ -80,3 +101,33 @@ def setup(app):
 	if "html_context" not in globals():
         	html_context = {}
 	html_context["READTHEDOCS"] = True
+
+# -- Options for LaTeX output ------------------------------------------------
+
+latex_engine = 'pdflatex'
+latex_elements = {
+    'papersize': 'letterpaper',
+    'pointsize': '10pt',
+    'preamble': r'''
+\usepackage{charter}
+\usepackage[defaultsans]{lato}
+\usepackage{inconsolata}
+''',
+}
+
+latex_documents = [
+    (master_doc, 'maap-project.tex', 'MAAP Documentation',
+     'NASA MAAP Team', 'manual'),
+]
+
+# Exclude notebooks from LaTeX/PDF to prevent timeout
+# Notebooks with large images/outputs cause LaTeX to timeout on Read the Docs
+# They will still be available in the HTML documentation
+latex_exclude_patterns = [
+    '**/*.ipynb',
+]
+
+# Only apply notebook exclusions for LaTeX builds
+import sys
+if 'latex' in sys.argv or 'latexpdf' in sys.argv:
+    exclude_patterns += latex_exclude_patterns
diff --git a/docs/source/getting_started/_static/launcher-register-algorithm.png b/docs/source/getting_started/_static/launcher-register-algorithm.png
diff --git a/docs/source/getting_started/_static/register-4-modal.png b/docs/source/getting_started/_static/register-4-modal.png
diff --git a/docs/source/getting_started/_static/register-5-status.png b/docs/source/getting_started/_static/register-5-status.png
diff --git a/docs/source/getting_started/_static/register-algorithm-form.png b/docs/source/getting_started/_static/register-algorithm-form.png
diff --git a/docs/source/getting_started/_static/run-1-launcher.png b/docs/source/getting_started/_static/run-1-launcher.png
diff --git a/docs/source/getting_started/_static/run-2-filledform.png b/docs/source/getting_started/_static/run-2-filledform.png
diff --git a/docs/source/getting_started/_static/run-4-viewjobs.png b/docs/source/getting_started/_static/run-4-viewjobs.png
diff --git a/docs/source/getting_started/_static/run-5-viewoutputs.png b/docs/source/getting_started/_static/run-5-viewoutputs.png
diff --git a/docs/source/getting_started/running_at_scale.ipynb b/docs/source/getting_started/running_at_scale.ipynb
@@ -25,63 +25,51 @@
     "## Register an Algorithm\n",
     "To register an Algorithm that can be run in the DPS, the code should be placed in a public Git repo (either Github or Gitlab).\n",
     "\n",
-    "1. Open the Register Algorithm tool in the MAAP Extensions section of the Launcher. To open the Launcher, choose File -> New Launcher, or press the blue \"+\" button above the Jupyter file browser.\n",
+    "1. Open the Register Algorithm tool in the MAAP Extensions section of the Launcher. To open the Launcher, choose File -> New Launcher, or press the blue \"+\" button above the Jupyter file browser. Then select the Algorithm Catalog under MAAP plugins\n",
     "![Register Algorithm tool in Launcher](_static/launcher-register-algorithm.png)\n",
     "\n",
-    "2. First you fill in the public code \"Repository Information\". \n",
-    "- The Repository URL is the .git URL. \n",
+    "2. Click the blue Register New Algorithm in the top right corner\n",
+    "\n",
+    "3. Now fill in the information for this form:\n",
+    "![Register Algorithm form](_static/register-algorithm-form.png)\n",
+    "You can also select an existing algorithm configuration to autofill this form \n",
+    "\n",
+    "First you fill in the algorithm name and version. Your algorithm can be identified by the algorithm name, version and who deployed it. \n",
+    "\n",
+    "- The Repository URL is the .git URL. For example, \n",
     "```\n",
     "https://github.com/MAAP-Project/dps-unit-test.git\n",
     "```\n",
-    "- Repository Branch is used as a version when this algorithm is registered.\n",
-    "```\n",
-    "main\n",
-    "```\n",
-    "- The Run and Build Commands must be the path of the scripts that will be used by the DPS to build and execute the algorithm. Typically these will be the repository_name/script_name.sh, as demonstrated in this screenshot:\n",
+    "- The Run and Build Commands must be the path of the scripts that will be used by the DPS to build and execute the algorithm. Typically these will be the repository_name/script_name.sh:\n",
     "```\n",
     "dps-unit-test/run-test.sh\n",
     "```\n",
-    "For this algorithm, there is no build script, so the Build Command may be left empty.\n",
-    "\n",
-    "![Register Algorithm repository information](_static/register-1-repo.png)\n",
+    "For this algorithm, there is no build script, so the Build Command may be left empty. In other examples, you can add a build command to add packages on top of an existing docker image \n",
     "\n",
-    "3. Once that is complete we enter some \"General Information\". \n",
-    "- The **Algorithm Name** will be the unique identifier for the algorithm in the MAAP system; for example, it is the label that you look for when running or monitoring a Job. It can be anything you would like. If you use the same name as an existing Algorithm, you will replace the existing Algorithm in the system with your new one.\n",
-    "- **Algorithm Description** is additional free-form text to describe what this algorithm does.\n",
-    "- **Disk Space** is the minimum amount of space (in GB) you expect—including all inputs, scratch, and outputs—it gives the DPS an approximation to help optimize the run. For this tutorial we can just put `1`.\n",
-    "- **Resource Allocation** tells the system what kind of cloud computer to use for a Job run with this Algorithm. Typically you will use `maap-dps-worker-` and the last number indicates the amount of RAM. In the example shown here, we choose the smallest amount of RAM because we have a very simple Algorithm, `maap-dps-worker-8gb`.  The options available to you are based on your MAAP organization membership. Guest accounts will only be able to use the `maap-dps-sandbox`.\n",
-    "- The **Container URL** is a URL of the Stack (workspace image environment) you are using as a base for the algorithm. This is a dropdown where the default is a standard minimal container called `maap_base` image such as `mas.maap-project.org/root/maap-workspaces/custom_images/maap_base:v4.2.0`. The other option is the Container of your current workspace (i.e. R, pangeo, etc.). These containers will have numerous conda packages installed which may or may not be useful for you. Just a note if you want the default conda packages for your current workspace container, if you successfully ran the Algorithm in a Terminal without adding additional packages, then you should be able to successfully use your current workspace container as the **Container URL** for your algorithm. \n",
+    "- The **Base Container URL** is a URL of the Stack (workspace image environment) you are using as a base for the algorithm. This is a dropdown where the default is a standard minimal container called `maap_base` image such as `mas.maap-project.org/root/maap-workspaces/custom_images/maap_base:v5.0.0`. The other option is the Container of your current workspace (i.e. R, pangeo, etc.). These containers will have numerous conda packages installed which may or may not be useful for you. Just a note if you want the default conda packages for your current workspace container, if you successfully ran the Algorithm in a Terminal without adding additional packages, then you should be able to successfully use your current workspace container as the **Container URL** for your algorithm. \n",
     "We recommend using `maap_base` as it makes algorithm registration faster, although using it means you need to manage your own conda packages. More information how to make a custom conda environment [here](../system_reference_guide/custom-environments.html#Custom-environments). See the Algorithm Registration documentation for [more information on Containers](../system_reference_guide/algorithm_registration.ipynb#Container-URLs).\n",
+    "You can also click \"Use pre-built algorithm container\" to bring your own already built image. \n",
     "\n",
-    "```\n",
-    "mas.maap-project.org/root/maap-workspaces/custom_images/maap_base:v4.2.0\n",
-    "```\n",
-    "\n",
-    "![Register Algorithm general information](_static/register-2-general.png)\n",
-    "\n",
-    "4. Fill in the Input section. There are File Inputs and Positional Inputs (i.e., command-line arguments). In our example we have on File Input called `input_file`. For each input you can add a Description, a Default Value, and mark whether it's required or optional. There are no positional inputs for this Algorithm.\n",
+    "4. Once that is complete enter some \"Resource Requirements\" and \"Metadata\"\n",
     "\n",
-    "![Register Algorithm file inputs](_static/register-3-inputs.png)\n",
+    "5. Fill in the Input section. For each input you can add a Name, Label, Description, Type, and Default Value. \n",
     "\n",
     ".. note:: **Understanding How the Algorithm Registration Form Relates to Job Execution in DPS**:\n",
     "When you run a Job in the DPS, the MAAP system will start up a \"worker\" computer in the cloud based on the Resource Allocation parameter. It will then run the build script to make sure that your runtime environment is set up properly, and then the run script indicated during the registration process to handle the input parameters and run the algorithm code. \n",
     "\n",
-    ".. note:: As part of execution, the DPS will create a directory called `/inputs`. Copies of the File Inputs are placed into `/inputs` in the working directory of your job. A directory called `/outputs` is also created, to store any file outputs.\n",
+    ".. note:: As part of execution, the DPS will create a directory called `/inputs`. Copies of the Inputs are placed into `/inputs` in the working directory of your job. A directory called `/outputs` is also created, to store any file outputs.\n",
     "\n",
     "\n",
-    "5. When it looks good, press Register Algorithm at the bottom of the page. A few seconds later you should see a modal dialog with a link to the algorithm registration process. \n",
+    "6. When it looks good, press Register Algorithm at the bottom of the page. A few seconds later you should see a notification with a link to your \"My Builds and Deployments\" page. \n",
     "![Register Algorithm submitted](_static/register-4-modal.png)\n",
     "\n",
     "\n",
-    "6. If you open that link in a new page or tab, you can monitor the progress of registration and see any error messages. By opening it in a new tab/window you can keep the Register Algorithm tool open and re-submit with the same values to correct any errors.\n",
+    "7. You can monitor the progress of registration and see any error messages in your \"My Builds and Deployments\" page. You can click the link in the Build Status column to see the GitLab pipeline of your building algorithm \n",
     "\n",
-    "Here is an example error message:\n",
-    "![Register Algorithm error](_static/register-5-status.png)\n",
+    "Here is an example of a building algorithm:\n",
+    "![Register Algorithm Building](_static/register-5-status.png)\n",
     "\n",
-    "If the process continues without failing (this may take some time) you will ultimately see \"Job succeeded\":\n",
-    "![Register Algorithm success](_static/register-6-success.png)\n",
-    "\n",
-    "At this point you have successfully registered your Algorithm, and it is ready to be run in the DPS.\n"
+    "Once the Build Status is successful, it is ready to be run in the DPS.\n"
    ]
   },
   {
@@ -99,33 +87,24 @@
     "\n",
     "![Jobs UI in Launcher](_static/run-1-launcher.png)\n",
     "\n",
-    "2. You can run your newly-registered Algorithm here. You will see it in the Submit Jobs tool in the Algorithm drop-down menu. If you open the dropdown menu, you can type a few letters to filter the list. Your Algorithm will be labeled with the name you put into the Algorithm Name field in the registration form you just submitted (in this example, `rob_test_registration_2406b` with version/branch `main`).\n",
-    "\n",
-    "![Jobs UI with new Algorithm](_static/register-7-jobsui.png)\n",
+    "2. You can run your newly-registered Algorithm here. You will see it in the Submit Jobs tool in the Algorithm drop-down menu. If you open the dropdown menu, you can type a few letters to filter the list. Your Algorithm will be labeled with the name you put into the Algorithm Name field in the registration form you just submitted. Select the desired Algorithm version and Deployed By fields \n",
     "\n",
-    "3. Once you have selected the Algorithm that you just registered, the form will display the inputs. By default every job has a \"Job Tag\" field and a \"Resource\" dropdown. Additionally, any inputs that you configured in your algorithm during registration will be available; in this case we have the \"input_file\" field.\n",
+    "3. Next you can select a resource queue, the queues you see are the ones you have access to. Job tag is an identifier for your job you can use as a label. It doesn't need to be unique \n",
     "\n",
-    "For our test run, choose a Job Tag that's distinctive. In this example we used `test_run_2024b` but you should pick your own. For the Resource, we can over-ride the one that we used during Algorithm registration; for the sake of this example we chose the same one as before (`maap-dps-work-8gb`).\n",
+    "4. Now, you can configure the inputs which are based on the algorithm you submitted \n",
     "\n",
-    "The input_file can be any file that is publicly accessible to MAAP, for example any file on the web. As an example you can use:\n",
-    "```\n",
-    "https://photojournal.jpl.nasa.gov/jpeg/PIA17931.jpg\n",
-    "```\n",
-    "\n",
-    "Leave the \"Publish to Content Metadata Repository\" section alone. This is an old placeholder feature that will be removed. You might not see that section of the Job submission form.\n",
+    "As a note, input files can be any file that is publicly accessible to MAAP, for example any file on the web. \n",
     "\n",
     "![Filled Submit Job form](_static/run-2-filledform.png)\n",
     "\n",
-    "4. Press **Submit Job**. A few seconds later a message should appear beneath the button indicating a successful job submission.\n",
-    "\n",
-    "![Submitted Job](_static/run-3-submitsuccess.png)\n",
+    "4. Press **Submit Job**. A few seconds later a notification should appear indicating a successful job submission.\n",
     "\n",
-    "5. Next, in the Launcher open the View Jobs tool (next to the Submit Jobs tool). If you do not see your test Job, you may need to refresh the table that opens up by pressing the button next to the \"Last updated\" message.\n",
+    "5. Next, in the Launcher open the View Jobs tool (next to the Submit Jobs tool). If you do not see your test Job, you may need to refresh the table that opens up by pressing the blue button next to the \"Last updated\" message.\n",
     "![Job List](_static/run-4-viewjobs.png)\n",
     "\n",
     "6. Your Job should finish shortly (use the refresh button to update the table as needed). Click on your Job in the table and the bottom panel will show the Job Details for that Job. Explore the various sections on your own to familiarize yourself with the information available.\n",
     "\n",
-    "If you select the Outputs section, you will see two buttons to help look at the outputs of your Job. \"Copy File Path to Clipboard\" can be useful if you need to record the path to another document, a script, or into a Terminal. \"Open in File Browser\" will open up the file panel in Jupyter to the output path, as shown here. Note that the demo Algorithm writes a text file called `write-output.txt`.\n",
+    "If you select the Outputs section, you can select \"Open in Workspace\" to open up the file panel in Jupyter to the output path, as shown here. \n",
     "![Output File Browser](_static/run-5-viewoutputs.png)\n",
     "\n",
     "One way to get your output files is to right-click in the File Browser and choose \"Download\".\n",

diff --git a/docs/source/index.rst b/docs/source/index.rst
@@ -5,6 +5,12 @@
 
 Welcome to the MAAP User Documentation!
 =======================================
+.. attention::
+    MAAP is transitioning from the MAAP ADE to the MAAP Hub for interactive Jupyterhub coding environments. The documentation now reflects the MAAP Hub as the default. 
+
+    If you need to look up information specific to the MAAP ADE, please see `last-ade-release <https://docs.maap-project.org/en/last-ade-release/>`_. 
+
+    Documentation around all other aspects of MAAP remains unchanged, including the use of maap-py and DPS.
 
 .. toctree::
   :maxdepth: 1

diff --git a/docs/source/release_notes.rst b/docs/source/release_notes.rst
@@ -3,6 +3,33 @@ Release Notes
 
 Release notes will mention the release date, a summary for each release, and comprehensive descriptions of major changes, minor changes, feature removal, and bug-fixes. This is typically more comprehensive than the announcements on the GitHub Discussion board: https://github.com/orgs/MAAP-Project/discussions/categories/announcements.
 
+-------------------------------------------------------------
+5.1.0
+-------------------------------------------------------------
+| March 3, 2026
+| Release with several important improvements. To use the new features, please start a new v5.1.0 workspace.
+
+Breaking changes
+^^^^^^^^^^^^
+* Updated to R 4.5.1
+* Updated packages in the R, Pangeo, and Isce3 images
+* Isce3 image has gdal bump from 3.11.4 to 3.11.5 
+* R image is using awsv2 aliased as aws 
+
+
+Fixed
+^^^^^^^^^^^^
+* RStudio fixes: AWS access and DPS job submissions with maap-py 
+* TensorFlow2 and PyTorch GPU images upgraded to Pangeo 2025.12.30
+* Pangeo image upgraded to Pangeo 2025.12.30
+* Isce3 image upgraded to Pangeo 2026.01.21
+* MAAP API improvements for authentication  
+
+
+Added
+^^^^^^^^^^^^
+* TensorFlow2 and PyTorch GPU images with MAAP extensions (Pangeo 2025.12.30)
+
 -------------------------------------------------------------
 4.3.0
 -------------------------------------------------------------