Skip to content

Commit 00923a3

Browse files
committed
edit pass: automobile-price-train-score-and-deploy
1 parent ce00e2a commit 00923a3

File tree

5 files changed

+45
-45
lines changed

5 files changed

+45
-45
lines changed
Lines changed: 26 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: 'Tutorial: Deploy a machine learning model with the designer'
33
titleSuffix: Azure Machine Learning
4-
description: Learn how to build a predictive analytics solution in Azure Machine Learning designer (preview). Train, score, and deploy a machine learning model using drag and drop modules.
4+
description: Learn how to build a predictive analytics solution in Azure Machine Learning designer (preview). Train, score, and deploy a machine learning model by using drag-and-drop modules.
55

66
author: peterclu
77
ms.author: peterlu
@@ -15,27 +15,27 @@ ms.date: 11/04/2019
1515
# Tutorial: Deploy a machine learning model with the designer (preview)
1616
[!INCLUDE [applies-to-skus](../../../includes/aml-applies-to-enterprise-sku.md)]
1717

18-
You can deploy the predictive model developed in [part one of the tutorial](tutorial-designer-automobile-price-train-score.md) to give others a chance to use it. In part 1, you trained your model. Now, it's time to generate new predictions based on user input. In this part of the tutorial, you will:
18+
You can deploy the predictive model developed in [part one of the tutorial](tutorial-designer-automobile-price-train-score.md) to give others a chance to use it. In part one, you trained your model. Now, it's time to generate new predictions based on user input. In this part of the tutorial, you will:
1919

2020
> [!div class="checklist"]
21-
> * Create a real-time inference pipeline
22-
> * Create an inferencing cluster
23-
> * Deploy a real-time endpoint
24-
> * Test a real-time endpoint
21+
> * Create a real-time inference pipeline.
22+
> * Create an inferencing cluster.
23+
> * Deploy the real-time endpoint.
24+
> * Test the real-time endpoint.
2525
2626
## Prerequisites
2727

2828
Complete [part one of the tutorial](tutorial-designer-automobile-price-train-score.md) to learn how to train and score a machine learning model in the designer.
2929

3030
## Create a real-time inference pipeline
3131

32-
In order to deploy your pipeline, you must first convert the training pipeline into a real-time inference pipeline. This process removes training modules and adds inputs and outputs for inferencing requests.
32+
To deploy your pipeline, you must first convert the training pipeline into a real-time inference pipeline. This process removes training modules and adds inputs and outputs for inferencing requests.
3333

3434
### Create a real-time inference pipeline
3535

36-
1. Above the pipeline canvas, select **Create inference pipeline** > **Real-time inference pipeline**
36+
1. Above the pipeline canvas, select **Create inference pipeline** > **Real-time inference pipeline**.
3737

38-
Your pipeline should now look like this:
38+
Your pipeline should now look like this:
3939

4040
![Screenshot showing the expected configuration of the pipeline after preparing it for deployment](./media/ui-tutorial-automobile-price-deploy/real-time-inference-pipeline.png)
4141

@@ -44,13 +44,13 @@ In order to deploy your pipeline, you must first convert the training pipeline i
4444
* The trained model is stored as a **Dataset** module in the module palette. You can find it under **My Datasets**.
4545
* Training modules like **Train Model** and **Split Data** are removed.
4646
* The saved trained model is added back into the pipeline.
47-
* **Web Service Input** and **Web Service Output** modules are added. These modules show where user data will enter the model, and where data is returned.
47+
* **Web Service Input** and **Web Service Output** modules are added. These modules show where user data enters the model and where data is returned.
4848

49-
> [!Note]
50-
> The **training pipeline** is saved under the new tab at the top of the pipeline canvas. It can also be found as a published pipeline in the designer.
49+
> [!NOTE]
50+
> The *training pipeline* is saved under the new tab at the top of the pipeline canvas. It can also be found as a published pipeline in the designer.
5151
>
5252
53-
1. Select **Run** and use the same compute target and experiment you used in part 1.
53+
1. Select **Run**, and use the same compute target and experiment that you used in part one.
5454

5555
1. Select the **Score Model** module.
5656

@@ -60,24 +60,24 @@ In order to deploy your pipeline, you must first convert the training pipeline i
6060

6161
## Create an inferencing cluster
6262

63-
In the dialog that appears, you can select from any existing Azure Kubernetes Service (AKS) clusters in to deploy your model to. If you don't have an AKS cluster, use the following steps to create one.
63+
In the dialog box that appears, you can select from any existing Azure Kubernetes Service (AKS) clusters to deploy your model to. If you don't have an AKS cluster, use the following steps to create one.
6464

65-
1. Select **Compute** in the dialog box that appears to navigate to the **Compute** page.
65+
1. Select **Compute** in the dialog box that appears to go to the **Compute** page.
6666

67-
1. In the navigation ribbon, select **Inference Clusters** > **+ New**.
67+
1. On the navigation ribbon, select **Inference Clusters** > **+ New**.
6868

