Skip to content

Commit af20188

Browse files
authored
Merge pull request #100016 from PeterCLu/plu-aml-designer-tut-patch
Update designer tutorial
2 parents c837d2f + 3c2bc86 commit af20188

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/machine-learning/tutorial-designer-automobile-price-deploy.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Complete [part one of the tutorial](tutorial-designer-automobile-price-train-sco
2929

3030
## Create a real-time inference pipeline
3131

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.
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 web service inputs and outputs to handle requests.
3333

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

@@ -44,10 +44,10 @@ To deploy your pipeline, you must first convert the training pipeline into a rea
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 enters 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 pipeline and where data is returned.
4848

4949
> [!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.
50+
> By default, the **Web Service Input** will expect the same data schema as the training data used to create the predictive pipeline. In this scenario, price is included in the schema. However, price isn't used as a factor during prediction.
5151
>
5252
5353
1. Select **Run**, and use the same compute target and experiment that you used in part one.

0 commit comments

Comments
 (0)