Skip to content

Commit c7953eb

Browse files
authored
Merge pull request #1606 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-ai-docs (branch main)
2 parents 8afe620 + 4ecf918 commit c7953eb

File tree

5 files changed

+10
-9
lines changed

5 files changed

+10
-9
lines changed

articles/machine-learning/how-to-log-view-metrics.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -148,7 +148,7 @@ mlflow.log_params(params)
148148
149149
## Log metrics
150150
151-
Metrics, as opposite to parameters, are always numeric, and they can be logged either synchronously or asynchronously. When metrics are logged, they are immediately available for consumption upon call return. The following table describes how to log specific numeric types:
151+
Metrics, as opposed to parameters, are always numeric, and they can be logged either synchronously or asynchronously. When metrics are logged, they are immediately available for consumption upon call return. The following table describes how to log specific numeric types:
152152
153153
|Logged value|Example code| Notes|
154154
|----|----|----|
@@ -261,7 +261,7 @@ MLflow supports two ways of logging images. Both ways persist the given image as
261261
|Logged value|Example code| Notes|
262262
|----|----|----|
263263
|Log numpy metrics or PIL image objects|`mlflow.log_image(img, "figure.png")`| `img` should be an instance of `numpy.ndarray` or `PIL.Image.Image`. `figure.png` is the name of the artifact generated inside of the run. It doesn't have to be an existing file.|
264-
|Log matlotlib plot or image file|` mlflow.log_figure(fig, "figure.png")`| `figure.png` is the name of the artifact generated inside of the run. It doesn't have to be an existing file. |
264+
|Log matplotlib plot or image file|` mlflow.log_figure(fig, "figure.png")`| `figure.png` is the name of the artifact generated inside of the run. It doesn't have to be an existing file. |
265265
266266
## Log files
267267
@@ -275,7 +275,7 @@ In general, files in MLflow are called artifacts. You can log artifacts in multi
275275
|Log all the artifacts in an existing folder | `mlflow.log_artifacts("path/to/folder")`| Folder structure is copied to the run, but the root folder indicated isn't included. |
276276
277277
> [!TIP]
278-
> When you log large files with `log_artifact` or `log_model`, you might encounter time out errors before the upload of the file is completed. Consider increasing the timeout value by adjusting the environment variable `AZUREML_ARTIFACTS_DEFAULT_TIMEOUT`. It's default value is *300* (seconds).
278+
> When you log large files with `log_artifact` or `log_model`, you might encounter time-out errors before the upload of the file is completed. Consider increasing the timeout value by adjusting the environment variable `AZUREML_ARTIFACTS_DEFAULT_TIMEOUT`. Its default value is *300* (seconds).
279279
280280
## Log models
281281
@@ -297,7 +297,7 @@ mlflow.autolog()
297297
```
298298
299299
> [!TIP]
300-
> You can control what gets automatically logged with autolog. For instance, if you indicate `mlflow.autolog(log_models=False)`, MLflow logs everything but models for you. Such control is useful in cases where you want to log models manually but still enjoy automatic logging of metrics and parameters. Also notice that some frameworks might disable automatic logging of models if the trained model goes beyond specific boundaries. Such behavior depends on the flavor used and we recommend that you view the documentation if this is your case.
300+
> You can control what gets automatically logged with autolog. For instance, if you indicate `mlflow.autolog(log_models=False)`, MLflow logs everything but models for you. Such control is useful in cases where you want to log models manually but still enjoy automatic logging of metrics and parameters. Also, notice that some frameworks might disable automatic logging of models if the trained model goes beyond specific boundaries. Such behavior depends on the flavor used and we recommend that you view the documentation if this is your case.
301301
302302
## View information about jobs or runs with MLflow
303303
@@ -366,15 +366,15 @@ Log files are an essential resource for debugging the Azure Machine Learning wor
366366
367367
#### user_logs folder
368368
369-
This folder contains information about the user generated logs. This folder is open by default, and the **std_log.txt** log is selected. The **std_log.txt** is where your code's logs (for example, print statements) show up. This file contains `stdout` log and `stderr` logs from your control script and training script, one per process. In most cases, you monitor the logs here.
369+
This folder contains information about the user-generated logs. This folder is open by default, and the **std_log.txt** log is selected. The **std_log.txt** is where your code's logs (for example, print statements) show up. This file contains `stdout` log and `stderr` logs from your control script and training script, one per process. In most cases, you monitor the logs here.
370370
371371
#### system_logs folder
372372
373373
This folder contains the logs generated by Azure Machine Learning and it's closed by default. The logs generated by the system are grouped into different folders, based on the stage of the job in the runtime.
374374
375375
#### Other folders
376376
377-
For jobs training on multi-compute clusters, logs are present for each IP node. The structure for each node is the same as single node jobs. There's one more logs folder for overall execution, stderr, and stdout logs.
377+
For jobs training on multi-compute clusters, logs are present for each IP node. The structure for each node is the same as single-node jobs. There's one more logs folder for overall execution, stderr, and stdout logs.
378378
379379
Azure Machine Learning logs information from various sources during training, such as AutoML or the Docker container that runs the training job. Many of these logs aren't documented. If you encounter problems and contact Microsoft support, they might be able to use these logs during troubleshooting.
380380

articles/machine-learning/how-to-managed-network.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -787,7 +787,7 @@ To enable the [serverless Spark jobs](how-to-submit-spark-jobs.md) for the manag
787787
2. Provision the managed virtual network.
788788

789789
> [!NOTE]
790-
> If your workspace is already configured for a public endpoint (for example, with an Azure Virtual Network), and has [public network access enabled](how-to-configure-private-link.md#enable-public-access), you must disable it before provisioning the managed VNet. If you don't disable public network access when provisioning the managed VNet, the private endpoints for the managed endpoint may not be created successfully.
790+
> If your workspace has [public network access enabled](/azure/machine-learning/how-to-configure-private-link?view=azureml-api-2#enable-public-access), you must disable it before provisioning the managed VNet. If you don't disable public network access when provisioning the managed VNet, the private endpoints for the workspace may not be created automatically in the managed VNet. Otherwise, you would have to manually configure the private endpoint outbound rule for the workspace after the provisioning.
791791

792792
# [Azure CLI](#tab/azure-cli)
793793

articles/machine-learning/how-to-track-experiments-mlflow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -164,7 +164,7 @@ By default, experiments are in descending order by `start_time`, which is the ti
164164
```
165165

