You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/machine-learning/concept-expressions.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ ms.custom: cliv2, sdkv2
17
17
18
18
With Azure Machine Learning SDK and CLI v2, you can use _expressions_ when a value may not be known when you're authoring a job or component. When you submit a job or call a component, the expression is evaluated and the value is substituted.
19
19
20
-
The format for an expression is `${{ <expression> }}`. Some expressions are evaluated on the _client_, when submitting the job or component. Other expressions are evaluated on the _server_&emdash; the compute where the job or component is running.
20
+
The format for an expression is `${{ <expression> }}`. Some expressions are evaluated on the _client_, when submitting the job or component. Other expressions are evaluated on the _server_(the compute where the job or component is running.)
21
21
22
22
## Client expressions
23
23
@@ -26,7 +26,7 @@ The format for an expression is `${{ <expression> }}`. Some expressions are eval
26
26
27
27
| Expression | Description | Scope |
28
28
| ---- | ---- | ---- |
29
-
|`${{inputs.<input_name>}}`| References to an input data asset. | Works for all jobs. |
29
+
|`${{inputs.<input_name>}}`| References to an input data asset or model. | Works for all jobs. |
30
30
|`${{outputs.<output_name>}}`| References to an output data asset. | Works for all jobs. |
31
31
|`${{search_space.<hyperparameter>}}`| References the hyperparameters to use in a sweep job. The hyperparameter values for each trial are selected based on the `search_space`. | Sweep jobs only. |
32
32
|`${{parent.inputs.<input_name>}}`| Binds the inputs of a child job (pipeline step) in a pipeline to the inputs of the top-level parent pipeline job. | Pipeline jobs only. |
@@ -46,4 +46,5 @@ For more information on these expressions, see the following articles and exampl
46
46
*[Hyperparameter tuning a model](how-to-tune-hyperparameters.md)
47
47
*[Tutorial: ML pipelines with Python SDK v2](tutorial-pipeline-python-sdk.md)
48
48
*[Create and run component-based ML pipelines (CLI)](how-to-create-component-pipelines-cli.md)
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-train-model.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -193,7 +193,7 @@ In the above examples, you configured:
193
193
-`code` - path where the code to run the command is located
194
194
-`command` - command that needs to be run
195
195
-`environment` - the environment needed to run the training script. In this example, we use a curated or ready-made environment provided by Azure Machine Learning called `AzureML-lightgbm-3.2-ubuntu18.04-py37-cpu`. We use the latest version of this environment by using the `@latest` directive. You can also use custom environments by specifying a base docker image and specifying a conda yaml on top of it.
196
-
-`inputs` - dictionary of inputs using name value pairs to the command. The key is a name for the input within the context of the job and the value is the input value. Inputs are referenced in the `command` using the `${{inputs.<input_name>}}` expression. To use files or folders as inputs, you can use the `Input` class.
196
+
-`inputs` - dictionary of inputs using name value pairs to the command. The key is a name for the input within the context of the job and the value is the input value. Inputs are referenced in the `command` using the `${{inputs.<input_name>}}` expression. To use files or folders as inputs, you can use the `Input` class. For more information, see [SDK and CLI v2 expressions](concept-expressions.md).
197
197
198
198
For more information, see the [reference documentation](/python/api/azure-ai-ml/azure.ai.ml#azure-ai-ml-command).
199
199
@@ -212,7 +212,7 @@ The `az ml job create` command used in this example requires a YAML job definiti
212
212
In the above, you configured:
213
213
-`code` - path where the code to run the command is located
214
214
-`command` - command that needs to be run
215
-
-`inputs` - dictionary of inputs using name value pairs to the command. The key is a name for the input within the context of the job and the value is the input value. Inputs are referenced in the `command` using the `${{inputs.<input_name>}}` expression.
215
+
-`inputs` - dictionary of inputs using name value pairs to the command. The key is a name for the input within the context of the job and the value is the input value. Inputs are referenced in the `command` using the `${{inputs.<input_name>}}` expression. For more information, see [SDK and CLI v2 expressions](concept-expressions.md).
216
216
-`environment` - the environment needed to run the training script. In this example, we use a curated or ready-made environment provided by Azure Machine Learning called `AzureML-sklearn-0.24-ubuntu18.04-py37-cpu`. We use the latest version of this environment by using the `@latest` directive. You can also use custom environments by specifying a base docker image and specifying a conda yaml on top of it.
217
217
To submit the job, use the following command. The run ID (name) of the training job is stored in the `$run_id` variable:
Copy file name to clipboardExpand all lines: articles/machine-learning/tutorial-pipeline-python-sdk.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -350,7 +350,7 @@ if __name__ == "__main__":
350
350
351
351
Now that you have a script that can perform the desired task, create an Azure Machine Learning Component from it.
352
352
353
-
Use the general purpose `CommandComponent` that can run command line actions. This command line action can directly call system commands or run a script. The inputs/outputs are specified on the command line via the `${{ ... }}` notation.
353
+
Use the general purpose `CommandComponent` that can run command line actions. This command line action can directly call system commands or run a script. The inputs/outputs are specified on the command line via the `${{ ... }}`(expression) notation. For more information, see [SDK and CLI v2 expressions](concept-expressions.md).
0 commit comments