69-
![Screenshot showing how to navigate to the new inference cluster pane](./media/ui-tutorial-automobile-price-deploy/new-inference-cluster.png)
69+
![Screenshot showing how to get to the new inference cluster pane](./media/ui-tutorial-automobile-price-deploy/new-inference-cluster.png)
7070

7171
1. In the inference cluster pane, configure a new Kubernetes Service.
7272

73-
1. Enter "aks-compute" for the **Compute name**.
73+
1. Enter *aks-compute* for the **Compute name**.
7474

75-
1. Select a nearby available **Region**.
75+
1. Select a nearby region that's available for the **Region**.
7676

7777
1. Select **Create**.
7878

79-
> [!Note]
80-
> It takes approximately 15 minutes to create a new AKS service. You can check the provisioning state on the **Inference Clusters** page
79+
> [!NOTE]
80+
> It takes approximately 15 minutes to create a new AKS service. You can check the provisioning state on the **Inference Clusters** page.
8181
>
8282
8383
## Deploy the real-time endpoint
@@ -94,21 +94,21 @@ After your AKS service has finished provisioning, return to the real-time infere
9494

9595
![Screenshot showing how to set up a new real-time endpoint](./media/ui-tutorial-automobile-price-deploy/setup-endpoint.png)
9696

97-
A success notification above the canvas will appear when deployment completes, it may take a few minutes.
97+
A success notification above the canvas appears after deployment finishes. It might take a few minutes.
9898

9999
## Test the real-time endpoint
100100

101-
Once deployment completes, you can test your real-time endpoint by navigating to the **Endpoints** page.
101+
After deployment finishes, you can test your real-time endpoint by going to the **Endpoints** page.
102102

103103
1. On the **Endpoints** page, select the endpoint you deployed.
104104

105105
![Screenshot showing the real-time endpoints tab with the recently created endpoint highlighted](./media/ui-tutorial-automobile-price-deploy/endpoints.png)
106106

107107
1. Select **Test**.
108108

109-
1. You can manually input testing data or use the autofilled sample data and select **Test**.
109+
1. You can manually input testing data or use the autofilled sample data, and select **Test**.
110110

111-
The portal submits a test request to the endpoint and shows the results. Although a price value is generated for the input data, it is not used to generate the prediction value.
111+
The portal submits a test request to the endpoint and shows the results. Although a price value is generated for the input data, it isn't used to generate the prediction value.
112112

113113
![Screenshot showing how to test the real-time endpoint with the scored label for price highlighted](./media/ui-tutorial-automobile-price-deploy/test-endpoint.png)
114114

@@ -118,7 +118,7 @@ Once deployment completes, you can test your real-time endpoint by navigating to
118118

119119
## Next steps
120120

121-
In this tutorial, you learned the key steps in creating, deploying, and consuming a machine learning model in the designer. To learn more about how you can use the designer to solve other types of problems, see out our other sample pipelines.
121+
In this tutorial, you learned the key steps in how to create, deploy, and consume a machine learning model in the designer. To learn more about how you can use the designer to solve other types of problems, see our other sample pipelines.
122122

123123
> [!div class="nextstepaction"]
124124
> [Credit risk classification sample](how-to-designer-sample-classification-credit-risk-cost-sensitive.md)

articles/machine-learning/service/tutorial-designer-automobile-price-train-score.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@ Your dataset still has missing values after you remove the **normalized-losses**
136136

137137
1. In the properties pane, select **Remove entire row** under **Cleaning mode**.
138138

139-
1. In the properties pane **Comment** box, enter *Remove missing value rows*.
139+
1. In the properties pane **Comment** box, enter *Remove missing value rows*.
140140

141141
Your pipeline should now look something like this:
142142

includes/aml-create-in-portal-enterprise.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.date: 10/04/2019
1313

