|
1 | 1 | ---
|
2 |
| -title: What is the Azure Machine Learning designer(v2)? |
| 2 | +title: What is Designer (v2)? |
3 | 3 | titleSuffix: Azure Machine Learning
|
4 |
| -description: Learn what the Azure Machine Learning designer is and what tasks you can use it for. The drag-and-drop UI enables customer to build machine learning pipeline. |
| 4 | +description: Learn about the drag-and-drop Designer UI in Machine Learning studio, and how it uses Designer v2 custom components to build and edit machine learning pipelines. |
5 | 5 | ms.service: machine-learning
|
6 | 6 | ms.subservice: core
|
7 | 7 | ms.topic: conceptual
|
8 | 8 | ms.author: lagayhar
|
9 | 9 | ms.reviewer: lagayhar
|
10 | 10 | author: lgayhardt
|
11 |
| -ms.date: 05/25/2023 |
| 11 | +ms.date: 05/21/2024 |
12 | 12 | ms.custom: designer
|
13 | 13 | ---
|
14 | 14 |
|
15 |
| -# What is Azure Machine Learning designer(v2)? |
| 15 | +# What is Designer (v2) in Azure Machine Learning? |
16 | 16 |
|
17 |
| -Azure Machine Learning designer is a drag-and-drop UI interface for building machine learning pipelines in Azure Machine Learning Workspaces. |
| 17 | +Designer in Azure Machine Learning studio is a drag-and-drop user interface for building machine learning pipelines in Azure Machine Learning workspaces. |
18 | 18 |
|
19 |
| -As shown in below GIF, you can build a pipeline visually by dragging and dropping building blocks and connecting them. |
| 19 | +> [!IMPORTANT] |
| 20 | +> Designer in Azure Machine Learning supports two types of pipelines, which use classic prebuilt (v1) or custom (v2) components. The two component types aren't compatible within pipelines. **This article applies to Designer (v2) with custom components.** |
| 21 | +> |
| 22 | +> - **Custom components (v2)** let you wrap your own code as components, enabling sharing across workspaces and seamless authoring across Azure Machine Learning studio, CLI v2, and SDK v2 interfaces. It's best to use custom components for new projects, because they're compatible with Azure Machine Learning v2 and continue to receive new updates. |
| 23 | +> |
| 24 | +> - **Classic prebuilt components (v1)** support typical data processing and machine learning tasks like regression and classification. Azure Machine Learning continues to support the existing classic prebuilt components, but no new classic prebuilt components are being added. For information about classic prebuilt components and the v1 designer, see [Azure Machine Learning designer (v1)](v1/concept-designer.md?view=azureml-api-1&preserve-view=true). |
20 | 25 |
|
21 |
| -:::image type="content" source="./media/concept-designer/designer-drag-and-drop.gif" alt-text="GIF of a building a pipeline in the designer." lightbox= "./media/concept-designer/designer-drag-and-drop.gif"::: |
| 26 | +The following animated GIF shows how you can build a pipeline visually in Designer by dragging and dropping assets and connecting them. |
22 | 27 |
|
| 28 | +:::image type="content" source="./media/concept-designer/designer-drag-and-drop.gif" alt-text="GIF of a building a pipeline in the designer." lightbox= "./media/concept-designer/designer-drag-and-drop.gif"::: |
23 | 29 |
|
24 |
| ->[!Note] |
25 |
| ->Designer supports two types of components, classic prebuilt components (v1) and custom components(v2). These two types of components are NOT compatible. |
| 30 | +## Asset libraries |
26 | 31 |
|
27 |
| ->Classic prebuilt components support typical data processing and machine learning tasks including regression and classification. Though classic prebuilt components will continue to be supported, no new components will be added. |
28 |
| -> |
29 |
| ->Custom components allow you to wrap your own code as a component enabling sharing across workspaces and seamless authoring across the Azure Machine Learning Studio, CLI v2, and SDK v2 interfaces. |
30 |
| -> |
31 |
| ->For new projects, we highly recommend that you use custom components since they are compatible with AzureML V2 and will continue to receive new updates. |
32 |
| -> |
33 |
| ->This article applies to custom components.. |
| 32 | +Designer uses building blocks from Azure Machine Learning asset libraries to create pipelines. The asset libraries include the following pipeline building blocks: |
34 | 33 |
|
| 34 | + - [Data](concept-data.md) |
| 35 | + - [Models](how-to-manage-models.md?view=azureml-api-2&preserve-view=true&tabs=cli) |
| 36 | + - [Components](concept-component.md) |
35 | 37 |
|
36 |
| -## Assets |
| 38 | +The **Data**, **Model**, and **Component** tabs on the left side of Designer show assets in your workspace and in all Azure Machine Learning [registries](./how-to-share-models-pipelines-across-workspaces-with-registries.md) that you have access to. |
37 | 39 |
|
38 |
| -The building blocks of pipeline are called assets in Azure Machine Learning, which includes: |
39 |
| - - [Data](./concept-data.md) |
40 |
| - - [Model](how-to-manage-models.md?view=azureml-api-2&preserve-view=true&tabs=cli) |
41 |
| - - [Component](./concept-component.md) |
| 40 | +:::image type="content" source="./media/concept-designer/asset-library.png" alt-text="Screenshot of the asset libraries filtered for one registry." lightbox= "./media/concept-designer/asset-library.png"::: |
42 | 41 |
|
43 |
| -Designer has an asset library on the left side, where you can access all the assets you need to create your pipeline. It shows both the assets you created in your workspace, and the assets shared in [registry](./how-to-share-models-pipelines-across-workspaces-with-registries.md) that you have permission to access. |
| 42 | +To view assets from specific registries, select the **Registry name** filter. The assets you created in your current workspace are in the **Workspace** registry. The assets provided by Azure Machine Learning are in the **azureml** registry. |
44 | 43 |
|
45 |
| -:::image type="content" source="./media/concept-designer/asset-library.png" alt-text="Screenshot of the asset library." lightbox= "./media/concept-designer/asset-library.png"::: |
| 44 | +To learn how to create data and component assets in your workspace, see the following articles: |
46 | 45 |
|
| 46 | +- [Create and manage data assets](./how-to-create-data-assets.md) |
| 47 | +- [Create and run pipelines using components](./how-to-create-component-pipelines-ui.md) |
47 | 48 |
|
48 |
| -To see assets from a specific registry, select the Registry name filter above the asset library. The assets you created in your current workspace are in the registry = workspace. The assets provided by Azure Machine Learning are in the registry = azureml. |
| 49 | +## Pipelines |
49 | 50 |
|
50 |
| -Designer only shows the assets that you created and named in your workspace. You won't see any unnamed assets in the asset library. To learn how to create data and component assets, read these articles: |
| 51 | +You can use Designer to visually build pipelines with your assets. You can either create new pipelines or clone and build on existing pipeline jobs. |
51 | 52 |
|
52 |
| -- [How to create data asset](./how-to-create-data-assets.md) |
53 |
| -- [How to create component](./how-to-create-component-pipelines-ui.md#register-component-in-your-workspace) |
| 53 | +### New pipelines |
54 | 54 |
|
55 |
| -## Pipeline |
| 55 | +Selecting the **+** symbol under **New pipeline** at the top of the Designer screen creates a new pipeline to build from scratch. Be sure to select the **Custom** option so you can use custom components. |
56 | 56 |
|
57 |
| -Designer is a tool that lets you create pipelines with your assets in a visual way. When you use designer, you'll encounter two concepts related to pipelines: pipeline draft and pipeline jobs. |
| 57 | +:::image type="content" source="./media/concept-designer/new-pipeline.png" alt-text="Screenshot of selecting new pipeline with custom components." lightbox= "./media/concept-designer/new-pipeline.png"::: |
58 | 58 |
|
59 |
| -:::image type="content" source="./media/concept-designer/pipeline-draft-and-job.png" alt-text="Screenshot of pipeline draft and pipeline job list." lightbox= "./media/concept-designer/pipeline-draft-and-job.png"::: |
| 59 | +The two tabs under **Pipelines** at the bottom of the Designer screen show the existing **Pipeline drafts** and **Pipeline jobs** in your workspace. |
60 | 60 |
|
61 |
| -### Pipeline draft |
| 61 | +### Pipeline drafts |
62 | 62 |
|
63 |
| -As you edit a pipeline in the designer, your progress is saved as a **pipeline draft**. You can edit a pipeline draft at any point by adding or removing components, configuring compute targets, creating parameters, and so on. |
| 63 | +As you build a pipeline, Designer saves your progress as a pipeline draft. |
64 | 64 |
|
65 |
| -A valid pipeline draft has these characteristics: |
| 65 | +:::image type="content" source="./media/concept-designer/pipeline-draft-and-job.png" alt-text="Screenshot of pipeline draft list." lightbox= "./media/concept-designer/pipeline-draft-and-job.png"::: |
66 | 66 |
|
67 |
| -- Data assets can only connect to components. |
68 |
| -- Components can only connect to either data assets or other components. |
69 |
| -- All required input ports for components must have some connection to the data flow. |
70 |
| -- All required parameters for each component must be set. |
| 67 | +You can edit a pipeline draft anytime by adding or removing components, configuring compute targets, and setting parameters. |
71 | 68 |
|
72 |
| -When you're ready to run your pipeline draft, you submit a pipeline job. |
| 69 | +:::image type="content" source="./media/concept-designer/edit-pipeline.png" alt-text="Screenshot of a draft pipeline being edited." lightbox= "./media/concept-designer/edit-pipeline.png"::: |
73 | 70 |
|
74 |
| -### Pipeline job |
| 71 | +A valid pipeline draft has the following characteristics: |
75 | 72 |
|
76 |
| -Each time you run a pipeline, the configuration of the pipeline and its results are stored in your workspace as a **pipeline job**. You can go back to any pipeline job to inspect it for troubleshooting or auditing. **Clone** a pipeline job creates a new pipeline draft for you to continue editing. |
| 73 | +- Data assets can connect only to components. |
| 74 | +- Components can connect only to either data assets or to other components. |
| 75 | +- All required input ports for components must have some connection to the data flow. |
| 76 | +- All required parameters for each component must be set. |
77 | 77 |
|
78 |
| -## Approaches to build pipeline in designer |
| 78 | +When you're ready to run your pipeline draft, you save it and submit it as a pipeline job. |
79 | 79 |
|
80 |
| -### Create new pipeline from scratch |
| 80 | +### Pipeline jobs |
81 | 81 |
|
82 |
| -You can create a new pipeline and build from scratch. Remember to select the **Custom component** option when you create the pipeline in designer. |
| 82 | +Each time you run a pipeline, the pipeline configuration and results are stored in your workspace as a pipeline job. You can resubmit any past pipeline job, inspect it for troubleshooting or auditing, or clone it to create a new pipeline draft for further editing. |
83 | 83 |
|
84 |
| -:::image type="content" source="./media/how-to-create-component-pipelines-ui/new-pipeline.png" alt-text="Screenshot showing to select custom component." lightbox= "./media/how-to-create-component-pipelines-ui/new-pipeline.png"::: |
| 84 | +:::image type="content" source="./media/concept-designer/pipeline-job.png" alt-text="Screenshot of pipeline job list." lightbox= "./media/concept-designer/pipeline-job.png"::: |
85 | 85 |
|
86 |
| -### Clone an existing pipeline job |
| 86 | +You can edit and resubmit your pipelines. After submitting, you can see the lineage between the job you submit and the original job by selecting **Show lineage** on the job detail page. |
87 | 87 |
|
88 |
| -If you would like to work based on an existing pipeline job in the workspace, you can easily clone it into a new pipeline draft to continue editing. |
| 88 | +:::image type="content" source="./media/concept-designer/resubmitted.png" alt-text="Screenshot showing the resubmitted lineage after selecting Show lineage." lightbox= "./media/concept-designer/resubmitted.png"::: |
89 | 89 |
|
90 |
| -:::image type="content" source="./media/how-to-debug-pipeline-failure/job-detail-clone.png" alt-text="Screenshot of a pipeline job in the workspace with the clone button highlighted." lightbox= "./media/how-to-debug-pipeline-failure/job-detail-clone.png"::: |
| 90 | +### Cloned pipeline jobs |
91 | 91 |
|
92 |
| -After cloning, you can also know which pipeline job it's cloned from by selecting **Show lineage**. |
| 92 | +If you want to base a new pipeline on an existing pipeline job in the workspace, you can clone the job into a new pipeline draft to continue editing. |
93 | 93 |
|
94 |
| -:::image type="content" source="./media/how-to-debug-pipeline-failure/draft-show-lineage.png" alt-text="Screenshot showing the draft lineage after selecting show lineage button." lightbox= "./media/how-to-debug-pipeline-failure/draft-show-lineage.png"::: |
| 94 | +:::image type="content" source="./media/concept-designer/pipeline-clone.png" alt-text="Screenshot of a pipeline job in the workspace with the clone button highlighted." lightbox= "./media/concept-designer/pipeline-clone.png"::: |
| 95 | +After cloning, you can find out which pipeline job the new pipeline was cloned from by selecting **Show lineage**. |
95 | 96 |
|
96 |
| -You can edit your pipeline and then submit again. After submitting, you can see the lineage between the job you submit and the original job by selecting **Show lineage** in the job detail page. |
| 97 | +:::image type="content" source="./media/concept-designer/draft-show-lineage.png" alt-text="Screenshot showing the draft lineage after selecting Show lineage." lightbox= "./media/concept-designer/draft-show-lineage.png"::: |
97 | 98 |
|
98 |
| -## Next step |
| 99 | +## Related content |
99 | 100 |
|
100 |
| -- [Create pipeline with components (UI)](./how-to-create-component-pipelines-ui.md) |
| 101 | +- [Create a pipeline with components (UI)](./how-to-create-component-pipelines-ui.md) |
0 commit comments