workbench 0.8.224__tar.gz → 0.8.230__tar.gz

{workbench-0.8.224 → workbench-0.8.230}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: workbench
-Version: 0.8.224
+Version: 0.8.230
 Summary: Workbench: A Dashboard and Python API for creating and deploying AWS SageMaker Model Pipelines
 Author-email: SuperCowPowers LLC <support@supercowpowers.com>
 License: MIT License
@@ -60,7 +60,7 @@ Requires-Dist: plotly>=6.0.0; extra == "ui"
 Requires-Dist: dash>=3.0.0; extra == "ui"
 Requires-Dist: dash-bootstrap-components>=1.6.0; extra == "ui"
 Requires-Dist: dash-bootstrap-templates>=1.3.0; extra == "ui"
-Requires-Dist: dash_ag_grid; extra == "ui"
+Requires-Dist: dash_ag_grid<=32.3.2; extra == "ui"
 Requires-Dist: tabulate>=0.9.0; extra == "ui"
 Requires-Dist: matplotlib>=3.9.2; extra == "ui"
 Provides-Extra: dev
@@ -77,51 +77,49 @@ Requires-Dist: workbench[dev]; extra == "all"
 Dynamic: license-file
 
 
-# Recent News
+## Live Dashboard Demo
+You can explore a live demo of the Workbench Dashboard at: [Workbench Dashboard Demo](https://workbench-dashboard.com)
 
-### Themes
+## Recent News
+**Chemprop Models!** All the rage for the Open ADMET Challenge. 
 
-Everyone knows that good data science requires... **Some Awesome Themes!**
+Workbench now supports:
+- Single Task Chemprop Models
+- Multi Task Chemprop Models
+- Chemprop Hybrid Models (MPNN + Descriptors)
+- Foundation Chemprop Models (CheMeleon Pretrained)
+
+Examples: 
+
+- [Deploying Chemprop Models](examples/models/chemprop.py)
+- [Deploying Foundation Chemprop Models](examples/models/chemprop_foundation.py)
+
+**References**
+- [Open ADMET Challenge](https://huggingface.co/spaces/openadmet/OpenADMET-ExpansionRx-Challenge)
+- **ChemProp:** Yang et al. "Analyzing Learned Molecular Representations for Property Prediction" *J. Chem. Inf. Model.* 2019 — [GitHub](https://github.com/chemprop/chemprop) | [Paper](https://pubs.acs.org/doi/10.1021/acs.jcim.9b00237)
+- [CheMeleon Github](https://github.com/JacksonBurns/chemeleon)
+
+### Chemprop Action Shots!
 
 <table>
   <tr>
     <td>
-      <a href="https://github.com/user-attachments/assets/82ab4eab-0688-4b93-ad8e-9b954564777b">
-        <img width="400" alt="theme_dark" src="https://github.com/user-attachments/assets/82ab4eab-0688-4b93-ad8e-9b954564777b" />
-      </a>
-    </td>
-    <td>
-      <a href="https://github.com/user-attachments/assets/b63a0789-c144-4048-afb6-f03e3d993680">
-        <img width="400" alt="theme_light" src="https://github.com/user-attachments/assets/b63a0789-c144-4048-afb6-f03e3d993680" />
+      <a href="https://github.com/user-attachments/assets/a36c6eff-c464-4c9a-9859-a45cd7e35145">
+        <img width="800" alt="theme_dark" src="https://github.com/user-attachments/assets/a36c6eff-c464-4c9a-9859-a45cd7e35145" />
       </a>
     </td>
   </tr>
   <tr>
     <td>
-      <a href="https://github.com/user-attachments/assets/8a59be19-0c5d-42c6-9922-feafb1a1eecd">
-        <img width="400" alt="theme_quartz" src="https://github.com/user-attachments/assets/8a59be19-0c5d-42c6-9922-feafb1a1eecd" />
-      </a>
-    </td>
-    <td>
-      <a href="https://github.com/user-attachments/assets/5b01ec64-8d56-43bf-96c5-7da8ec48f527">
-        <img width="400" alt="theme_quartz_dark" src="https://github.com/user-attachments/assets/5b01ec64-8d56-43bf-96c5-7da8ec48f527" />
+      <a href="https://github.com/user-attachments/assets/d65ec1da-e04e-44fe-8782-4da0fb50588a">
+        <img width="800" alt="theme_quartz" src="https://github.com/user-attachments/assets/d65ec1da-e04e-44fe-8782-4da0fb50588a" />
       </a>
     </td>
   </tr>
 </table>
 
-All of the Dashboard pages, subpages, and plugins use our new `ThemeManager()` class. See [Workbench Themes](https://supercowpowers.github.io/workbench/themes/), also big thanks to our friends at [Dash Bootstrap Templates](https://github.com/AnnMarieW/dash-bootstrap-templates)
-
 
 
-### Workbench up on the AWS Marketplace
-
-Powered by AWS® to accelerate your Machine Learning Pipelines development with our new [Dashboard for ML Pipelines](https://aws.amazon.com/marketplace/pp/prodview-5idedc7uptbqo). Getting started with Workbench is a snap and can be billed through AWS.
-
-### Coming Soon: `v0.9`
-
-We're getting ready for our `v0.9` release. Here's the road map: [Workbench RoadMaps](https://supercowpowers.github.io/workbench/road_maps/0_9_0/) 
-
 # Welcome to Workbench
 The Workbench framework makes AWS® both easier to use and more powerful. Workbench handles all the details around updating and managing a complex set of AWS Services. With a simple-to-use Python API and a beautiful set of web interfaces, Workbench makes creating AWS ML pipelines a snap. It also dramatically improves both the usability and visibility across the entire spectrum of services: Glue Job, Athena, Feature Store, Models, and Endpoints, Workbench makes it easy to build production ready, AWS powered, machine learning pipelines.
 
@@ -159,6 +157,10 @@ For the full instructions for connecting your AWS Account see:
 - One time AWS Onboarding: [AWS Setup](https://supercowpowers.github.io/workbench/aws_setup/core_stack/)
 
 
+### Workbench up on the AWS Marketplace
+
+Powered by AWS® to accelerate your Machine Learning Pipelines development with our new [Dashboard for ML Pipelines](https://aws.amazon.com/marketplace/pp/prodview-5idedc7uptbqo). Getting started with Workbench is a snap and can be billed through AWS.
+
 ### Workbench Presentations
 Even though Workbench makes AWS easier, it's taking something very complex (the full set of AWS ML Pipelines/Services) and making it less complex. Workbench has a depth and breadth of functionality so we've provided higher level conceptual documentation See: [Workbench Presentations](https://supercowpowers.github.io/workbench/presentations/)
 

{workbench-0.8.224 → workbench-0.8.230}/README.md

@@ -1,49 +1,47 @@
 
-# Recent News
+## Live Dashboard Demo
+You can explore a live demo of the Workbench Dashboard at: [Workbench Dashboard Demo](https://workbench-dashboard.com)
 
-### Themes
+## Recent News
+**Chemprop Models!** All the rage for the Open ADMET Challenge. 
 
-Everyone knows that good data science requires... **Some Awesome Themes!**
+Workbench now supports:
+- Single Task Chemprop Models
+- Multi Task Chemprop Models
+- Chemprop Hybrid Models (MPNN + Descriptors)
+- Foundation Chemprop Models (CheMeleon Pretrained)
+
+Examples: 
+
+- [Deploying Chemprop Models](examples/models/chemprop.py)
+- [Deploying Foundation Chemprop Models](examples/models/chemprop_foundation.py)
+
+**References**
+- [Open ADMET Challenge](https://huggingface.co/spaces/openadmet/OpenADMET-ExpansionRx-Challenge)
+- **ChemProp:** Yang et al. "Analyzing Learned Molecular Representations for Property Prediction" *J. Chem. Inf. Model.* 2019 — [GitHub](https://github.com/chemprop/chemprop) | [Paper](https://pubs.acs.org/doi/10.1021/acs.jcim.9b00237)
+- [CheMeleon Github](https://github.com/JacksonBurns/chemeleon)
+
+### Chemprop Action Shots!
 
 <table>
   <tr>
     <td>
-      <a href="https://github.com/user-attachments/assets/82ab4eab-0688-4b93-ad8e-9b954564777b">
-        <img width="400" alt="theme_dark" src="https://github.com/user-attachments/assets/82ab4eab-0688-4b93-ad8e-9b954564777b" />
-      </a>
-    </td>
-    <td>
-      <a href="https://github.com/user-attachments/assets/b63a0789-c144-4048-afb6-f03e3d993680">
-        <img width="400" alt="theme_light" src="https://github.com/user-attachments/assets/b63a0789-c144-4048-afb6-f03e3d993680" />
+      <a href="https://github.com/user-attachments/assets/a36c6eff-c464-4c9a-9859-a45cd7e35145">
+        <img width="800" alt="theme_dark" src="https://github.com/user-attachments/assets/a36c6eff-c464-4c9a-9859-a45cd7e35145" />
       </a>
     </td>
   </tr>
   <tr>
     <td>
-      <a href="https://github.com/user-attachments/assets/8a59be19-0c5d-42c6-9922-feafb1a1eecd">
-        <img width="400" alt="theme_quartz" src="https://github.com/user-attachments/assets/8a59be19-0c5d-42c6-9922-feafb1a1eecd" />
-      </a>
-    </td>
-    <td>
-      <a href="https://github.com/user-attachments/assets/5b01ec64-8d56-43bf-96c5-7da8ec48f527">
-        <img width="400" alt="theme_quartz_dark" src="https://github.com/user-attachments/assets/5b01ec64-8d56-43bf-96c5-7da8ec48f527" />
+      <a href="https://github.com/user-attachments/assets/d65ec1da-e04e-44fe-8782-4da0fb50588a">
+        <img width="800" alt="theme_quartz" src="https://github.com/user-attachments/assets/d65ec1da-e04e-44fe-8782-4da0fb50588a" />
       </a>
     </td>
   </tr>
 </table>
 
-All of the Dashboard pages, subpages, and plugins use our new `ThemeManager()` class. See [Workbench Themes](https://supercowpowers.github.io/workbench/themes/), also big thanks to our friends at [Dash Bootstrap Templates](https://github.com/AnnMarieW/dash-bootstrap-templates)
-
 
 
-### Workbench up on the AWS Marketplace
-
-Powered by AWS® to accelerate your Machine Learning Pipelines development with our new [Dashboard for ML Pipelines](https://aws.amazon.com/marketplace/pp/prodview-5idedc7uptbqo). Getting started with Workbench is a snap and can be billed through AWS.
-
-### Coming Soon: `v0.9`
-
-We're getting ready for our `v0.9` release. Here's the road map: [Workbench RoadMaps](https://supercowpowers.github.io/workbench/road_maps/0_9_0/) 
-
 # Welcome to Workbench
 The Workbench framework makes AWS® both easier to use and more powerful. Workbench handles all the details around updating and managing a complex set of AWS Services. With a simple-to-use Python API and a beautiful set of web interfaces, Workbench makes creating AWS ML pipelines a snap. It also dramatically improves both the usability and visibility across the entire spectrum of services: Glue Job, Athena, Feature Store, Models, and Endpoints, Workbench makes it easy to build production ready, AWS powered, machine learning pipelines.
 
@@ -81,6 +79,10 @@ For the full instructions for connecting your AWS Account see:
 - One time AWS Onboarding: [AWS Setup](https://supercowpowers.github.io/workbench/aws_setup/core_stack/)
 
 
+### Workbench up on the AWS Marketplace
+
+Powered by AWS® to accelerate your Machine Learning Pipelines development with our new [Dashboard for ML Pipelines](https://aws.amazon.com/marketplace/pp/prodview-5idedc7uptbqo). Getting started with Workbench is a snap and can be billed through AWS.
+
 ### Workbench Presentations
 Even though Workbench makes AWS easier, it's taking something very complex (the full set of AWS ML Pipelines/Services) and making it less complex. Workbench has a depth and breadth of functionality so we've provided higher level conceptual documentation See: [Workbench Presentations](https://supercowpowers.github.io/workbench/presentations/)
 

{workbench-0.8.224 → workbench-0.8.230}/applications/aws_dashboard/Dockerfile

@@ -1,4 +1,16 @@
-# Base image: python:3.12.5-bookworm
+# Define workbench version once at the top
+ARG WORKBENCH_VERSION=0.8.228
+
+# Stage 1: Extract dependencies from workbench[ui]
+FROM python:3.12.5-bookworm AS deps-extractor
+ARG WORKBENCH_VERSION
+RUN pip install --no-cache-dir pip-tools && \
+    pip download --no-deps "workbench[ui]==${WORKBENCH_VERSION}" -d /tmp/pkg && \
+    cd /tmp/pkg && unzip -q *.whl -d /tmp/extracted && \
+    cat /tmp/extracted/*.dist-info/METADATA | grep "^Requires-Dist:" | \
+    sed 's/Requires-Dist: //' | sed 's/;.*//' | sed 's/ (.*//' > /tmp/deps.txt
+
+# Stage 2: Build the final image
 FROM python:3.12.5-bookworm AS base
 WORKDIR /app
 EXPOSE 8000
@@ -6,9 +18,6 @@ EXPOSE 8000
 # Set PYTHONHASHSEED to ensure consistent hashing across processes
 ENV PYTHONHASHSEED=0
 
-# Define workbench version
-ARG WORKBENCH_VERSION=0.8.208
-
 # Install system packages and gunicorn in one layer
 RUN apt-get update && apt-get install -y --no-install-recommends \
     nginx supervisor libnghttp2-dev && \
@@ -16,13 +25,13 @@ RUN apt-get update && apt-get install -y --no-install-recommends \
     rm -rf /var/lib/apt/lists/* && \
     pip install --no-cache-dir gunicorn
 
-# Dependency Layer: Install all dependencies of workbench[ui]
-RUN pip install --no-cache-dir "workbench[ui]==${WORKBENCH_VERSION}" && \
-    pip uninstall -y workbench && \
-    pip cache purge
+# Copy and install dependencies (this layer only changes when deps change)
+COPY --from=deps-extractor /tmp/deps.txt /tmp/deps.txt
+RUN pip install --no-cache-dir -r /tmp/deps.txt && rm /tmp/deps.txt
 
 # Install workbench[ui] in separate layer (dependencies already satisfied)
-RUN pip install --no-cache-dir "workbench[ui]==${WORKBENCH_VERSION}"
+ARG WORKBENCH_VERSION
+RUN pip install --no-cache-dir --no-deps "workbench[ui]==${WORKBENCH_VERSION}"
 
 # Copy app code and configuration (after pip installs to avoid cache invalidation)
 COPY . /app

{workbench-0.8.224 → workbench-0.8.230}/applications/aws_dashboard/pages/data_sources/page.py

@@ -21,19 +21,11 @@ register_page(
 
 # Create a table to display the Data Sources
 data_sources_table = AGTable()
-data_sources_component = data_sources_table.create_component(
-    "data_sources_table",
-    header_color="rgb(120, 70, 70)",
-    max_height=270,
-)
+data_sources_component = data_sources_table.create_component("data_sources_table", max_height=270)
 
 # Create a table that sample rows from the currently selected data source
 samples_table = AGTable()
-samples_component = samples_table.create_component(
-    "data_source_sample_rows",
-    header_color="rgb(70, 70, 110)",
-    max_height=250,
-)
+samples_component = samples_table.create_component("data_source_sample_rows", max_height=250)
 
 # Data Source Details Markdown PANEL
 data_details = DataDetails()

{workbench-0.8.224 → workbench-0.8.230}/applications/aws_dashboard/pages/endpoints/page.py

@@ -23,9 +23,7 @@ register_page(
 
 # Create a table to display the endpoints
 endpoints_table = ag_table.AGTable()
-endpoints_component = endpoints_table.create_component(
-    "endpoints_table", header_color="rgb(100, 60, 100)", max_height=270
-)
+endpoints_component = endpoints_table.create_component("endpoints_table", max_height=270)
 
 # Create a Markdown component to display the endpoint details
 endpoint_details = endpoint_details.EndpointDetails()

{workbench-0.8.224 → workbench-0.8.230}/applications/aws_dashboard/pages/feature_sets/page.py

@@ -16,17 +16,11 @@ register_page(__name__, path="/feature_sets", name="Workbench - Feature Sets")
 
 # Create a table to display the Feature Sets
 feature_sets_table = AGTable()
-feature_sets_component = feature_sets_table.create_component(
-    "feature_sets_table", header_color="rgb(60, 100, 60)", max_height=270
-)
+feature_sets_component = feature_sets_table.create_component("feature_sets_table", max_height=270)
 
 # Grab smart_sample rows from the first Feature Set
 samples_table = AGTable()
-samples_component = samples_table.create_component(
-    "feature_set_sample_rows",
-    header_color="rgb(70, 70, 110)",
-    max_height=250,
-)
+samples_component = samples_table.create_component("feature_set_sample_rows", max_height=250)
 
 # Feature Set Details
 feature_details = DataDetails()

{workbench-0.8.224 → workbench-0.8.230}/applications/aws_dashboard/pages/main/page.py

@@ -25,29 +25,13 @@ for table_name in table_names:
 # Create a table container for each Workbench Artifact Type
 table_containers = dict()
 table_name = "data_sources"
-table_containers[table_name] = tables[table_name].create_component(
-    f"main_{table_name}",
-    header_color="rgb(120, 70, 70)",
-    max_height=200,
-)
+table_containers[table_name] = tables[table_name].create_component(f"main_{table_name}", max_height=200)
 table_name = "feature_sets"
-table_containers[table_name] = tables[table_name].create_component(
-    f"main_{table_name}",
-    header_color="rgb(110, 110, 70)",
-    max_height=200,
-)
+table_containers[table_name] = tables[table_name].create_component(f"main_{table_name}", max_height=200)
 table_name = "models"
-table_containers[table_name] = tables[table_name].create_component(
-    f"main_{table_name}",
-    header_color="rgb(60, 100, 60)",
-    max_height=500,
-)
+table_containers[table_name] = tables[table_name].create_component(f"main_{table_name}", max_height=500)
 table_name = "endpoints"
-table_containers[table_name] = tables[table_name].create_component(
-    f"main_{table_name}",
-    header_color="rgb(100, 60, 100)",
-    max_height=500,
-)
+table_containers[table_name] = tables[table_name].create_component(f"main_{table_name}", max_height=500)
 
 # Set up our layout (Dash looks for a var called layout)
 layout = main_layout(**table_containers)

{workbench-0.8.224 → workbench-0.8.230}/applications/aws_dashboard/pages/models/callbacks.py

@@ -5,7 +5,6 @@ from dash import callback, no_update, Input, Output, State
 from dash.exceptions import PreventUpdate
 from urllib.parse import urlparse, parse_qs
 
-
 # Workbench Imports
 from workbench.api import ModelType
 from workbench.web_interface.page_views.models_page_view import ModelsPageView
@@ -136,18 +135,19 @@ def setup_plugin_callbacks(plugins, scatter_plot_plugin: ScatterPlot, confusion_
             if df is None:
                 raise PreventUpdate
 
-            # Get target column and compute error for coloring
+            # Get target column (residual is already computed in CachedModel)
             target = model.target()
             if isinstance(target, list):
                 target = next((t for t in target if t in inference_run), target[0])
 
-            df["error"] = abs(df["prediction"] - df[target])
+            # Check if "confidence" column exists for coloring
+            color_col = "confidence" if "confidence" in df.columns else "prediction"
 
             scatter_props = scatter_plot_plugin.update_properties(
                 df,
                 x=target,
                 y="prediction",
-                color="error",
+                color=color_col,
                 regression_line=True,
             )
             cm_props = [no_update] * len(confusion_matrix_plugin.properties)

{workbench-0.8.224 → workbench-0.8.230}/applications/aws_dashboard/pages/models/layout.py

@@ -37,8 +37,8 @@ def models_layout(
                 [
                     # Column 1: Model Details
                     dbc.Col(
-                        dcc.Loading(model_details, type="dot", color="#33aa33", delay_show=1000, delay_hide=100),
-                        width=5,
+                        dcc.Loading(model_details, type="dot", color="#33aa33", delay_show=1000),
+                        width=4,
                         className="text-break workbench-container",
                         style={"margin": "20px 0px 0px 0px", "padding": "20px"},
                     ),
@@ -46,7 +46,11 @@ def models_layout(
                     dbc.Col(
                         [
                             dbc.Row(
-                                dcc.Loading(model_plot, type="graph", delay_show=500, style={"height": "400px"}),
+                                dcc.Loading(
+                                    model_plot,
+                                    type="graph",
+                                    delay_show=500,
+                                ),
                                 className="workbench-container",
                                 style={"margin": "20px 0px 10px 20px"},
                             ),
@@ -56,7 +60,7 @@ def models_layout(
                                 style={"margin": "20px 0px 10px 20px"},
                             ),
                         ],
-                        width=7,
+                        width=8,
                         style={"padding": "0px"},
                     ),
                 ],

{workbench-0.8.224 → workbench-0.8.230}/applications/aws_dashboard/pages/models/page.py

@@ -25,7 +25,7 @@ register_page(
 
 # Create a table to display the models
 models_table = ag_table.AGTable()
-models_table_component = models_table.create_component("models_table", header_color="rgb(60, 100, 60)", max_height=270)
+models_table_component = models_table.create_component("models_table", max_height=270)
 
 # Create a Markdown component to display the model details
 my_model_details = model_details.ModelDetails()
@@ -40,9 +40,11 @@ my_confusion_matrix = confusion_matrix.ConfusionMatrix()
 confusion_matrix_component = my_confusion_matrix.create_component("model_confusion_matrix")
 
 # Wrap both in visibility-controlled containers
+# Show scatter plot by default (with "Waiting for Data..." placeholder)
+# The callback will toggle visibility based on model type once data loads
 model_plot_container = html.Div(
     [
-        html.Div(scatter_plot_component, id="scatter-plot-container", style={"display": "none"}),
+        html.Div(scatter_plot_component, id="scatter-plot-container", style={"display": "block"}),
         html.Div(confusion_matrix_component, id="confusion-matrix-container", style={"display": "none"}),
     ],
     id="model-plot-container",

{workbench-0.8.224 → workbench-0.8.230}/applications/aws_dashboard/pages/pipelines/callbacks.py

@@ -6,7 +6,6 @@ from dash import callback, Output, Input, State
 from dash.exceptions import PreventUpdate
 from urllib.parse import urlparse, parse_qs
 
-
 # Workbench Imports
 from workbench.web_interface.page_views.pipelines_page_view import PipelinesPageView
 from workbench.web_interface.components.plugins.ag_table import AGTable

{workbench-0.8.224 → workbench-0.8.230}/applications/aws_dashboard/pages/status/page.py

@@ -7,7 +7,6 @@ from dash import html
 from workbench.web_interface.components.plugins import dashboard_status
 from workbench.utils.config_manager import ConfigManager
 
-
 # Register this page with Dash
 register_page(
     __name__,

{workbench-0.8.224 → workbench-0.8.230}/applications/compound_explorer/app.py

@@ -11,7 +11,6 @@ from workbench.web_interface.components.plugins import scatter_plot, molecule_vi
 from layout import compound_explorer_layout
 import callbacks
 
-
 # Note: The 'app' and 'server' objects need to be at the top level since NGINX/uWSGI needs to
 #       import this file and use the server object as an ^entry-point^ into the Dash Application Code
 

{workbench-0.8.224 → workbench-0.8.230}/aws_setup/workbench_core/workbench_core/workbench_core_stack.py

@@ -180,6 +180,7 @@ class WorkbenchCoreStack(Stack):
                 "glue:GetDatabases",
                 "glue:GetTable",
                 "glue:GetTables",
+                "glue:GetPartitions",
                 "glue:SearchTables",
             ],
             resources=[f"arn:aws:glue:{self.region}:{self.account}:catalog"],

{workbench-0.8.224 → workbench-0.8.230}/aws_setup/workbench_dashboard_full/app.py

@@ -12,7 +12,7 @@ print(f"Account: {aws_account}")
 print(f"Region: {aws_region}")
 
 # When you want a different docker image change this line
-dashboard_image = "public.ecr.aws/m6i5k1r2/workbench_dashboard:v0_8_208_amd64"
+dashboard_image = "public.ecr.aws/m6i5k1r2/workbench_dashboard:v0_8_228_amd64"
 
 # Workbench Configuration
 try:

{workbench-0.8.224 → workbench-0.8.230}/aws_setup/workbench_dashboard_lite/app.py

@@ -12,7 +12,7 @@ print(f"Account: {aws_account}")
 print(f"Region: {aws_region}")
 
 # When you want a different docker image change this line
-dashboard_image = "public.ecr.aws/m6i5k1r2/workbench_dashboard:v0_8_208_amd64"
+dashboard_image = "public.ecr.aws/m6i5k1r2/workbench_dashboard:v0_8_228_amd64"
 
 # Workbench Configuration
 try:

{workbench-0.8.224 → workbench-0.8.230}/docs/admin/dashboard_docker_push.md

@@ -6,9 +6,10 @@ Notes and information on how to do the Dashboard Docker Builds and Push to AWS E
 ```
 cd applications/aws_dashboard
 vi Dockerfile
+...
 
-# Install workbench[ui] in separate layer
-RUN pip install --no-cache-dir "workbench[ui]==0.8.116"  <-- change this
+# Install workbench[ui] in separate layer (dependencies already satisfied)
+ARG WORKBENCH_VERSION=0.8.227  <-- change this
 ```
 
 ### Run the Deploy Script

{workbench-0.8.224 → workbench-0.8.230}/docs/themes/details.md

@@ -54,66 +54,30 @@ Bootstrap and Dash Bootstrap Components (DBC) provide mechanisms to control them
 
 # Theming Strategy for Workbench Dashboard
 
-## **Phase 1: Application Start-Up Theming**
-This focuses on setting a polished, cohesive interface at startup. It ensures:
+## **How Theme Switching Works**
 
-1. **CSS and Plotly Templates at Start-Up**:
-   - The current system handles global styles via CSS (including Flask-served `custom.css`) and Plotly templates (via `pio.templates.default`) during app initialization.
-2. **Highly Customizable Interface**:
-   - By leveraging both custom CSS and Plotly templates, you can style everything to match branding and preferences.
+Workbench supports dynamic theme switching at runtime. When a user changes themes, the page reloads to ensure all styling systems are applied consistently.
 
-### **Why Phase 1 Works Well**
-- **Plotly Templates**: Figures are automatically styled if `pio.templates.default` is set before app initialization.
-- **CSS**: Dynamically affects the entire app without additional callbacks.
-- **Scalability**: Suitable for large apps since styles and templates are applied globally.
+### **Why We Use Page Reload**
 
-<br><br>
+1. **CSS and Plotly Templates**:
+   - Global styles are handled via CSS (including Flask-served `custom.css`) and Plotly templates (via `pio.templates.default`) during app initialization.
+   - Plotly figures have their styling "baked in" at render time—they don't respond to CSS variable changes.
 
-## **Phase 2: Dynamic Theme Switching**
-Dynamic theme switching allows users to toggle between themes (e.g., light and dark) at runtime. This is more complex, and splitting it into its own phase will reduce the complexity of each Phase.
+2. **The Alternative Would Be Complex**:
+   - Without reload, every figure would need an explicit callback to re-render when themes change.
+   - With 20+ dynamic figures across plugin pages, wiring up individual callbacks isn't practical.
 
-### **Challenges with Dynamic Switching**
-1. **Encapsulation Barriers**:
-   - A centralized callback for theme switching needs to know about every figure or component in the app, which is not scalable.
-2. **Dynamic Content/Plugins**:
-   - We have plugin pages, views, and components. A Typical app has 20 figures dynamically created, adding complexity to centralized callbacks.
+3. **Reload Is Simple and Reliable**:
+   - A page reload ensures all three systems (CSS, Plotly templates, Bootstrap) are applied correctly.
+   - Theme switching is typically a one-time choice, not something users toggle frequently.
 
+### **What Happens on Theme Change**
 
-
-### **Proposed Solution: `set_theme()` Method**
-Introduce a `set_theme()` method in each component to manage its own updates:
-
-- **Figures**: Update their `layout.template` or regenerate themselves.
-- **HTML/CSS Components**: Dynamically update styles or toggle CSS classes.
-
-### **Advantages of `set_theme()`**
-1. **Encapsulation**:
-   - Each component knows how to update itself based on the theme.
-2. **Simple Callback**:
-   - The theme switch callback iterates through all registered components and calls their `set_theme()` method.
-3. **Scalable**:
-   - Suitable for multi-page apps with many dynamic components.
-
-
-
-## **How the Two Phases Work Together**
-### Phase 1:
-- **Focus**: Global theming at app start-up.
-- **What Works**:
-  - Plotly templates are applied to all figures by default.
-  - CSS styles are applied across the app.
-
-### Phase 2:
-- **Focus**: Extend components to dynamically update their theme.
-- **What to Add**:
-  - Extend components with a `set_theme(theme_name: str)` method.
-  - The callback triggers `set_theme()` for each registered component.
-
-
-
-## **Next Steps**
-- **Phase 1**: Finalize CSS and Plotly template integration for start-up theming.
-- **Phase 2**: Begin implementing a `set_theme()` system for individual components.
+1. User selects a new theme
+2. Theme preference is saved (persisted across sessions)
+3. Page reloads
+4. On reload, the new CSS stylesheet, Plotly template, and Bootstrap theme are all applied consistently
 
 <br><br><br>
 <br><br><br>

{workbench-0.8.224 → workbench-0.8.230}/docs/themes/index.md

@@ -47,6 +47,36 @@ The `data-bs-theme=light/dark` html attribute affects **Bootstrap-specific compo
 
 * Some figure parameters will automatically work, but for stuff like colorscales the component code needs to 'pull' that from the template meta data when it updates it's figure.
 
+## Why We Require a Page Reload for Theme Switching
+
+Workbench supports dynamic theme switching—you can change themes at runtime. However, switching themes triggers a page reload rather than an instant in-place update. If you've seen demos like the [Dash Bootstrap Theme Explorer Gallery](https://hellodash.pythonanywhere.com/theme-explorer/gallery) where themes switch instantly, you might wonder why we can't do the same.
+
+### The Technical Reality
+
+**Plotly figures don't respond to CSS variables.** Unlike Bootstrap components (buttons, cards, tables) which automatically re-style when `data-bs-theme` changes, Plotly figures have their styling "baked in" at render time. The figure's colors, fonts, and backgrounds are set when the figure is created—they don't dynamically respond to theme changes.
+
+### What dash-bootstrap-templates Actually Does
+
+Even the excellent [dash-bootstrap-templates](https://github.com/AnnMarieW/dash-bootstrap-templates) library has this limitation. From their docs:
+
+> *"The All-in-One component switches the Bootstrap stylesheet and sets the default Plotly figure template, however, figures must be updated in a callback in order to render the figure with the new template."*
+
+This means every figure needs an explicit callback to re-render when the theme changes. In a simple demo app with 3-5 figures, that's manageable. In Workbench, with 20+ dynamic figures across multiple plugin pages, wiring up individual callbacks for each figure isn't practical.
+
+### Three Separate Styling Systems
+
+| **System**           | **What It Styles**              | **Instant Switching?**                     |
+|----------------------|---------------------------------|--------------------------------------------|
+| CSS/Bootstrap        | Layout, buttons, cards, tables  | ✅ Yes (via `data-bs-theme`)                |
+| Plotly Templates     | Figure axes, colors, fonts      | ❌ No - requires figure re-render           |
+| Custom CSS           | Non-Bootstrap elements          | ⚠️ Requires stylesheet swap                 |
+
+### Our Approach: Reload on Theme Change
+
+Rather than implementing complex callback wiring for every figure across all plugin pages, Workbench takes a pragmatic approach: **when you switch themes, the page reloads**. This ensures all three styling systems (CSS, Plotly templates, and Bootstrap components) are applied consistently and correctly.
+
+The reload is fast, and theme selection is typically a one-time choice rather than something users toggle frequently. This approach gives us full theme flexibility without the architectural complexity of in-place figure updates.
+
 ## Additional Resources
 
 <img align="right" src="../images/scp.png" width="180">

{workbench-0.8.224 → workbench-0.8.230}/examples/datasource/datasource_from_df.py

@@ -2,7 +2,6 @@ from workbench.utils.test_data_generator import TestDataGenerator
 from workbench.api.data_source import DataSource
 from pprint import pprint
 
-
 # Create a new Data Source from a Pandas DataFrame
 gen_data = TestDataGenerator()
 df = gen_data.person_data()

{workbench-0.8.224 → workbench-0.8.230}/examples/ml_pipelines/wine_classifier.py

@@ -12,7 +12,6 @@ Endpoints:
 
 from workbench.api import DataSource, FeatureSet, Model, ModelType
 
-
 if __name__ == "__main__":
 
     # Create the wine_features FeatureSet

{workbench-0.8.224 → workbench-0.8.230}/examples/plugins/components/custom_plugin.py

@@ -2,7 +2,6 @@
 
 from dash import dcc
 
-
 # Workbench Imports
 from workbench.web_interface.components.plugin_interface import PluginInterface, PluginPage, PluginInputType
 from workbench.api.model import Model