-Tags are user-defined, color-coded labels that can be added to experiments (and pipelines, datasets, and models),
-allowing to easily identify and group experiments. Tags can help in organizing, querying, and automating experiments.
-For example, tag experiments by the machine type used to execute them, label versions, team names, or any other
+Tags are user-defined, color-coded labels that can be added to tasks (and pipelines, datasets, and models),
+allowing to easily identify and group tasks. Tags can help in organizing, querying, and automating tasks.
+For example, tag tasks by the machine type used to execute them, label versions, team names, or any other
category.
-You can use tags to filter your experiments in your experiment table (see [Filtering Columns](webapp_exp_table.md#filtering-columns))
-or when querying experiments in your code (see [Tag Filters](../clearml_sdk/task_sdk.md#tag-filters)). You can trigger
-experiment execution according to their tags (see [TriggerScheduler](../references/sdk/trigger.md)) or automatically
+You can use tags to filter the tasks in your task table (see [Filtering Columns](webapp_exp_table.md#filtering-columns))
+or when querying tasks in your code (see [Tag Filters](../clearml_sdk/task_sdk.md#tag-filters)). You can trigger
+task execution according to their tags (see [TriggerScheduler](../references/sdk/trigger.md)) or automatically
deploy models according to their tags (see [ClearML Serving](../clearml_serving/clearml_serving_tutorial.md#automatic-model-deployment)).
**To add tags:**
-1. Click the experiment **>** Hover over the tag area **>** **+ADD TAG** or
(menu)
+1. Click the task **>** Hover over the tag area **>** **+ADD TAG** or
(menu)
1. Do one of the following:
* Add a new tag - Type the new tag name **>** **(Create New)**.
* Add an existing tag - Click a tag.
@@ -471,6 +480,6 @@ deploy models according to their tags (see [ClearML Serving](../clearml_serving/
-## Locating the Experiment (Task) ID
+## Locating the Task ID
-The task ID appears in the experiment page's header.
+The task ID appears in the task page's header.
-(**View in experiments table / full screen**), or clicking 
to
-hide details in the experiment table, so only the experiment names and statuses are displayed
+hide details in the task table, so only the task names and statuses are displayed
### Full Screen Details View
-The full screen details view allows for easier viewing and working with experiment tracking and results. The experiments
-table is not visible when the full screen details view is open. Perform experiment actions from the menu.
+The full screen details view allows for easier viewing and working with task tracking and results. The task
+table is not visible when the full screen details view is open. Perform task actions from the menu.
## Execution
-An experiment's **EXECUTION** tab of lists the following:
+A task's **EXECUTION** tab of lists the following:
* Source code
* Uncommitted changes
* Installed Python packages
@@ -59,8 +58,8 @@ In full-screen mode, the source code and output details are grouped in the **DET
### Source Code
-The Source Code section of an experiment's **EXECUTION** tab includes:
-* The experiment's repository
+The Source Code section of a task's **EXECUTION** tab includes:
+* The task's repository
* Commit ID
* Script path
* Working directory
@@ -70,7 +69,7 @@ The Source Code section of an experiment's **EXECUTION** tab includes:
### Uncommitted Changes
-ClearML displays the git diff of the experiment in the Uncommitted Changes section.
+ClearML displays the git diff of the task in the Uncommitted Changes section.
@@ -88,12 +87,12 @@ using to set up an environment (`pip` or `conda`) are available. Select which re
### Container
The Container section list the following information:
-* Image - a pre-configured Docker that ClearML Agent will use to remotely execute this experiment (see [Building Docker containers](../clearml_agent/clearml_agent_docker.md))
-* Arguments - add Docker arguments
-* Setup shell script - a bash script to be executed inside the Docker before setting up the experiment's environment
+* Image - a pre-configured container that ClearML Agent will use to remotely execute this task (see [Building Docker containers](../clearml_agent/clearml_agent_docker.md))
+* Arguments - add container arguments
+* Setup shell script - a bash script to be executed inside the container before setting up the task's environment
:::important
-To [rerun](webapp_exp_tuning.md) an experiment through the UI in the listed container, the ClearML Agent executing the experiment must be running in
+To [rerun](webapp_exp_tuning.md) a task through the UI in the listed container, the ClearML Agent executing the task must be running in
Docker mode:
```bash
@@ -119,7 +118,7 @@ All parameters and configuration objects appear in the **CONFIGURATION** tab.
### Hyperparameters
-Hyperparameters are grouped by their type and appear in **CONFIGURATION** **>** **HYPERPARAMETERS**. Once an experiment
+Hyperparameters are grouped by their type and appear in **CONFIGURATION** **>** **HYPERPARAMETERS**. Once a task
is run and stored in ClearML Server, any of these hyperparameters can be [modified](webapp_exp_tuning.md#modifying-experiments).
#### Command Line Arguments
@@ -157,14 +156,14 @@ The **TF_DEFINE** parameter group shows automatic TensorFlow logging.
### User Properties
-User properties allow to store any descriptive information in a key-value pair format. They are editable in any experiment,
-except experiments whose status is *Published* (read-only).
+User properties allow to store any descriptive information in a key-value pair format. They are editable in any task,
+except *Published* ones (read-only).
### Configuration Objects
-ClearML tracks experiment (Task) model configuration objects, which appear in **Configuration Objects** **>** **General**.
+ClearML tracks a task's model configuration objects, which appear in **Configuration Objects** **>** **General**.
These objects include those that are automatically tracked, and those connected to a Task in code (see [`Task.connect_configuration`](../references/sdk/task.md#connect_configuration)).
@@ -200,7 +199,7 @@ The task's input and output models appear in the **ARTIFACTS** tab. Each model e
* ID
* Configuration.
-Input models also display their creating experiment, which on-click navigates you to the experiment's page.
+Input models also display their creating task, which on-click navigates you to the task's page.
@@ -210,10 +209,10 @@ to navigate to its page in the **MODELS** tab (see [Model Details](webapp_model_
## Info
-The **INFO** tab shows extended experiment information:
-* [Latest experiment events log](#latest-events-log)
-* [Experiment description](#description)
-* [Experiment details](#experiment-details)
+The **INFO** tab shows extended task information:
+* [Latest task events log](#latest-events-log)
+* [Task description](#description)
+* [Task details](#task-details)
### Latest Events Log
@@ -237,19 +236,19 @@ ClearML maintains a system-wide, large but strict limit for task history items.
:::
### Description
-Add descriptive text to the experiment in the **Description** section. To modify the description, hover over the
+Add descriptive text to the task in the **Description** section. To modify the description, hover over the
description box and click **Edit**.
-### Experiment Details
-The **Experiment Details** section lists information describing the experiment:
+### Task Details
+The **Task Details** section lists information describing the task:
-* The parent experiment
+* The parent task
* Project name
* Creation, start, and last update dates and times
-* User who created the experiment
-* Experiment state (status)
-* Whether the experiment is archived
-* Runtime properties - Information about the machine running the experiment, including:
+* User who created the task
+* Task state (status)
+* Whether the task is archived
+* Runtime properties - Information about the machine running the task:
* Operating system
* CUDA driver version
* Number of CPU cores
@@ -259,21 +258,21 @@ The **Experiment Details** section lists information describing the experiment:
* Host name
* Processor
* Python version
-* Experiment Progress
+* Task Progress
-## Experiment Results
+## Task Results
:::tip Embedding ClearML Visualization
-You can embed experiment plots and debug samples into ClearML [Reports](webapp_reports.md). These visualizations are
-updated live as the experiment(s) updates. The Enterprise Plan and Hosted Service support embedding resources in external
+You can embed task plots and debug samples into ClearML [Reports](webapp_reports.md). These visualizations are
+updated live as the task(s) updates. The Enterprise Plan and Hosted Service support embedding resources in external
tools (e.g. Notion). See [Plot Controls](#plot-controls).
:::
### Console
-The complete experiment log containing everything printed to stdout and stderr appears in the **CONSOLE** tab. The full log
+The complete task log containing everything printed to stdout and stderr appears in the **CONSOLE** tab. The full log
is downloadable. To view the end of the log, click **Jump to end**.
@@ -289,7 +288,10 @@ Scalar series can be displayed in [graph view](#graph-view) (default) or in [met
#### Graph View
Scalar graph view (
)
-shows scalar series plotted as a time series line chart. The series are sub-sampled for
+shows scalar series plotted as a time series line chart. By default, a single plot is shown for each scalar metric,
+with all variants overlaid within.
+
+The series are sub-sampled for
display efficiency. For high resolution, view a series in full screen mode by hovering over the graph and clicking 
.
:::info Full Screen Refresh
@@ -304,26 +306,24 @@ a `Summary` table.
Use the scalar tools to improve analysis of scalar metrics. In the info panel, click 
to use the tools. In the full screen details view, the tools
are on the left side of the window. The tools include:
-* **Group by** - Select one of the following:
- * **Metric** - All variants for a metric on the same plot
- 
on each plot you want to view.
-To embed scalar plots in your [Reports](webapp_reports.md), hover over a plot and click 
,
-which will copy to clipboard the embed code to put in your Reports. In contrast to static screenshots, embedded resources
+To embed scalar plots in your [Reports](webapp_reports.md), hover over a plot and click Embed