diff --git a/docs/clearml_sdk/task_sdk.md b/docs/clearml_sdk/task_sdk.md index 2b36b27b..92041405 100644 --- a/docs/clearml_sdk/task_sdk.md +++ b/docs/clearml_sdk/task_sdk.md @@ -151,7 +151,7 @@ Pass one of the following in the `continue_last_task` parameter: [Task Reuse](#task-reuse)). * `True` - Continue the previously run Task. * Task ID (string) - The ID of the task to be continued. -* Initial iteration offset (Integer) - Specify the initial iteration offset. By default, the task will continue one +* Initial iteration offset (integer) - Specify the initial iteration offset. By default, the task will continue one iteration after the last reported one. Pass `0`, to disable the automatic last iteration offset. To also specify a task ID, use the `reuse_last_task_id` parameter . diff --git a/docs/configs/clearml_conf.md b/docs/configs/clearml_conf.md index 0ccec108..22242dd9 100644 --- a/docs/configs/clearml_conf.md +++ b/docs/configs/clearml_conf.md @@ -434,7 +434,7 @@ match_rules: [ **`agent.package_manager.conda_env_as_base_docker`** (*bool*) -* Uses conda environment for execution (Like a docker) +* Uses conda environment for execution (like a docker) ___ diff --git a/docs/getting_started/ds/best_practices.md b/docs/getting_started/ds/best_practices.md index 39ddece8..4ff0b2e6 100644 --- a/docs/getting_started/ds/best_practices.md +++ b/docs/getting_started/ds/best_practices.md @@ -46,7 +46,7 @@ that we need. - [ClearML SDK](../../clearml_sdk/clearml_sdk.md) ensures that all the metrics, parameters and Models are automatically logged and can later be accessed, [compared](../../webapp/webapp_exp_comparing.md) and [tracked](../../webapp/webapp_exp_track_visual.md). - [ClearML Agent](../../clearml_agent.md) does the heavy lifting. It reproduces the execution environment, clones your code, - applies code patches, manages parameters (Including overriding them on the fly), executes the code and queues multiple tasks + applies code patches, manages parameters (including overriding them on the fly), executes the code and queues multiple tasks It can even [build](../../clearml_agent.md#exporting-a-task-into-a-standalone-docker-container) the docker container for you! - [ClearML Pipelines](../../pipelines/pipelines.md) ensure that steps run in the same order, programmatically chaining tasks together, while giving an overview of the execution pipeline's status. diff --git a/docs/guides/ide/google_colab.md b/docs/guides/ide/google_colab.md index 0b2e1854..a7fc8d6d 100644 --- a/docs/guides/ide/google_colab.md +++ b/docs/guides/ide/google_colab.md @@ -11,7 +11,7 @@ This tutorial goes over how to create a ClearML worker node in a Google Colab no and running, users can send Tasks to be executed on Google Colab's HW. ## Prerequisites -* Be signed up for ClearML (Or have a server deployed). +* Be signed up for ClearML (or have a server deployed). * Have a Google account to access Google Colab diff --git a/docs/img/examples_keras_03.png b/docs/img/examples_keras_03.png deleted file mode 100644 index 0e78c228..00000000 Binary files a/docs/img/examples_keras_03.png and /dev/null differ diff --git a/docs/img/examples_reporting_config.png b/docs/img/examples_reporting_config.png deleted file mode 100644 index 4c68b666..00000000 Binary files a/docs/img/examples_reporting_config.png and /dev/null differ diff --git a/docs/img/examples_reporting_config_2.png b/docs/img/examples_reporting_config_2.png deleted file mode 100644 index 6a727318..00000000 Binary files a/docs/img/examples_reporting_config_2.png and /dev/null differ diff --git a/docs/img/examples_reporting_config_3.png b/docs/img/examples_reporting_config_3.png deleted file mode 100644 index 2b495f6c..00000000 Binary files a/docs/img/examples_reporting_config_3.png and /dev/null differ diff --git a/docs/img/fundamentals_hyperparameters_config_objects.png b/docs/img/fundamentals_hyperparameters_config_objects.png deleted file mode 100644 index 893b125e..00000000 Binary files a/docs/img/fundamentals_hyperparameters_config_objects.png and /dev/null differ diff --git a/docs/img/plotly/zoombox.svg b/docs/img/plotly/zoombox.svg deleted file mode 100644 index 2e6c1f25..00000000 --- a/docs/img/plotly/zoombox.svg +++ /dev/null @@ -1 +0,0 @@ - diff --git a/docs/img/settings_user_management_table.png b/docs/img/settings_user_management_table.png index eddc5ce1..7e935d93 100644 Binary files a/docs/img/settings_user_management_table.png and b/docs/img/settings_user_management_table.png differ diff --git a/docs/img/webapp-common/filter-off.svg b/docs/img/webapp-common/filter-off.svg deleted file mode 100644 index b03147f2..00000000 --- a/docs/img/webapp-common/filter-off.svg +++ /dev/null @@ -1,14 +0,0 @@ - - - - background - - - - Layer 1 - - - - - - \ No newline at end of file diff --git a/docs/img/webapp-common/plus-blue.svg b/docs/img/webapp-common/plus-blue.svg deleted file mode 100644 index 7d48cb7a..00000000 --- a/docs/img/webapp-common/plus-blue.svg +++ /dev/null @@ -1,3 +0,0 @@ - - - diff --git a/docs/img/webapp-common/queues.svg b/docs/img/webapp-common/queues.svg deleted file mode 100644 index 3e277b2e..00000000 --- a/docs/img/webapp-common/queues.svg +++ /dev/null @@ -1,10 +0,0 @@ - - - - - - - - - - diff --git a/docs/img/webapp-common/settings_gear.svg b/docs/img/webapp-common/settings_gear.svg deleted file mode 100644 index 332517bc..00000000 --- a/docs/img/webapp-common/settings_gear.svg +++ /dev/null @@ -1,11 +0,0 @@ - - - - - - diff --git a/docs/img/webapp-common/side-nav/annotator.svg b/docs/img/webapp-common/side-nav/annotator.svg deleted file mode 100644 index 759e9798..00000000 --- a/docs/img/webapp-common/side-nav/annotator.svg +++ /dev/null @@ -1,36 +0,0 @@ - - - - - - - - - - - - - - - - - sidebar-annotator-icon - - - - - - - - - - - - - - - - diff --git a/docs/img/webapp-common/side-nav/datasets.svg b/docs/img/webapp-common/side-nav/datasets.svg deleted file mode 100644 index ae4265ca..00000000 --- a/docs/img/webapp-common/side-nav/datasets.svg +++ /dev/null @@ -1,10 +0,0 @@ - - - - - sidebar-data-icon - - - diff --git a/docs/img/webapp-common/side-nav/home.svg b/docs/img/webapp-common/side-nav/home.svg deleted file mode 100644 index b7265b99..00000000 --- a/docs/img/webapp-common/side-nav/home.svg +++ /dev/null @@ -1,7 +0,0 @@ - - - - - sidebar-home-icon - - diff --git a/docs/img/webapp-common/side-nav/projects.svg b/docs/img/webapp-common/side-nav/projects.svg deleted file mode 100644 index c2c2c8e5..00000000 --- a/docs/img/webapp-common/side-nav/projects.svg +++ /dev/null @@ -1,10 +0,0 @@ - - - - - sidebar-projects-icon - - - diff --git a/docs/img/webapp-common/side-nav/queues.svg b/docs/img/webapp-common/side-nav/queues.svg deleted file mode 100644 index 2cd8c411..00000000 --- a/docs/img/webapp-common/side-nav/queues.svg +++ /dev/null @@ -1,8 +0,0 @@ - - - - - sidebar-workers-icon - - diff --git a/docs/img/webapp_dataview_table_batch_operations.png b/docs/img/webapp_dataview_table_batch_operations.png deleted file mode 100644 index 5987756a..00000000 Binary files a/docs/img/webapp_dataview_table_batch_operations.png and /dev/null differ diff --git a/docs/img/webapp_module_icons.png b/docs/img/webapp_module_icons.png deleted file mode 100644 index 26896dbf..00000000 Binary files a/docs/img/webapp_module_icons.png and /dev/null differ diff --git a/docs/img/webapp_projects_card.png b/docs/img/webapp_projects_card.png deleted file mode 100644 index 5298de91..00000000 Binary files a/docs/img/webapp_projects_card.png and /dev/null differ diff --git a/docs/img/webapp_projects_inside.png b/docs/img/webapp_projects_inside.png deleted file mode 100644 index c56820ed..00000000 Binary files a/docs/img/webapp_projects_inside.png and /dev/null differ diff --git a/docs/img/webapp_setting_usage.png b/docs/img/webapp_setting_usage.png deleted file mode 100644 index 22ace3ee..00000000 Binary files a/docs/img/webapp_setting_usage.png and /dev/null differ diff --git a/docs/img/webapp_settings_workspace_conf.png b/docs/img/webapp_settings_workspace_conf.png deleted file mode 100644 index 01732415..00000000 Binary files a/docs/img/webapp_settings_workspace_conf.png and /dev/null differ diff --git a/docs/pipelines/pipelines_sdk_function_decorators.md b/docs/pipelines/pipelines_sdk_function_decorators.md index 60c55ae0..8aafb2d8 100644 --- a/docs/pipelines/pipelines_sdk_function_decorators.md +++ b/docs/pipelines/pipelines_sdk_function_decorators.md @@ -87,7 +87,7 @@ def step_one(pickle_data_url: str, extra: int = 43): ### Arguments * `return_values` - The artifact names for the step’s corresponding ClearML task to store the step’s returned objects. In the example above, a single object is returned and stored as an artifact named `data_frame` -* `name` (Optional) - The name for the pipeline step. If not provided, the function name is used +* `name` (optional) - The name for the pipeline step. If not provided, the function name is used * `cache` - If `True`, the pipeline controller checks if a step with the same code (including setup, see task [Execution](../webapp/webapp_exp_track_visual.md#execution) section) and input arguments was already executed. If found, the cached step's outputs are used instead of rerunning the step. @@ -101,8 +101,8 @@ def step_one(pickle_data_url: str, extra: int = 43): * `docker` - Specify the Docker image to be used when executing the pipeline step remotely * `docker_args` - Add Docker execution arguments for the remote execution (use single string for all docker arguments). * `docker_bash_setup_script` - Add a bash script to be executed inside the docker before setting up the Task's environment -* `task_type` (Optional) - The [task type](../fundamentals/task.md#task-types) to be created -* `repo` (Optional) - Specify a repository to attach to the function when remotely executing. Allow users to execute the function inside the specified repository, enabling them to load modules / script from the repository. Notice the execution work directory will be the repository root folder. Supports both git repo url link, and local repository path (automatically converted into the remote git / commit as is currently checkout). +* `task_type` (optional) - The [task type](../fundamentals/task.md#task-types) to be created +* `repo` (optional) - Specify a repository to attach to the function when remotely executing. Allow users to execute the function inside the specified repository, enabling them to load modules / script from the repository. Notice the execution work directory will be the repository root folder. Supports both git repo url link, and local repository path (automatically converted into the remote git / commit as is currently checkout). * Examples: * remote url: `"https://github.com/user/repo.git"` * local repo copy: `"./repo"` -> will automatically store the remote repo url and commit ID based on the locally cloned copy diff --git a/docs/pipelines/pipelines_sdk_tasks.md b/docs/pipelines/pipelines_sdk_tasks.md index 47bba11c..20d5b614 100644 --- a/docs/pipelines/pipelines_sdk_tasks.md +++ b/docs/pipelines/pipelines_sdk_tasks.md @@ -94,7 +94,7 @@ pipe.add_step( * `cache_executed_step` – If `True`, the controller will check if an identical task with the same code (including setup, e.g. required packages, docker image, etc.) and input arguments was already executed. If found, the cached step's outputs are used instead of launching a new task. -* `execution_queue` (Optional) - the queue to use for executing this specific step. If not provided, the task will be sent to the default execution queue, as defined on the class +* `execution_queue` (optional) - the queue to use for executing this specific step. If not provided, the task will be sent to the default execution queue, as defined on the class * `parents` – Optional list of parent steps in the pipeline. The current step in the pipeline will be sent for execution only after all the parent steps have been executed successfully. * `parameter_override` - Dictionary of parameters and values to override in the current step. See [parameter_override](#parameter_override). * `configuration_overrides` - Dictionary of configuration objects and values to override in the current step. See [configuration_overrides](#configuration_overrides) @@ -209,19 +209,19 @@ def step_completed_callback( You can enable automatic logging of a step’s metrics /artifacts / models to the pipeline task using the following arguments: -* `monitor_metrics` (Optional) - Automatically log the step's reported metrics also on the pipeline Task. The expected +* `monitor_metrics` (optional) - Automatically log the step's reported metrics also on the pipeline Task. The expected format is one of the following: * List of pairs metric (title, series) to log: [(step_metric_title, step_metric_series), ]. Example: `[('test', 'accuracy'), ]` * List of tuple pairs, to specify a different target metric to use on the pipeline Task: [((step_metric_title, step_metric_series), (target_metric_title, target_metric_series)), ]. Example: `[[('test', 'accuracy'), ('model', 'accuracy')], ]` -* `monitor_artifacts` (Optional) - Automatically log the step's artifacts on the pipeline Task. +* `monitor_artifacts` (optional) - Automatically log the step's artifacts on the pipeline Task. * Provided a list of artifact names created by the step function, these artifacts will be logged automatically also on the Pipeline Task itself. Example: `['processed_data', ]` (target artifact name on the Pipeline Task will have the same name as the original artifact). * Alternatively, provide a list of pairs (source_artifact_name, target_artifact_name), where the first string is the artifact name as it appears on the step Task, and the second is the target artifact name to put on the Pipeline Task. Example: `[('processed_data', 'final_processed_data'), ]` -* `monitor_models` (Optional) - Automatically log the step's output models on the pipeline Task. +* `monitor_models` (optional) - Automatically log the step's output models on the pipeline Task. * Provided a list of model names created by the step's Task, they will also appear on the Pipeline itself. Example: `['model_weights', ]` * To select the latest (lexicographic) model, use `model_*`, or the last created model with just `*`. Example: `['model_weights_*', ]` * Alternatively, provide a list of pairs (source_model_name, target_model_name), where the first string is the model diff --git a/docs/webapp/applications/apps_aws_autoscaler.md b/docs/webapp/applications/apps_aws_autoscaler.md index 7c0c47ab..44f94a3b 100644 --- a/docs/webapp/applications/apps_aws_autoscaler.md +++ b/docs/webapp/applications/apps_aws_autoscaler.md @@ -31,11 +31,11 @@ each instance is spun up. repositories to retrieve the code for their jobs * Git User * Git Password / Personal Access Token -* **Max Idle Time** (Optional) - Maximum time in minutes that an EC2 instance can be idle before the autoscaler spins it +* **Max Idle Time** (optional) - Maximum time in minutes that an EC2 instance can be idle before the autoscaler spins it down -* **Workers Prefix** (Optional) - A Prefix added to workers’ names, associating them with this autoscaler -* **Polling Interval** (Optional) - Time period in minutes at which the designated queue is polled for new tasks -* **Base Docker Image** (Optional) - Default Docker image in which the ClearML Agent will run. Provide a Docker stored +* **Workers Prefix** (optional) - A Prefix added to workers’ names, associating them with this autoscaler +* **Polling Interval** (optional) - Time period in minutes at which the designated queue is polled for new tasks +* **Base Docker Image** (optional) - Default Docker image in which the ClearML Agent will run. Provide a Docker stored in a Docker artifactory so instances can automatically fetch it * **Compute Resources** * Resource Name - Assign a name to the resource type. This name will appear in the Autoscaler dashboard @@ -49,24 +49,24 @@ each instance is spun up. * Max Number of Instances - Maximum number of concurrent running instances of this type allowed * Monitored Queue - Queue associated with this instance type. The tasks enqueued to this queue will be executed on instances of this type - * EC2 Tags (Optional) - AWS instance tags to attach to launched EC2 instances. Insert key=value pairs, separated by + * EC2 Tags (optional) - AWS instance tags to attach to launched EC2 instances. Insert key=value pairs, separated by commas - * EBS Device (Optional) - Disk mount point - * EBS Volume Size (Optional) - Disk size (GB) - * EBS Volume Type (Optional) - See [here](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volume-types.html) + * EBS Device (optional) - Disk mount point + * EBS Volume Size (optional) - Disk size (GB) + * EBS Volume Type (optional) - See [here](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volume-types.html) for full list of types - * Instance Key Pair (Optional) - AWS key pair that is provided to the spun EC2 instances for connecting to them via + * Instance Key Pair (optional) - AWS key pair that is provided to the spun EC2 instances for connecting to them via SSH. Provide the Key Pair's name, as was created in AWS. See [here](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html) for more details - * Security Group ID (Optional) - Comma separated list of AWS VPC Security Group IDs to attach to the launched + * Security Group ID (optional) - Comma separated list of AWS VPC Security Group IDs to attach to the launched instance. Read more [here](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html) * \+ Add Item - Define another resource type -* **IAM Instance Profile** (Optional) - Set an IAM instance profile for all instances spun by the Autoscaler +* **IAM Instance Profile** (optional) - Set an IAM instance profile for all instances spun by the Autoscaler * Arn - Amazon Resource Name specifying the instance profile * Name - Name identifying the instance profile -* **Autoscaler Instance Name** (Optional) - Name for the Autoscaler instance. This will appear in the instance list -* **Init script** (Optional) - A bash script to execute after launching the EC2 instance -* **Additional ClearML Configuration** (Optional) - A ClearML configuration file to use by the ClearML Agent when +* **Autoscaler Instance Name** (optional) - Name for the Autoscaler instance. This will appear in the instance list +* **Init script** (optional) - A bash script to execute after launching the EC2 instance +* **Additional ClearML Configuration** (optional) - A ClearML configuration file to use by the ClearML Agent when executing your experiments * **Export Configuration** - Export the app instance configuration as a JSON file, which you can later import to create a new instance with the same configuration diff --git a/docs/webapp/applications/apps_dashboard.md b/docs/webapp/applications/apps_dashboard.md index d6b1b970..f65c14ec 100644 --- a/docs/webapp/applications/apps_dashboard.md +++ b/docs/webapp/applications/apps_dashboard.md @@ -19,7 +19,7 @@ on failed Tasks via Slack integration. * Monitored Metric - Series - Metric series (variant) to track * Monitored Metric - Trend - Choose whether to track the monitored metric's highest or lowest values * **Dashboard Title** - Name of the project dashboard instance, which will appear in the instance list -* **Failed Task Slack Monitor** (Optional) +* **Failed Task Slack Monitor** (optional) * API Token - Slack workspace access token * Channel Name - Slack channel to which task failure alerts will be posted * Fail Iteration Threshold - Minimum number of iterations to trigger Slack alerts about task failure (failed tasks that do not meet the threshold will be ignored) diff --git a/docs/webapp/applications/apps_gcp_autoscaler.md b/docs/webapp/applications/apps_gcp_autoscaler.md index 72a48851..b52e6e9c 100644 --- a/docs/webapp/applications/apps_gcp_autoscaler.md +++ b/docs/webapp/applications/apps_gcp_autoscaler.md @@ -30,7 +30,7 @@ when each VM instance is spun up. repositories to retrieve the code for their jobs * Git User * Git Password / Personal Access Token -* **Base Docker Image** (Optional) - Default Docker image in which the ClearML Agent will run. Provide a Docker stored in a +* **Base Docker Image** (optional) - Default Docker image in which the ClearML Agent will run. Provide a Docker stored in a Docker artifactory so VM instances can automatically fetch it * **Compute Resources** * Resource Name - Assign a name to the resource type. This name will appear in the Autoscaler dashboard @@ -40,15 +40,15 @@ when each VM instance is spun up. * Use Preemptible Instance - Choose whether VM instances of this type will be [preemptible](https://cloud.google.com/compute/docs/instances/preemptible) * Max Number of Instances - Maximum number of concurrent running VM instances of this type allowed * Monitored Queue - Queue associated with this VM instance type. The tasks enqueued to this queue will be executed on VM instances of this type - * Machine Image (Optional) - The GCP machine image to launch - * Disc Size (in GB) (Optional) + * Machine Image (optional) - The GCP machine image to launch + * Disc Size (in GB) (optional) * \+ Add Item - Define another resource type -* **Autoscaler Instance Name** (Optional) - Name for the Autoscaler instance. This will appear in the instance list -* **Max Idle Time** (Optional) - Maximum time in minutes that a VM instance can be idle before the autoscaler spins it down -* **Workers Prefix** (Optional) - A Prefix added to workers’ names, associating them with this autoscaler -* **Polling Interval** (Optional) - Time period in minutes at which the designated queue is polled for new tasks -* **Init Script** (Optional) - A bash script to execute after launching the VM instance -* **Additional ClearML Configuration** (Optional) - A ClearML configuration file to use by the ClearML Agent when executing your experiments +* **Autoscaler Instance Name** (optional) - Name for the Autoscaler instance. This will appear in the instance list +* **Max Idle Time** (optional) - Maximum time in minutes that a VM instance can be idle before the autoscaler spins it down +* **Workers Prefix** (optional) - A Prefix added to workers’ names, associating them with this autoscaler +* **Polling Interval** (optional) - Time period in minutes at which the designated queue is polled for new tasks +* **Init Script** (optional) - A bash script to execute after launching the VM instance +* **Additional ClearML Configuration** (optional) - A ClearML configuration file to use by the ClearML Agent when executing your experiments * **Export Configuration** - Export the app instance configuration as a JSON file, which you can later import to create a new instance with the same configuration. diff --git a/docs/webapp/applications/apps_gpu_compute.md b/docs/webapp/applications/apps_gpu_compute.md index 1bd6a28b..438b94d1 100644 --- a/docs/webapp/applications/apps_gpu_compute.md +++ b/docs/webapp/applications/apps_gpu_compute.md @@ -27,13 +27,13 @@ queue. The app instance automatically terminates idle machines based on a specif * Monitored Queue - Queue associated with application instance. The tasks enqueued to this queue will be executed on machines of this specification * Cloud Machine Limit - Maximum number of concurrent machines to launch -* **Idle Time Limit** (Optional) - Maximum time in minutes that a cloud machine can be idle before it is spun down -* **Default Docker Image** (Optional) - Default Docker image in which the ClearML Agent will run. Provide a Docker stored +* **Idle Time Limit** (optional) - Maximum time in minutes that a cloud machine can be idle before it is spun down +* **Default Docker Image** (optional) - Default Docker image in which the ClearML Agent will run. Provide a Docker stored in a Docker artifactory so instances can automatically fetch it * **Git Configuration** - Git credentials with which the ClearML Agents running on your cloud instances will access your repositories to retrieve the code for their jobs * Git User * Git Password / Personal Access Token -* **Cloud Storage Access** (Optional) - Access credentials to cloud storage service. Provides ClearML Tasks running on cloud +* **Cloud Storage Access** (optional) - Access credentials to cloud storage service. Provides ClearML Tasks running on cloud machines access to your storage ![GPU Compute wizard](../../img/apps_gpu_compute_wizard.png) diff --git a/docs/webapp/applications/apps_hpo.md b/docs/webapp/applications/apps_hpo.md index 2f823a8d..4617e025 100644 --- a/docs/webapp/applications/apps_hpo.md +++ b/docs/webapp/applications/apps_hpo.md @@ -54,11 +54,11 @@ limits. Additionally, make sure that the initial experiment's `_allow_omegaconf_edit_` parameter is set to `False` (in experiment's **CONFIGURATION > HYPERPARAMETERS > Hydra**). ::: -* **Optimization Job Title** (Optional) - Name for the HPO instance. This will appear in the instance list -* **Optimization Experiments Destination Project** (Optional) - The project where optimization tasks will be saved. +* **Optimization Job Title** (optional) - Name for the HPO instance. This will appear in the instance list +* **Optimization Experiments Destination Project** (optional) - The project where optimization tasks will be saved. Leave empty to use the same project as the Initial task. * **Maximum Concurrent Tasks** - The maximum number of simultaneously running optimization experiments -* **Advanced Configuration** (Optional) +* **Advanced Configuration** (optional) * Limit Total HPO Experiments - Maximum total number of optimization experiments * Number of Top Experiments to Save - Number of best performing experiments to save (the rest are archived) * Limit Single Experiment Running Time (Minutes) - Time limit per optimization experiment. Experiments will be diff --git a/docs/webapp/webapp_exp_comparing.md b/docs/webapp/webapp_exp_comparing.md index 5379a70c..8560c2b7 100644 --- a/docs/webapp/webapp_exp_comparing.md +++ b/docs/webapp/webapp_exp_comparing.md @@ -45,7 +45,7 @@ The **DETAILS** tab includes deep comparisons of the following: **To Locate the Source Differences:** Click the **DETAILS** tab **>** Expand highlighted sections, or, in the header, click Up arrow -(Previous diff) or Down arrow (Next diff). +(previous diff) or Down arrow (next diff). For example, in the image below, expanding **ARTIFACTS** **>** **Output Model** **>** **Model** shows that the model names are different. @@ -68,8 +68,8 @@ The Values mode is a side-by-side comparison that shows hyperparameter value dif 1. In the dropdown menu (on the upper left, next to **+ Add Experiments**), choose **Values**. 1. To show only differences, move the **Hide Identical Fields** slider to on. 1. Locate differences by either: - * Clicking Up arrow (Previous diff) or - Down arrow (Next diff). + * Clicking Up arrow (previous diff) or + Down arrow (next diff). * Scrolling to see highlighted hyperparameters. For example, expanding **General** shows that the `batch_size` and `epochs` differ between the experiments. @@ -190,8 +190,8 @@ first. Use the viewer / player to inspect images, audio, video samples and do an 1. Locate debug samples by doing the following: * Filter by metric. In the **Metric** list, choose a metric. - * Show other iterations. Click Left arrow (Older images), - Right arrow (New images), or right arrow, newest image (Newest images). + * Show other iterations. Click Left arrow (older images), + Right arrow (new images), or right arrow, newest image (newest images). * Click Sync selection in order to synchronize iteration and metric selection across experiments. For example, if you select a metric for one experiment’s debug samples, the same metric will be automatically selected for the rest of the experiments in the comparison.