Skip to content

Conversation

@ngrayluna
Copy link
Contributor

@ngrayluna ngrayluna commented Dec 23, 2025

Description

Classic Noah, started off as a simple "update images" task...then grew to a complete Runs rewrite...here's a summary of what I did:

New Documentation Pages (7 added):

  • customize-run-display.mdx - How to customize run display settings
  • delete-runs.mdx - Instructions for deleting runs
  • run-identifiers.mdx - Explanation of run IDs and identifiers
  • run-states.mdx - Documentation on run states
  • search-runs.mdx - How to search for runs
  • stop-runs.mdx - How to stop runs
  • view-logged-runs.mdx - Viewing logged run data

Renamed File:

  • multiple-runs-per-process.mdx → initialize-run.mdx

Major Edits:

  • models/runs.mdx - Significantly reduced (597 lines removed) as content was split out
  • models/runs/grouping.mdx - Reorganized and updated
  • models/runs/forking.mdx - Expanded with more content
  • models/runs/filter-runs.mdx - Updates and improvements
  • Updated navigation in docs.json

Image Cleanup:

  • Removed 17 outdated images/GIFs
  • Added 6 new, updated images

@github-actions
Copy link
Contributor

Images automagically compressed by Calibre's image-actions

Compression reduced images by 78%, saving 926.9 KB.

Filename Before After Improvement Visual comparison
images/runs/unique-run-id.png 472.9 KB 103.7 KB 78.1% View diff
images/runs/group_job_type.png 384.5 KB 92.6 KB 75.9% View diff
images/runs/run_log_example_2.png 330.5 KB 64.7 KB 80.4% View diff

@github-actions
Copy link
Contributor

github-actions bot commented Dec 23, 2025

📚 Mintlify Preview Links

🔗 View Full Preview

🔄 Renamed/Moved (1 total)

📄 Pages (1)

Old Path → New Path Preview
models/runs/multiple-runs-per-process.mdx
models/runs/initialize-run.mdx
Initialize Run

✨ Added (13 total)

📄 Pages (7)

File Preview
models/runs/customize-run-display.mdx Customize Run Display
models/runs/delete-runs.mdx Delete Runs
models/runs/run-identifiers.mdx Run Identifiers
models/runs/run-states.mdx Run States
models/runs/search-runs.mdx Search Runs
models/runs/stop-runs.mdx Stop Runs
models/runs/view-logged-runs.mdx View Logged Runs
🖼️ Images (6)
File Preview
images/runs/group_job_type.png View Group Job Type
images/runs/group_name_3_groups.png View Group Name 3 Groups
images/runs/run_logs_info.png View Run Logs Info
images/runs/run_table_all.png View Run Table All
images/runs/runs_artifacts_info.png View Runs Artifacts Info
images/runs/runs_files_info.png View Runs Files Info

📝 Changed (26 total)

📄 Pages (23)

File Preview
ja/models/runs.mdx Runs
ja/models/runs/filter-runs.mdx Filter Runs
ja/models/runs/grouping.mdx Grouping
ja/models/runs/manage-runs.mdx Manage Runs
ja/models/track/project-page.mdx Project Page
ko/models/runs.mdx Runs
ko/models/runs/filter-runs.mdx Filter Runs
ko/models/runs/grouping.mdx Grouping
ko/models/runs/manage-runs.mdx Manage Runs
ko/models/track/project-page.mdx Project Page
... and 13 more files

🖼️ Images (2)

File Preview
images/runs/run_log_example_2.png View Run Log Example 2
images/runs/unique-run-id.png View Unique Run Id
⚙️ Other (1)
File
docs.json

🗑️ Deleted (18 total)

View deleted files

🖼️ Images (18)

File
images/app_ui/artifacts_tab.png
images/app_ui/demo_move_runs.gif
images/app_ui/export_to_csv.gif
images/app_ui/howto_move_runs.gif
images/app_ui/wandb-run-page-workspace-tab.png
images/app_ui/wandb_run_overview_page.png
images/app_ui/wandb_run_page_files_tab.png
images/app_ui/wandb_run_page_log_tab.png
images/data_vis/group.png
images/runs/demo-project.gif
... and 8 more images

🤖 Generated automatically when Mintlify deployment succeeds
📍 Deployment: d3164d4 at 2025-12-30 23:05:31 UTC

@github-actions
Copy link
Contributor

Images automagically compressed by Calibre's image-actions

Compression reduced images by 8.7%, saving 9.0 KB.

Filename Before After Improvement Visual comparison
images/runs/unique-run-id.png 103.7 KB 94.6 KB 8.7% View diff

