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/how-to-log-view-metrics.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,7 +148,7 @@ mlflow.log_params(params)
148
148
149
149
## Log metrics
150
150
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:
152
152
153
153
|Logged value|Example code| Notes|
154
154
|----|----|----|
@@ -261,7 +261,7 @@ MLflow supports two ways of logging images. Both ways persist the given image as
261
261
|Logged value|Example code| Notes|
262
262
|----|----|----|
263
263
|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. |
265
265
266
266
## Log files
267
267
@@ -275,7 +275,7 @@ In general, files in MLflow are called artifacts. You can log artifacts in multi
275
275
|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. |
276
276
277
277
> [!TIP]
278
-
> When you log large files with `log_artifact` or `log_model`, you might encounter timeout 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).
279
279
280
280
## Log models
281
281
@@ -297,7 +297,7 @@ mlflow.autolog()
297
297
```
298
298
299
299
> [!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 foryou. Such control is usefulin 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.
301
301
302
302
## View information about jobs or runs with MLflow
303
303
@@ -366,15 +366,15 @@ Log files are an essential resource for debugging the Azure Machine Learning wor
366
366
367
367
#### user_logs folder
368
368
369
-
This folder contains information about the usergenerated 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.
370
370
371
371
#### system_logs folder
372
372
373
373
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.
374
374
375
375
#### Other folders
376
376
377
-
For jobs training on multi-compute clusters, logs are present for each IP node. The structure for each node is the same as singlenode 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.
378
378
379
379
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.
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-managed-network.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
@@ -787,7 +787,7 @@ To enable the [serverless Spark jobs](how-to-submit-spark-jobs.md) for the manag
787
787
2. Provision the managed virtual network.
788
788
789
789
> [!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.
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-track-experiments-mlflow.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
@@ -164,7 +164,7 @@ By default, experiments are in descending order by `start_time`, which is the ti
164
164
```
165
165
166
166
> [!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.
0 commit comments