1414
1. Sign in to the [Azure portal](https://portal.azure.com/) by using the credentials for your Azure subscription.
1515

16-
1. In the upper-left corner of Azure portal, select **+ Create a resource**.
16+
1. In the upper-left corner of the Azure portal, select **+ Create a resource**.
1717

1818
![Create a new resource](media/aml-create-in-portal/create-workspace.gif)
1919

@@ -27,15 +27,15 @@ ms.date: 10/04/2019
2727

2828
Field|Description
2929
---|---
30-
Workspace name |Enter a unique name that identifies your workspace. In this example, we use **docs-ws**. Names must be unique across the resource group. Use a name that's easy to recall and to differentiate from workspaces created by others.
30+
Workspace name |Enter a unique name that identifies your workspace. In this example, we use **docs-ws**. Names must be unique across the resource group. Use a name that's easy to recall and to differentiate from workspaces created by others.
3131
Subscription |Select the Azure subscription that you want to use.
32-
Resource group | Use an existing resource group in your subscription or enter a name to create a new resource group. A resource group holds related resources for an Azure solution. In this example, we use **docs-aml**.
32+
Resource group | Use an existing resource group in your subscription, or enter a name to create a new resource group. A resource group holds related resources for an Azure solution. In this example, we use **docs-aml**.
3333
Location | Select the location closest to your users and the data resources to create your workspace.
34-
Workspace edition | Select **Enterprise**. This tutorial requires the use of the Enterprise edition. The Enterprise edition is in preview and does not currently add any extra costs.
34+
Workspace edition | Select **Enterprise**. This tutorial requires the use of the Enterprise edition. The Enterprise edition is in preview and doesn't currently add any extra costs.
3535

36-
1. After you are finished configuring the workspace, select **Create**.
36+
1. After you're finished configuring the workspace, select **Create**.
3737

38-
> [!Warning]
38+
> [!WARNING]
3939
> It can take several minutes to create your workspace in the cloud.
4040
4141
When the process is finished, a deployment success message appears.

includes/aml-ui-cleanup.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.date: 11/06/2019
1515
1616
### Delete everything
1717

18-
If you don't plan to use anything that you created, delete the entire resource group so you don't incur any charges:
18+
If you don't plan to use anything that you created, delete the entire resource group so you don't incur any charges.
1919

2020
1. In the Azure portal, select **Resource groups** on the left side of the window.
2121

@@ -25,20 +25,20 @@ If you don't plan to use anything that you created, delete the entire resource g
2525

2626
1. Select **Delete resource group**.
2727

28-
Deleting the resource group also deletes all resources that you created in the designer.
28+
Deleting the resource group also deletes all resources that you created in the designer.
2929

3030
### Delete individual assets
3131

3232
In the designer where you created your experiment, delete individual assets by selecting them and then selecting the **Delete** button.
3333

34-
The compute target that you created here *automatically autoscales* to zero nodes when it's not being used. This is to minimize charges. If you want to delete the compute target, take these steps:
34+
The compute target that you created here *automatically autoscales* to zero nodes when it's not being used. This action is taken to minimize charges. If you want to delete the compute target, take these steps:
3535

3636
![Delete assets](./media/aml-ui-cleanup/delete-asset.png)
3737

3838
Datasets can be unregistered from your workspace by selecting each dataset and selecting **Unregister**.
3939

4040
![Unregister dataset](./media/aml-ui-cleanup/unregister-dataset.png)
4141

42-
To delete a dataset, navigate to the storage account using the Azure portal or the Storage Explorer and manually delete those assets.
42+
To delete a dataset, go to the storage account by using the Azure portal or the Storage Explorer and manually delete those assets.
4343

4444

includes/aml-ui-create-training-compute.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.topic: "include"
1111
ms.date: 10/09/2019
1212
---
1313

14-
A pipeline runs on a compute target which is a compute resource that is attached to your workspace. Once you create a compute target, you can reuse it for future runs.
14+
A pipeline runs on a compute target, which is a compute resource that's attached to your workspace. After you create a compute target, you can reuse it for future runs.
1515

1616
1. Select **Run** at the top of the canvas to run the pipeline.
1717

@@ -20,28 +20,28 @@ A pipeline runs on a compute target which is a compute resource that is attached
2020
If you already have an available compute target, you can select it to run this pipeline.
2121

2222
> [!NOTE]
23-
> The designer can only run experiments on Machine Learning Compute targets. Other compute targets will not be shown.
23+
> The designer can run experiments only on Azure Machine Learning Compute targets. Other compute targets won't be shown.
2424
25-
1. Provide a name for the compute resource.
25+
1. Enter a name for the compute resource.
2626

2727
1. Select **Save**.
2828

2929
![Setup compute target](./media/aml-ui-create-training-compute/set-compute.png)
3030

3131
1. Select **Run**.
3232

33-
1. In the **Set up pipeline run** dialog, select **+ New experiment** for the **Experiment**
33+
1. In the **Set up pipeline run** dialog box, select **+ New experiment** for the **Experiment**.
3434

3535
> [!NOTE]
3636
> Experiments group similar pipeline runs together. If you run a pipeline multiple times, you can select the same experiment for successive runs.
3737
38-
* Enter a descriptive **Experiment Name**
38+
1. Enter a descriptive name for **Experiment Name**.
3939

40-
* Select **Run**
40+
1. Select **Run**.
4141

4242
You can view run status and details at the top right of the canvas.
4343

4444
> [!NOTE]
45-
> It takes approximately 5 minutes to create a compute resource. After the resource is created, you can reuse it and skip this wait time for future runs.
45+
> It takes approximately five minutes to create a compute resource. After the resource is created, you can reuse it and skip this wait time for future runs.
4646
>
47-
> The compute resource will autoscale to 0 nodes when it is idle to save cost. When you use it again after a delay, you may again experience approximately 5 minutes of wait time while it scales back up.
47+
> The compute resource autoscales to zero nodes when it's idle to save cost. When you use it again after a delay, you might experience approximately five minutes of wait time while it scales back up.

0 commit comments

Comments
 (0)