Skip to content

Commit 36fa06d

Browse files
committed
fix blocking issues
1 parent 7533249 commit 36fa06d

5 files changed

+13
-13
lines changed

articles/machine-learning/tutorial-1st-experiment-hello-world.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -148,7 +148,7 @@ Here's a description of how the control script works:
148148
`ml_client = MLClient(DefaultAzureCredential(), subscription_id, resource_group, workspace)`
149149
:::column-end:::
150150
:::column span="2":::
151-
[MLClient](/python/api/azure-ai-ml/azure.ai.ml.mlclient) manages your Azure Machine Learning workspace and it's assets and resources.
151+
[MLClient](/python/api/azure-ai-ml/azure.ai.ml.mlclient) manages your Azure Machine Learning workspace and its assets and resources.
152152
:::column-end:::
153153
:::row-end:::
154154
:::row:::

articles/machine-learning/tutorial-1st-experiment-sdk-train.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -255,7 +255,7 @@ if __name__ == "__main__":
255255

256256
### View the output
257257

258-
1. In the page that opens, you'll see the job status. The first time you run this script, Azure Machine Learning will build a new Docker image from your PyTorch environment. The whole job might around 10 minutes to complete. This image will be reused in future jobs to make them job much quicker.
258+
1. In the page that opens, you'll see the job status. The first time you run this script, Azure Machine Learning will build a new Docker image from your PyTorch environment. The whole job might take around 10 minutes to complete. This image will be reused in future jobs to make them job much quicker.
259259
1. You can see view Docker build logs in the Azure Machine Learning studio. Select the **Outputs + logs** tab, and then select **20_image_build_log.txt**.
260260
1. When the status of the job is **Completed**, select **Output + logs**.
261261
1. Select **std_log.txt** to view the output of your job.

articles/machine-learning/v1/tutorial-1st-experiment-bring-data.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -204,7 +204,7 @@ To run this script in Azure Machine Learning, you need to make your training dat
204204
Uploaded 9 files
205205
```
206206

207-
## <a name="control-script"></a> Create a control script
207+
## Create a control script
208208

209209
As you've done previously, create a new Python control script called *run-pytorch-data.py* in the **get-started** folder:
210210

@@ -271,7 +271,7 @@ The control script is similar to the one from [part 3 of this series](tutorial-1
271271
:::column-end:::
272272
:::row-end:::
273273

274-
## <a name="submit-to-cloud"></a> Submit the run to Azure Machine Learning
274+
## Submit the run to Azure Machine Learning
275275

276276
Select **Save and run script in terminal** to run the *run-pytorch-data.py* script. This run will train the model on the compute cluster using the data you uploaded.
277277

@@ -280,7 +280,7 @@ This code will print a URL to the experiment in the Azure Machine Learning studi
280280
[!INCLUDE [amlinclude-info](../../../includes/machine-learning-py38-ignore.md)]
281281

282282

283-
### <a name="inspect-log"></a> Inspect the log file
283+
### Inspect the log file
284284

285285
In the studio, go to the experiment job (by selecting the previous URL output) followed by **Outputs + logs**. Select the `std_log.txt` file. Scroll down through the log file until you see the following output:
286286

articles/machine-learning/v1/tutorial-1st-experiment-hello-world.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Your project folder structure will now look like:
6565
:::image type="content" source="../media/tutorial-1st-experiment-hello-world/directory-structure.png" alt-text="Folder structure shows hello.py in src subfolder.":::
6666

6767

68-
### <a name="test"></a>Test your script
68+
### Test your script
6969

7070
You can run your code locally, which in this case means on the compute instance. Running code locally has the benefit of interactive debugging of code.
7171

@@ -79,7 +79,7 @@ Select **Save and run script in terminal** to run the script.
7979

8080
You'll see the output of the script in the terminal window that opens. Close the tab and select **Terminate** to close the session.
8181

82-
## <a name="control-script"></a> Create a control script
82+
## Create a control script
8383

8484
A *control script* allows you to run your `hello.py` script on different compute resources. You use the control script to control how and where your machine learning code is run.
8585

@@ -148,7 +148,7 @@ Here's a description of how the control script works:
148148
:::row-end:::
149149

150150

151-
## <a name="submit"></a> Submit and run your code in the cloud
151+
## Submit and run your code in the cloud
152152

153153
1. Select **Save and run script in terminal** to run your control script, which in turn runs `hello.py` on the compute cluster that you created in the [setup tutorial](../quickstart-create-resources.md).
154154

@@ -164,7 +164,7 @@ Here's a description of how the control script works:
164164
1. When the status of the job is **Completed**, select **Output + logs** at the top of the page.
165165
1. Select **std_log.txt** to view the output of your job.
166166

167-
## <a name="monitor"></a>Monitor your code in the cloud in the studio
167+
## Monitor your code in the cloud in the studio
168168

169169
The output from your script will contain a link to the studio that looks something like this:
170170
`https://ml.azure.com/experiments/hello-world/runs/<run-id>?wsid=/subscriptions/<subscription-id>/resourcegroups/<resource-group>/workspaces/<workspace-name>`.

articles/machine-learning/v1/tutorial-1st-experiment-sdk-train.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -170,7 +170,7 @@ First you'll create a file with the package dependencies.
170170
```
171171
1. On the toolbar, select **Save** to save the file. Close the tab if you wish.
172172

173-
## <a name="create-local"></a> Create the control script
173+
## Create the control script
174174

175175
The difference between the following control script and the one that you used to submit "Hello world!" is that you add a couple of extra lines to set the environment.
176176

@@ -225,7 +225,7 @@ if __name__ == "__main__":
225225
:::column-end:::
226226
:::row-end:::
227227

228-
## <a name="submit"></a> Submit the run to Azure Machine Learning
228+
## Submit the run to Azure Machine Learning
229229

230230
1. Select **Save and run script in terminal** to run the *run-pytorch.py* script.
231231

@@ -235,7 +235,7 @@ if __name__ == "__main__":
235235

236236
### View the output
237237

238-
1. In the page that opens, you'll see the job status. The first time you run this script, Azure Machine Learning will build a new Docker image from your PyTorch environment. The whole job might around 10 minutes to complete. This image will be reused in future jobs to make them run much quicker.
238+
1. In the page that opens, you'll see the job status. The first time you run this script, Azure Machine Learning will build a new Docker image from your PyTorch environment. The whole job might take around 10 minutes to complete. This image will be reused in future jobs to make them run much quicker.
239239
1. You can see view Docker build logs in the Azure Machine Learning studio. Select the **Outputs + logs** tab, and then select **20_image_build_log.txt**.
240240
1. When the status of the job is **Completed**, select **Output + logs**.
241241
1. Select **std_log.txt** to view the output of your job.
@@ -367,7 +367,7 @@ dependencies:
367367
368368
Make sure you save this file before you submit the run.
369369
370-
### <a name="submit-again"></a> Submit the run to Azure Machine Learning
370+
### Submit the run to Azure Machine Learning
371371
372372
Select the tab for the *run-pytorch.py* script, then select **Save and run script in terminal** to re-run the *run-pytorch.py* script. Make sure you've saved your changes to `pytorch-env.yml` first.
373373

0 commit comments

Comments
 (0)