Runs table

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

Each time you create a run with the Run() constructor from the API, 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

Show experiment history

You can switch between showing all runs or just experiment runs in the runs table:

• Experiments (default): Shows only runs that currently represent an experiment.
• Runs: Shows all runs created in the project.

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:

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

Configuring columns

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

Add columns to the table

To add a column to the runs table:

1. In the toolbar, select Controls.
2. Go to Table columns → Add/manage columns.
3. Select an attribute. The attribute path is the location of the piece of metadata in the run structure: run["attribute/path"].

Pin columns

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

There are two ways to pin a column:

• Open the column menu () and select Pin column.
• 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 runs 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. In the toolbar, select Controls → Save to new view.
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)

To switch from List to Group mode, in the toolbar, select Controls → 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

The search bar targets the experiment name (sys/name).

To add filters, click next to the search bar.

• 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 type	Operators	Value(s)	Example
Numerical (Float or Integer)	=, !=, >=, >, <=, <, exists, not exists	integer or float	f1 >= 0.95
Numerical series (FloatSeries) aggregates: average, variance, last value, max, or min	=, !=, >=, >, <=, <	integer or float	test/acc LAST < 0.6
Text (String)	=, !=, contains, not contains, matches, not matches, exists, not exists	string	sys/name = blobfish-candytuft
Owner	one of, not one of	user or service account name	sys/owner one of jackie, francis
Tags (StringSet)	one of, not one of, all of	one or more tags	sys/tags all of finetune, v2.0
Datetime	exists, 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 False	sys/failed = True

Related

• Manage tags
• Neptune Query Language
• Regular expressions

Archiving runs

See Archive runs.