2 images did not require optimisation.

@github-actions
Copy link
Contributor

Images automagically compressed by Calibre's image-actions

Compression reduced images by 79.5%, saving 241.1 KB.

Filename Before After Improvement Visual comparison
images/runs/group_name_3_groups.png 303.3 KB 62.2 KB 79.5% View diff

3 images did not require optimisation.

@github-actions
Copy link
Contributor

Images automagically compressed by Calibre's image-actions

Compression reduced images by 78.8%, saving 1.4 MB.

Filename Before After Improvement Visual comparison
images/runs/run_logs_info.png 623.5 KB 130.0 KB 79.1% View diff
images/runs/run_table_all.png 602.3 KB 144.1 KB 76.1% View diff
images/runs/runs_files_info.png 337.3 KB 62.7 KB 81.4% View diff
images/runs/runs_artifacts_info.png 276.5 KB 53.2 KB 80.8% View diff

4 images did not require optimisation.

@github-actions
Copy link
Contributor

Images automagically compressed by Calibre's image-actions

Compression reduced images by 7.6%, saving 24.8 KB.

Filename Before After Improvement Visual comparison
images/runs/run_table_all.png 144.1 KB 133.8 KB 7.2% View diff
images/runs/run_logs_info.png 130.0 KB 122.2 KB 6.0% View diff
images/runs/runs_artifacts_info.png 53.2 KB 46.5 KB 12.5% View diff

5 images did not require optimisation.

@ngrayluna ngrayluna marked this pull request as ready for review December 30, 2025 22:54
@ngrayluna ngrayluna requested a review from a team as a code owner December 30, 2025 22:54
@ngrayluna ngrayluna changed the title Runs: Update run overview page Runs: Rewrite Runs section Dec 30, 2025

