Skip to content

Commit fdd3774

Browse files
Merge pull request #276823 from ssalgadodev/patch-111
Update how-to-tune-hyperparameters.md
2 parents f609758 + 14b8eb8 commit fdd3774

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/machine-learning/v1/how-to-tune-hyperparameters.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: ssalgadodev
77
services: machine-learning
88
ms.service: machine-learning
99
ms.subservice: core
10-
ms.date: 05/02/2022
10+
ms.date: 05/30/2024
1111
ms.topic: how-to
1212
ms.custom: UpdateFrequency5
1313
---
@@ -202,7 +202,7 @@ Azure Machine Learning supports the following early termination policies:
202202

203203
### Bandit policy
204204

205-
[Bandit policy](/python/api/azureml-train-core/azureml.train.hyperdrive.banditpolicy#definition) is based on slack factor/slack amount and evaluation interval. Bandit ends runs when the primary metric isn't within the specified slack factor/slack amount of the most successful run.
205+
[Bandit policy](/python/api/azureml-train-core/azureml.train.hyperdrive.banditpolicy#definition) is based on slack factor/slack amount and evaluation interval. Bandit ends the runs when the primary metric isn't within the specified slack factor/slack amount of the most successful run.
206206

207207
> [!NOTE]
208208
> Bayesian sampling does not support early termination. When using Bayesian sampling, set `early_termination_policy = None`.
@@ -261,7 +261,7 @@ In this example, the early termination policy is applied at every interval start
261261

262262
### No termination policy (default)
263263

264-
If no policy is specified, the hyperparameter tuning service will let all training runs execute to completion.
264+
If no policy is specified, the hyperparameter tuning service lets all training runs execute to completion.
265265

266266
```Python
267267
policy=None
@@ -305,7 +305,7 @@ To [configure your hyperparameter tuning](/python/api/azureml-train-core/azureml
305305
* Resource allocation settings
306306
* ScriptRunConfig `script_run_config`
307307

308-
The ScriptRunConfig is the training script that will run with the sampled hyperparameters. It defines the resources per job (single or multi-node), and the compute target to use.
308+
The ScriptRunConfig is the training script that runs with the sampled hyperparameters. It defines the resources per job (single or multi-node), and the compute target to use.
309309

310310
> [!NOTE]
311311
>The compute target used in `script_run_config` must have enough resources to satisfy your concurrency level. For more information on ScriptRunConfig, see [Configure training runs](how-to-set-up-training-targets.md).
@@ -432,15 +432,15 @@ You can visualize all of your hyperparameter tuning runs in the [Azure Machine L
432432

433433
:::image type="content" source="../media/how-to-tune-hyperparameters/hyperparameter-tuning-metrics.png" alt-text="Hyperparameter tuning metrics chart":::
434434

435-
- **Parallel Coordinates Chart**: This visualization shows the correlation between primary metric performance and individual hyperparameter values. The chart is interactive via movement of axes (click and drag by the axis label), and by highlighting values across a single axis (click and drag vertically along a single axis to highlight a range of desired values). The parallel coordinates chart includes an axis on the right most portion of the chart that plots the best metric value corresponding to the hyperparameters set for that run instance. This axis is provided in order to project the chart gradient legend onto the data in a more readable fashion.
435+
- **Parallel Coordinates Chart**: This visualization shows the correlation between primary metric performance and individual hyperparameter values. The chart is interactive via movement of axes (select and drag by the axis label), and by highlighting values across a single axis (select and drag vertically along a single axis to highlight a range of desired values). The parallel coordinates chart includes an axis on the rightmost portion of the chart that plots the best metric value corresponding to the hyperparameters set for that run instance. This axis is provided in order to project the chart gradient legend onto the data in a more readable fashion.
436436

437437
:::image type="content" source="../media/how-to-tune-hyperparameters/hyperparameter-tuning-parallel-coordinates.png" alt-text="Hyperparameter tuning parallel coordinates chart":::
438438

439439
- **2-Dimensional Scatter Chart**: This visualization shows the correlation between any two individual hyperparameters along with their associated primary metric value.
440440

441441
:::image type="content" source="../media/how-to-tune-hyperparameters/hyperparameter-tuning-2-dimensional-scatter.png" alt-text="Hyparameter tuning 2-dimensional scatter chart":::
442442

443-
- **3-Dimensional Scatter Chart**: This visualization is the same as 2D but allows for three hyperparameter dimensions of correlation with the primary metric value. You can also click and drag to reorient the chart to view different correlations in 3D space.
443+
- **3-Dimensional Scatter Chart**: This visualization is the same as 2D but allows for three hyperparameter dimensions of correlation with the primary metric value. You can also select and drag to reorient the chart to view different correlations in 3D space.
444444

445445
:::image type="content" source="../media/how-to-tune-hyperparameters/hyperparameter-tuning-3-dimensional-scatter.png" alt-text="Hyparameter tuning 3-dimensional scatter chart":::
446446

0 commit comments

Comments
 (0)