Skip to content

Commit da404de

Browse files
committed
removing merged include; it was linking from v1 to v2 content, which we should not be doing.
1 parent bab129d commit da404de

6 files changed

Lines changed: 0 additions & 18 deletions

articles/machine-learning/v1/how-to-monitor-tensorboard.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -141,9 +141,6 @@ compute_target.wait_for_completion(show_output=True, min_node_count=None)
141141
# print(compute_target.get_status().serialize())
142142
```
143143

144-
> [!NOTE]
145-
> You may choose to use [low-priority VMs](../how-to-manage-optimize-cost.md#low-pri-vm) to run some or all of your workloads. See how to [create a low-priority VM](how-to-create-attach-compute-cluster.md#lower-your-compute-cluster-cost-with-low-priority-vms).
146-
147144
### Configure and submit training job
148145

149146
Configure a training job by creating a ScriptRunConfig object.

articles/machine-learning/v1/how-to-secure-training-vnet.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -278,9 +278,6 @@ except ComputeTargetException:
278278

279279
When the creation process finishes, you train your model. For more information, see [Select and use a compute target for training](how-to-set-up-training-targets.md).
280280

281-
> [!NOTE]
282-
> You may choose to use [low-priority VMs](../how-to-manage-optimize-cost.md#low-pri-vm) to run some or all of your workloads. See how to [create a low-priority VM](how-to-create-attach-compute-cluster.md#lower-your-compute-cluster-cost-with-low-priority-vms).
283-
284281
## Azure Databricks
285282

286283
* The virtual network must be in the same subscription and region as the Azure Machine Learning workspace.

articles/machine-learning/v1/how-to-train-keras.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -123,9 +123,6 @@ except ComputeTargetException:
123123
compute_target.wait_for_completion(show_output=True, min_node_count=None, timeout_in_minutes=20)
124124
```
125125

126-
> [!NOTE]
127-
> You may choose to use [low-priority VMs](../how-to-manage-optimize-cost.md#low-pri-vm) to run some or all of your workloads. See how to [create a low-priority VM](how-to-create-attach-compute-cluster.md#lower-your-compute-cluster-cost-with-low-priority-vms).
128-
129126
For more information on compute targets, see the [what is a compute target](../concept-compute-target.md) article.
130127

131128
### Define your environment

articles/machine-learning/v1/how-to-train-pytorch.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -117,9 +117,6 @@ except ComputeTargetException:
117117

118118
If you instead want to create a CPU cluster, provide a different VM size to the vm_size parameter, such as STANDARD_D2_V2.
119119

120-
> [!NOTE]
121-
> You may choose to use [low-priority VMs](../how-to-manage-optimize-cost.md#low-pri-vm) to run some or all of your workloads. See how to [create a low-priority VM](how-to-create-attach-compute-cluster.md#lower-your-compute-cluster-cost-with-low-priority-vms).
122-
123120
For more information on compute targets, see the [what is a compute target](../concept-compute-target.md) article.
124121

125122
### Define your environment

articles/machine-learning/v1/how-to-train-tensorflow.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -123,9 +123,6 @@ except ComputeTargetException:
123123
compute_target.wait_for_completion(show_output=True, min_node_count=None, timeout_in_minutes=20)
124124
```
125125

126-
> [!NOTE]
127-
> You may choose to use [low-priority VMs](../how-to-manage-optimize-cost.md#low-pri-vm) to run some or all of your workloads. See how to [create a low-priority VM](how-to-create-attach-compute-cluster.md#lower-your-compute-cluster-cost-with-low-priority-vms).
128-
129126
For more information on compute targets, see the [what is a compute target](../concept-compute-target.md) article.
130127

131128
### Define your environment

articles/machine-learning/v1/how-to-use-automlstep-in-pipelines.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -94,9 +94,6 @@ if not compute_name in ws.compute_targets :
9494
compute_target = ws.compute_targets[compute_name]
9595
```
9696

97-
> [!NOTE]
98-
> You may choose to use [low-priority VMs](../how-to-manage-optimize-cost.md#low-pri-vm) to run some or all of your workloads. See how to [create a low-priority VM](how-to-create-attach-compute-cluster.md#lower-your-compute-cluster-cost-with-low-priority-vms).
99-
10097
The intermediate data between the data preparation and the automated ML step can be stored in the workspace's default datastore, so we don't need to do more than call `get_default_datastore()` on the `Workspace` object.
10198

10299
After that, the code checks if the Azure Machine Learning compute target `'cpu-cluster'` already exists. If not, we specify that we want a small CPU-based compute target. If you plan to use automated ML's deep learning features (for instance, text featurization with DNN support) you should choose a compute with strong GPU support, as described in [GPU optimized virtual machine sizes](../../virtual-machines/sizes-gpu.md).

0 commit comments

Comments
 (0)