166166
> [!WARNING]
167-
> Using `order_by` with expressions containing `metrics.*`, `params.*`, or `tags.*` in the parameter `order_by` isn't currently supported. Instead, use the `order_values` method from Pandas as shown in the example.
167+
> Using `order_by` with expressions containing `metrics.*`, `params.*`, or `tags.*` in the parameter `order_by` isn't currently supported. Instead, use the `sort_values` method from Pandas as shown in the example.
168168

169169
### Filter runs
170170

articles/search/search-region-support.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ AI service integration refers to internal connections to an Azure AI multi-servi
5656

5757
| Region | AI service integration | Semantic ranker | Availability zones | Capacity constrained |
5858
|--|--|--|--|--|
59-
| North Europe​​ |||| |
59+
| North Europe​​ |||| S2, S3, S3, S3 HD, L1, L2 |
6060
| West Europe​​ <sup>1</sup>|||| All Tiers |
6161
| France Central​​ |||| |
6262
| Germany West Central​ <sup>1</sup>​|| || |

articles/search/search-sku-tier.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,7 @@ Currently, several regions are at capacity for specific tiers and can't be used
6464
| US Gov Virginia | All tiers | US Gov Arizona |
6565
| West Europe | All tiers | Sweden Central/North Europe |
6666
| West US 3| Basic, S1 | Central US |
67+
| North Europe | S2, S3, S3 HD, L1, L2 | UK South |
6768

6869
## Feature availability by tier
6970

0 commit comments

Comments
 (0)