### Run events
An automation can be triggered by a change in a [run's status](/models/#run-states) or a change in a [metric value](/models/track/log/#what-data-is-logged-with-specific-wb-api-calls).
An automation can be triggered by a change in a [run's status](/models/(/models/runs/run-states) or a change in a [metric value](/models/track/log/#what-data-is-logged-with-specific-wb-api-calls).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Munged URL? One more instance in this file.

@@ -0,0 +1,96 @@
---
title: View all runs a project
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
title: View all runs a project
title: View all runs a project
sidebarTitle: View all runs

I think it will improve the left nav to shorten some of these page nav titles.

@@ -0,0 +1,96 @@
---
title: View all runs a project
description: This section shows how to customize how runs are displayed in your project's runs table
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
description: This section shows how to customize how runs are displayed in your project's runs table
description: Details about customizing how runs are displayed in your project's runs table

A workspace is limited to displaying a maximum of 1000 runs, regardless of its configuration.
</Note> */}

View all runs logged to your W&B project in the **Runs** tab of your project sidebar. The *Runs table* shows details about all of your runs in a project. Use the Runs table to compare runs, sort runs by specific columns, and organize runs into groups.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To connect the dots, is it worth mentioning that the Runs Table is in the Runs Tab, and that the Runs Table and Workspace runs list share a config?

<img src="/images/runs/run_table_all.png" alt="Runs table" />
</Frame>

## Add columns
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These sections could be consolidated as H3s in a "Manage columns" section, all the way through Hide Columns. This would help the right-hand TOC.


To sort the list of runs by any visible column:
<Note>
W&B stores job types as a run [`wandb.Run.job_type`](/models/ref/python/experiments/run#property-run-job-type) property.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
W&B stores job types as a run [`wandb.Run.job_type`](/models/ref/python/experiments/run#property-run-job-type) property.
Specify the job type in the run's [`wandb.Run.job_type`](/models/ref/python/experiments/run#property-run-job-type) property.

Organize runs by their *job type*. A job type indicates the function of a run, such as `preprocessing`, `training`, or `evaluation`.

To sort the list of runs by any visible column:
<Note>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure this needs to be a note or if the sentence is necessary at all. It seems to be covered in line 102.

```

Suppose you set grouping in `wandb.init()`, we will group runs by default in the UI. You can toggle this on and off by clicking the **Group** button at the top of the table. Here's an [example project](https://wandb.ai/carey/group-demo?workspace=user-carey) generated from [sample code](https://wandb.me/grouping) where we set grouping. You can click on each "Group" row in the sidebar to get to a dedicated group page for that experiment.
The following image shows runs organized by the job type:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The following image shows runs organized by the job type:
The following image shows runs organized by job type:


1. In your project sidebar, select the **Runs** tab.
2. Above the list of runs, click the **Group** button.
3. From the dropdown, select either **Job Type**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
3. From the dropdown, select either **Job Type**.
3. From the dropdown, select **Job Type**.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stopped review after this file, for now.


If you group runs into experiments, refer to [Set a group in the UI](/models/runs/grouping/#set-a-group-in-the-ui).

## Move runs between your projects
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about section titles like "Move a run to a different project" and "Move a run to a different team"? I now you can move multiple runs at once, but I think you can't move multiple runs to different projects / teams at once, and the "between" is not the most important part because you probably moving only in one direction at a time. WDYT? Though as noted in my comment around line 22, I'm not sure this really needs to be presented as two different headings at all.

2. Select the **Runs** tab from the project sidebar.
3. Select the checkbox next to the runs you want to move.
4. Choose the **Move** button above the table.
4. Choose the **Move to project** button above the table.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
4. Choose the **Move to project** button above the table.
4. Click the **Move to project** button above the table.

Not sure about choosing a button.

</Frame>

## Move runs to a team
## Move runs between your teams
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unless I'm missing something, this is still moving a run to a new project, right? It just happens to be a project owned by a different team. This heading structure may give a reader the idea that you could move a run to a different team without moving it to a project owned by that team.

* **Artifact association**: W&B associates artifacts with the source run that produces them.
</Warning>

<Note>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To avoid note stacking, consider reworking this as a Requirements or Prerequisites section?

* You must use monotonically increasing steps. This does not work with non-monotonic steps defined with [`define_metric()`](/models/ref/python/experiments/run#define_metric) because it disrupts the required chronological order of run history and system metrics.
</Note>

Rewind a run to correct or modify the history of a run without losing the original data. In addition, when you
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd move this paragraph up to the very top, above the warning. Then the reader can see what the page is about before dealing with the private preview warning and the requirements.

description: Learn how to view a specific logged run and its properties using the W&B App or the LEET terminal UI.
---

View information about a specific run such as the state of the run, artifacts logged to the run, metrics logged to a run, system metrics, and more.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
View information about a specific run such as the state of the run, artifacts logged to the run, metrics logged to a run, system metrics, and more.
View information about a specific run, such as its current state, artifacts, metrics, and more.

https://wandb.ai/<team-name>/<project-name>/runs/<run-id>
```

Where values enclosed in angle brackets (`< >`) are placeholders for the actual values of the team name, project name, and [run ID](/models/runs/run-identifiers#run-id).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Where values enclosed in angle brackets (`< >`) are placeholders for the actual values of the team name, project name, and [run ID](/models/runs/run-identifiers#run-id).
Replace values enclosed in angle brackets (`< >`) with the actual values of the team name, project name, and [run ID](/models/runs/run-identifiers#run-id).


Where values enclosed in angle brackets (`< >`) are placeholders for the actual values of the team name, project name, and [run ID](/models/runs/run-identifiers#run-id).

After you select a run, explore its properties by navigating through the tabs: [Overview](/models/runs/view-logged-runs#overview), [Logs](/models/runs/view-logged-runs#logs), [Files](/models/runs/view-logged-runs#files), [Code](/models/runs/view-logged-runs#code), and [Artifacts](/models/runs/view-logged-runs#artifacts).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
After you select a run, explore its properties by navigating through the tabs: [Overview](/models/runs/view-logged-runs#overview), [Logs](/models/runs/view-logged-runs#logs), [Files](/models/runs/view-logged-runs#files), [Code](/models/runs/view-logged-runs#code), and [Artifacts](/models/runs/view-logged-runs#artifacts).
Explore the run's properties by navigating through the tabs: [Overview](/models/runs/view-logged-runs#overview), [Logs](/models/runs/view-logged-runs#logs), [Files](/models/runs/view-logged-runs#files), [Code](/models/runs/view-logged-runs#code), and [Artifacts](/models/runs/view-logged-runs#artifacts).

</Tabs>


### Overview
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure but I think that all of these H3s relate only to the W&B App tab above, not the LEET tab. Can you confirm?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now reviewed up to here.

Copy link
Contributor

@mdlinville mdlinville left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here's the rest of the first pass review. :)

A *run* is a single unit of computation logged by W&B. You can think of a W&B Run as an atomic element of your whole project. In other words, each run is a record of a specific computation, such as training a model and logging the results, hyperparameter sweeps, and so forth.

Common patterns for initiating a run include, but are not limited to:
Common reasons for initiating a run include, but are not limited to:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Common reasons for initiating a run include, but are not limited to:
Some common reasons for initiating a run include:

But this seems like kind of a weird way to talk about this.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you need a redirect for this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants