Skip to main content

Experiments table

In the All runs tab, you can see all the runs of the project.

Each time you create a run with Run(), it's added to the top of the table.

The leftmost column shows:

  • Whether the run is visible in compare mode ()
  • The experiment name
  • A status indicator, if the run is active

Toggling experiment history​

You can toggle between showing all runs or just experiment runs:

  • All runs: Shows all runs created in the project.
  • Experiments: Shows only runs that currently represent an experiment.

All runs tab in the Neptune app with a highlighted button for switching between all runs and experiment runs.

For example, in a new project, if run seagull-1 is created as the first run of experiment seabird-flying-skills, the two toggle options show the same thing.

Then, if run seagull-2 is created and becomes the new representative of experiment seabird-flying-skills:

  • All runs: Shows both runs seagull-1 and seagull-2.
  • Experiments: Shows only run seagull-2.

Selecting runs for compare mode​

To visualize runs in compare tabs and reports, click their eye icons () in the table.

You can access more visualization options by clicking the eye icon () on the header row.

tip

To hide runs that are not selected for compare mode (), enable the Display only selected runs option.

Configuring columns​

Apart from filtering, you can customize the table columns to display the attributes you are interested in.

All runs tab in the Neptune app with highlighted column menu and a button for adding columns to the table.

Adding columns to the table​

Click Add column, then enter the attribute to add. The attribute path is the location of the piece of metadata in the run structure: run["attribute/path"].

Pinning columns​

Pinned columns keep the attributes visible as you switch between different tabs. They're also automatically included as columns in legends.

  1. If you haven't already, add the attribute of interest with the Add column button.

  2. On the column, click the icon and select Pin column.

    Alternatively, drag the column to the left of the separator line.

tip

You can have one set of pinned columns in one custom view, and a different set in another view.

Sorting and customization​

Click the dots menu () on a column to:

  • Access sorting options
  • Configure the column name, color, and numerical format
  • Group by the column
  • Pin the column
  • Remove the column

Sorting by last edited​

Modification timestamps are stored automatically in the sys namespace.

You can sort by the following:

  • sys/ping_time – when the Neptune API interacted with the object. That is, something was logged or modified through the code.
  • sys/modification_time – when any kind of edit was made, such as editing the run metadata through the app. This can be setting a description or managing the tags.

Custom views​

Once you're happy with your experiments table configuration, you can save the view for later. It'll be visible to any member of your project.

The following is retained in the saved view:

  • Column configuration
  • Query filters
  • Grouping

To save a custom view:

  1. Next to the search input box, click Save view as new.
  2. Give your new table view a name. You can change it later.

Now any project members can access the view and share it with a persistent link.

Grouping runs (groupBy)​

How to switch to group mode in the Neptune app.

To switch from List to Group mode, click Group.

By default, runs are grouped by group tag. You can group runs by other values, such as batch size or learning rate. For details, see Groups.

Searching and filtering runs​

Filter input box and selection menu for date and time

You can query runs by any attribute. By default, the search targets the experiment name (sys/name).

To switch to the query builder, click the Query button or use the keyboard shortcut: Ctrl + K

  • To change parts of a filter, you can click on the operator or value to change them without altering the rest.
  • To instantly filter by tag or owner, click on a value in the respective column.

Query syntax​

The syntax of a condition is:

  • <attribute> exists
  • <attribute> <operator> <one or (if applicable) more values>

You can build a query out of multiple conditions, in which case all of the conditions are applied (joined by AND).

Data and attribute typeOperatorsValue(s)Example
Numerical (Float or Integer)=, !=, >=, >, <=, <, exists, not existsinteger or floatf1 >= 0.95
Numerical series (FloatSeries) aggregates: average, variance, last value, max, or min=, !=, >=, >, <=, <integer or floattest/acc LAST < 0.6
Text (String)=, !=, contains, not contains, matches, not matches, exists, not existsstringsys/name = blobfish-candytuft
Ownerone of, not one ofuser or service account namesys/owner one of jackie, francis
Tags (StringSet)one of, not one of, all ofone or more tagssys/tags all of finetune, v2.0
Datetimeexists, not exists, before, after, last

Value for before/after: date and time

Values for last: day, week, month, quarter, or year

sys/creation_time last quarter
Boolean=, !=True or Falsesys/failed = True
Related