From 9fd2c4c0861b6e8b0778d38de2b164ec79837e38 Mon Sep 17 00:00:00 2001 From: Mo King Date: Wed, 4 Feb 2026 17:30:19 -0500 Subject: [PATCH] Fix UI inconsistencies in Your First Project part 1 + 2 --- docs/operate/hello-world/first-project/part-1.md | 12 ++++++------ docs/operate/hello-world/first-project/part-2.md | 14 +++++++------- 2 files changed, 13 insertions(+), 13 deletions(-) diff --git a/docs/operate/hello-world/first-project/part-1.md b/docs/operate/hello-world/first-project/part-1.md index ec65f22ecd..a7bc724643 100644 --- a/docs/operate/hello-world/first-project/part-1.md +++ b/docs/operate/hello-world/first-project/part-1.md @@ -71,14 +71,15 @@ To add the camera component to your machine part: 6. Enter `inspection-cam` for the name {{< expand "Why were two items added to my machine part?" >}} -After adding the camera component, you will see two items appear under your machine part. One is the actual camera hardware (`inspection-cam`) that you will use through the Viam camera API. The other is the software module (`gz-camera`) that implements this API for the specific model of camera you are using. All components that are supported through modules available in the Viam registry will appear this way in the **Configuration** tab. For built-in components, such as webcams, you will not also see a module appear in the configuration. +After adding the camera component, you will see two items appear under your machine part. One is the actual camera hardware (`inspection-cam`) that you will use through the Viam camera API. The other is the software module (`gz-camera`) that implements this API for the specific model of camera you are using. All components that are supported through modules available in the Viam registry will appear this way in the **Configure** tab. For built-in components, such as webcams, you will not also see a module appear in the configuration. {{< /expand >}} ### Configure the camera To configure your camera component to work with the camera in the simulation, you need to specify the correct camera ID. Most components require a few configuration parameters. -1. In the **Attributes** section, add: +1. Select the `inspection-cam` component in your machine’s configuration +2. Add this to the **JSON configuration** field: ```json { @@ -141,10 +142,9 @@ The **ML model service** loads a trained model (TensorFlow, ONNX, or PyTorch) an Configure the `model-service` ML model service you just included in your configuration. 1. In the `model-service` configuration panel, click **Select model** -2. Click the **Registry** tab -3. Search for `can-defect-detection` and select it from the list (a model that classifies cans as PASS or FAIL based on defect detection) -4. Click **Choose** to save the model selection -5. Click **Save** in the upper right corner to save your configuration +2. Search for `can-defect-detection` and select it from the list (a model that classifies cans as PASS or FAIL based on defect detection) +3. Click **Choose** to save the model selection +4. Click **Save** in the upper right corner to save your configuration {{< alert title="Your own models" color="tip" >}} For a different application, you'd train a model on your specific data and upload it to the registry. The registry handles versioning and deployment of ML models across your fleet. diff --git a/docs/operate/hello-world/first-project/part-2.md b/docs/operate/hello-world/first-project/part-2.md index 6ddd3a64b9..8756e418f1 100644 --- a/docs/operate/hello-world/first-project/part-2.md +++ b/docs/operate/hello-world/first-project/part-2.md @@ -53,7 +53,7 @@ The default configuration options for the data service are correct for our appli Your machine is now capturing detection results and images every 2 seconds and syncing them to the Viam cloud application. Once synced to the cloud, the data is removed from your machine to free up storage. {{< alert title="Tip" color="tip" >}} -Click **JSON** in the Configure tab to see how data capture settings appear in the raw configuration. Each component and service with data capture enabled has a `service_configs` entry containing `capture_methods`. +Click **JSON** in the **Configure** tab (above the sidebar on the left) to see how data capture settings appear in the raw configuration. Each component and service with data capture enabled has a `service_configs` entry containing `capture_methods`. {{< /alert >}} ## 2.2 View Captured Data @@ -73,16 +73,16 @@ Right click on **Data** to open in a separate tab. **Verify the data includes:** -- **Detection results**—Each row shows label (PASS/FAIL) and confidence score -- **Camera images**—Click any row to see the image that was analyzed +- **Detection results**—Each capture that detected a can shows a label (PASS/FAIL) +- **Camera images**—Click any capture to see the image that was analyzed - **Timestamps**—When each capture occurred -- **Machine ID**—Which machine captured it (matters when you have multiple stations) +- **Machine**—Which machine captured it (matters when you have multiple stations) **Filter the data:** -1. Click **Filter** and select your machine: `inspection-station-1` -2. Set time range to "Last hour" -3. You can also filter by component to see only vision service results or only camera images +1. Under **Filters**, click the dropdown for **Machine name** and select your machine: `inspection-station-1` +2. Update **Start time** and **End time** to filter for images in the last hour +3. Click **Apply** to filter the results This captured data serves multiple purposes: