Skip to content

Commit 9d288f7

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into update-faq
2 parents 059a7a7 + c689a88 commit 9d288f7

File tree

3 files changed

+54
-6
lines changed

3 files changed

+54
-6
lines changed

articles/machine-learning/how-to-auto-train-forecast.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ The [`AutoMLConfig`](https://docs.microsoft.com/python/api/azureml-train-automl-
124124

125125
See the [reference documentation](/python/api/azureml-train-automl-client/azureml.train.automl.automlconfig.automlconfig) for more information.
126126

127-
Create the time-series settings as a dictionary object. Set the `time_column_name` to the `day_datetime` field in the data set. Define the `grain_column_names` parameter to ensure that **two separate time-series groups** are created for the data; one for store A and B. Lastly, set the `max_horizon` to 50 in order to predict for the entire test set. Set a forecast window to 10 periods with `target_rolling_window_size`, and specify a single lag on the target values for two periods ahead with the `target_lags` parameter.
127+
Create the time-series settings as a dictionary object. Set the `time_column_name` to the `day_datetime` field in the data set. Define the `grain_column_names` parameter to ensure that **two separate time-series groups** are created for the data; one for store A and B. Lastly, set the `max_horizon` to 50 in order to predict for the entire test set. Set a forecast window to 10 periods with `target_rolling_window_size`, and specify a single lag on the target values for two periods ahead with the `target_lags` parameter. It is recommended to set `max_horizon`, `target_rolling_window_size` and `target_lags` to "auto" which will automatically detect these values for you. In the example below, "auto" settings have been used for these paramaters.
128128

129129
```python
130130
time_series_settings = {

articles/machine-learning/how-to-manage-runs.md

Lines changed: 45 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,14 +10,13 @@ ms.author: roastala
1010
author: rastala
1111
manager: cgronlun
1212
ms.reviewer: nibaccam
13-
ms.date: 11/04/2019
14-
13+
ms.date: 01/09/2020
1514
---
1615

1716
# Start, monitor, and cancel training runs in Python
1817
[!INCLUDE [applies-to-skus](../../includes/aml-applies-to-basic-enterprise-sku.md)]
1918

20-
The [Azure Machine Learning SDK for Python](https://docs.microsoft.com/python/api/overview/azure/ml/intro?view=azure-ml-py) and [Machine Learning CLI](reference-azure-machine-learning-cli.md) provide various methods to monitor, organize, and manage your runs for training and experimentation.
19+
The [Azure Machine Learning SDK for Python](https://docs.microsoft.com/python/api/overview/azure/ml/intro?view=azure-ml-py), [Machine Learning CLI](reference-azure-machine-learning-cli.md), and [Azure Machine Learning studio](https://ml.azure.com) provide various methods to monitor, organize, and manage your runs for training and experimentation.
2120

2221
This article shows examples of the following tasks:
2322

@@ -101,6 +100,16 @@ To start a run of your experiment, use the following steps:
101100

102101
For more information, see [az ml run submit-script](https://docs.microsoft.com/cli/azure/ext/azure-cli-ml/ml/run?view=azure-cli-latest#ext-azure-cli-ml-az-ml-run-submit-script).
103102

103+
### Using Azure Machine Learning studio
104+
105+
To start a submit a pipeline run in the designer (preview), use the following steps:
106+
107+
1. Set a default compute target for your pipeline.
108+
109+
1. Select **Run** at the top of the pipeline canvas.
110+
111+
1. Select an Experiment to group your pipeline runs.
112+
104113
## Monitor the status of a run
105114

106115
### Using the SDK
@@ -156,6 +165,22 @@ print(notebook_run.get_status())
156165

157166
For more information, see [az ml run show](https://docs.microsoft.com/cli/azure/ext/azure-cli-ml/ml/run?view=azure-cli-latest#ext-azure-cli-ml-az-ml-run-show).
158167

168+
169+
### Using Azure Machine Learning studio
170+
171+
To view the number of active runs for your experiment in the studio.
172+
173+
1. Navigate to the **Experiments** section..
174+
175+
1. Select an experiment.
176+
177+
In the experiment page, you can see the number of active compute targets and the duration for each run.
178+
179+
1. Select a specific run number.
180+
181+
1. In the **Logs** tab, you can find diagnostic and error logs for your pipeline run.
182+
183+
159184
## Cancel or fail runs
160185

161186
If you notice a mistake or if your run is taking too long to finish, you can cancel the run.
@@ -191,6 +216,17 @@ az ml run cancel -r runid -w workspace_name -e experiment_name
191216

192217
For more information, see [az ml run cancel](https://docs.microsoft.com/cli/azure/ext/azure-cli-ml/ml/run?view=azure-cli-latest#ext-azure-cli-ml-az-ml-run-cancel).
193218

219+
### Using Azure Machine Learning studio
220+
221+
To cancel a run in the studio, using the following steps:
222+
223+
1. Go to the running pipeline in either the **Experiments** or **Pipelines** section.
224+
225+
1. Select the pipeline run number you want to cancel.
226+
227+
1. In the toolbar, select **Cancel**
228+
229+
194230
## Create child runs
195231

196232
Create child runs to group together related runs, such as for different hyperparameter-tuning iterations.
@@ -333,6 +369,12 @@ az ml run list --experiment-name experiment [?properties.author=='azureml-user'
333369

334370
For more information on querying Azure CLI results, see [Query Azure CLI command output](https://docs.microsoft.com/cli/azure/query-azure-cli?view=azure-cli-latest).
335371

372+
### Using Azure Machine Learning studio
373+
374+
1. Navigate to the **Pipelines** section.
375+
376+
1. Use the search bar to filter pipelines using tags, descriptions, experiment names, and submitter name.
377+
336378
## Example notebooks
337379

338380
The following notebooks demonstrate the concepts in this article:

articles/media-services/video-indexer/release-notes.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.service: media-services
1111
ms.subservice: video-indexer
1212
ms.workload: na
1313
ms.topic: article
14-
ms.date: 01/07/2019
14+
ms.date: 01/07/2020
1515
ms.author: juliako
1616
---
1717

@@ -34,7 +34,13 @@ Update a specific section in the transcript using the [Update-Video-Index](https
3434

3535
### Fix account configuration from the Video Indexer portal
3636

37-
You can now update Media Services connection configuration in order to self-help with issues like: incorrect Azure Media Services resource. To fix the account configuration, in Video Indexer portal navigate to Settings > Account tab (as owner).
37+
You can now update Media Services connection configuration in order to self-help with issues like:
38+
39+
* incorrect Azure Media Services resource
40+
* password was changed
41+
* Media Services resources were moved between subscriptions
42+
43+
To fix the account configuration, in Video Indexer portal navigate to Settings > Account tab (as owner).
3844

3945
### Configure the custom vision account
4046

0 commit comments

Comments
 (0)