Skip to content

Commit 74d1819

Browse files
authored
Merge pull request #189671 from nibaccam/ui-path
Train on UI | new Inputs screenshots
2 parents a22c1f4 + 128edb3 commit 74d1819

File tree

4 files changed

+3
-10
lines changed

4 files changed

+3
-10
lines changed

articles/machine-learning/how-to-train-with-ui.md

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Create a Training Job with the job creation UI
33
titleSuffix: Azure Machine Learning
4-
description: Learn how to use the job creation UI in Azure Machine Learning Studio to create a training job.
4+
description: Learn how to use the job creation UI in Azure Machine Learning studio to create a training job.
55
services: machine-learning
66
ms.service: machine-learning
77
ms.subservice: core
@@ -15,7 +15,7 @@ ms.reviewer: laobri
1515

1616
# Create a training job with the job creation UI (preview)
1717

18-
There are many ways to create a training job with Azure Machine Learning. You can use the CLI (see [Train models (create jobs) with the CLI (v2) (preview)](how-to-train-cli.md)), the REST API (see [Train models with REST (preview)](how-to-train-with-rest.md)), or you can use the UI to directly create a training job. In this article, you'll learn how to use your own data and code to train a machine learning model with the job creation UI in Azure Machine Learning Studio.
18+
There are many ways to create a training job with Azure Machine Learning. You can use the CLI (see [Train models (create jobs) with the CLI (v2) (preview)](how-to-train-cli.md)), the REST API (see [Train models with REST (preview)](how-to-train-with-rest.md)), or you can use the UI to directly create a training job. In this article, you'll learn how to use your own data and code to train a machine learning model with the job creation UI in Azure Machine Learning studio.
1919

2020
## Prerequisites
2121

@@ -130,17 +130,10 @@ Here, the source code is in the `src` subdirectory. The command would be `python
130130

131131
#### Inputs
132132

133-
There are two ways to do input binding:
133+
When you use an input in the command, you need to specify the input name. To indicate an input variable, use the form `${{inputs.input_name}}`. For instance, `${{inputs.wiki}}`. You can then refer to it in the command, for instance, `--data ${{inputs.wiki}}`.
134134

135-
* Input name: When you use an input in the command, you need to specify the input name. To indicate an input variable, use the form `{inputs.input_name}`. For instance, `{inputs.wiki}`. You can then refer to it in the command, for instance, `--data {inputs.wiki}`.
136135
[![Refer input name in the command](media/how-to-train-with-ui/input-command-name.png)](media/how-to-train-with-ui/input-command-name.png)
137136

138-
* Path: You can use `--data .path` to specify a cloud location. The path is what you enter in the **Path on compute** field.
139-
[![Refer input path in the command](media/how-to-train-with-ui/input-command-path.png)](media/how-to-train-with-ui/input-command-path.png)
140-
141-
>[!NOTE]
142-
>In the **command to start the job**, you must add a period to the **Path on compute** value. For instance, `/data/wikitext-2` becomes `./data/wikitext-2`.
143-
144137
## Review and Create
145138

146139
Once you've configured your job, choose **Next** to go to the **Review** page. To modify a setting, choose the pencil icon and make the change.
-36.2 KB
Loading
-78 KB
Loading
Binary file not shown.

0 commit comments

Comments
 (0)