Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit b24c4cc

Browse files
committedFeb 22, 2022
update migration article
1 parent b4b63fa commit b24c4cc

File tree

5 files changed

+19
-2
lines changed

5 files changed

+19
-2
lines changed
 
Loading
Loading

‎articles/machine-learning/migrate-overview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,8 @@ Learn how to migrate from Studio (classic) to Azure Machine Learning. Azure Mach
2424

2525
This is a guide for a basic "lift and shift" migration. If you want to optimize an existing machine learning workflow, or modernize a machine learning platform, see the [Azure Machine Learning adoption framework](https://aka.ms/mlstudio-classic-migration-repo) for additional resources including digital survey tools, worksheets, and planning templates.
2626

27+
Please work with your Cloud Solution Architect on the migration.
28+
2729
![Azure ML adoption framework](./media/migrate-overview/aml-adoption-framework.png)
2830

2931
## Recommended approach
@@ -59,6 +61,8 @@ To migrate to Azure Machine Learning, we recommend the following approach:
5961
1. Align an actionable Azure Machine Learning adoption plan to business outcomes.
6062
1. Prepare people, processes, and environments for change.
6163

64+
Please work with your Cloud Solution Architect to define your stragety.
65+
6266
See the [Azure Machine Learning Adoption Framework](https://aka.ms/mlstudio-classic-migration-repo) for planning resources including a planning doc template.
6367

6468
## Step 3: Rebuild your first model

‎articles/machine-learning/migrate-rebuild-experiment.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,20 @@ After the run finishes, you can check the results of each module:
8383
- **View Log**: View driver and system logs. Use the **70_driver_log** to see information related to your user-submitted script such as errors and exceptions.
8484

8585
> [!IMPORTANT]
86-
> Designer components use open source Python packages, compared to C# packages in Studio (classic). As a result, module output may vary slightly between the designer and Studio (classic).
86+
> Designer components use open source Python packages to implement machine learning algorithms. However Studio(classic) use a Microsoft internal C# library. As a result, prediction result may vary between the designer and Studio (classic).
87+
88+
89+
## Save trained model to use in another pipeline
90+
91+
Sometimes you may want to save the model trained in a pipeline and use the model in another pipeline later. In Studio(classic), all trained models are saved in "Trained Models" category in the module list. In designer, the trained models are automatically registered as file dataset with system generately name. Naming convention follows "MD - pipeline draft name - component name - Trained model ID" pattern.
92+
93+
To give a trained model a meaningful name, you can register the output of **Train Model** component as a **file dataset**. Give it the name you want, for example linear-regression-model.
94+
95+
![Screenshot showing how to save trained model.](./media/migrate-rebuild-experiment/save-model.png)
96+
97+
You can find the trained model in "Dataset" category in the component list or seach it by name. Then connect the trained model to a **Score Model** component to use it for prediction.
98+
99+
![Screenshot showing how to find trained model.](./media/migrate-rebuild-experiment/search-model-in-list.png)
87100

88101

89102
## Next steps

‎includes/machine-learning-studio-classic-deprecation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.author: cgronlun
1212
> [!IMPORTANT]
1313
> Support for Machine Learning Studio (classic) will end on 31 August 2024. We recommend you transition to [Azure Machine Learning](https://azure.microsoft.com/services/machine-learning/) by that date.
1414
>
15-
> Beginning 1 December 2021, you will not be able to create new Machine Learning Studio (classic) resources. Through 31 August 2024, you can continue to use the existing Machine Learning Studio (classic) resources.
15+
> Beginning 1 December 2021, you will not be able to create new Machine Learning Studio (classic) resources (workspace and web service plan). Through 31 August 2024, you can continue to use the existing Machine Learning Studio (classic) experiments and web services.
1616
>
1717
> - See [information on moving machine learning projects from ML Studio (classic) to Azure Machine Learning](../articles/machine-learning/migrate-overview.md).
1818
> - Learn more about [Azure Machine Learning](../articles/machine-learning/overview-what-is-azure-machine-learning.md)

0 commit comments

Comments
 (0)
Please sign in to comment.