Polyaxon v3 is coming →

Save and reuse an experiment comparison

Save a Polyaxon comparison's query, columns, sorting and charts, reopen it for later runs, and share reusable searches and dashboards with your team.

October 30, 2026by Polyaxon

Once you have filtered your experiments, picked the useful columns and arranged the charts, save that comparison. You can reopen it when more runs finish, or make the same view available to teammates.

Polyaxon has two useful ways to do this: a saved search keeps the query and comparison settings, including charts; a saved dashboard keeps a reusable set of widgets. Both are part of the commercial offering. Version 2.14 expanded their visibility options and moved management into their selectors.

The screenshots below use the acme/demo project. Select an image to view it at full size.

Save the comparison

Open the project's runs page and configure the view you want to return to. For a classifier comparison, show the learning rate, batch size, final validation loss and best validation accuracy, then sort by validation accuracy. Add metric charts through Layout → Events if you also want to compare learning curves.

Use the query to define which runs belong in the comparison. For example, this query finds successful runs carrying the classifier tag:

status: succeeded, tags: classifier

The screenshots use a fixed uuid query for four demonstration runs. A tag-based query is useful for an ongoing review because later matching runs can appear when you reopen it. Selecting checkboxes alone does not save that selection of runs.

Click the save icon beside the search selector. Give the view a name, a description that explains its purpose, and any useful tags. The example below saves a variant called validation-comparison.

Save search dialog naming a new comparison validation-comparison, with a description, tags, New instance enabled and a Save button

When editing an existing saved search, enable New instance to keep it and save a separate version. Leave the switch off and choose Update to replace its saved configuration.

Reopen it for the next review

Open the search selector and choose a saved view. The list includes names, descriptions and tags; the example has validation-leaders selected.

Saved-search selector with validation-leaders selected above a classifier comparison table showing learning rate, batch size, validation loss and validation accuracy

Polyaxon restores the query, sorting, columns and saved chart configuration. The query runs against the available records, so a saved search can show updated results. It does not freeze the results at the time you saved it.

Recheck date filters when reopening a view: a shortcut such as Last week is saved as a concrete cutoff, rather than a window that moves forward automatically.

For the chart interactions themselves, see comparing runs across synchronized charts.

Make it available to your team

Open Manage saved queries at the bottom of the selector. The table shows each search's owner, description, tags and visibility. These example searches have Project visibility.

Manage saved queries table listing six saved searches, their owners and descriptions, Project visibility and per-row action menus

With the required permissions, open a row's action menu, choose Change Search visibility, select a scope and click Promote. All projects makes the search reusable across projects; Organization and all projects also makes it available in the organization-wide view. Keep reusable queries based on fields and tags that those projects actually use.

Sharing the configuration leaves project and run permissions in place. Teammates still need access to the data they want to compare.

Reuse just the charts

A saved dashboard is useful when several runs log the same metrics and you want the same charts on each run. In a run's Dashboards view, arrange the widgets and click the save icon beside the dashboard selector.

The dialog below shows an existing dashboard being edited: New instance is off, so the action is Update. Enable New instance to save a separate dashboard instead. For a new run dashboard, choose All runs in this project when you want to reuse it on other runs.

Save dashboard dialog with the name validation-metrics, a description and tags, New instance disabled and the Update button

On another run, open the dashboard selector and choose the saved layout. Its widgets use that run's data, so keep metric names consistent. The screenshot below shows the training-metrics layout selected on a single run.

Saved-dashboard selector with training-metrics selected on a run, displaying validation ROC and precision-recall curves, final metrics and accuracy history

For an existing dashboard limited to one run, open Manage dashboards and change its visibility to All runs under this project. The same menu can make a suitable layout available across projects.

Manage dashboards table listing five saved dashboards, their owners, descriptions, tags, Entity visibility and per-row action menus

See saved dashboards and saved searches for the reference workflows.