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
@@ -26,9 +28,9 @@ You can view and delete your in-product user data from Azure AI Gallery using th
26
28
27
29
You can view items you published through the Azure AI Gallery website UI. Users can view both public and unlisted solutions, projects, experiments, and other published items:
28
30
29
-
1.Sign in to the [Azure AI Gallery](https://gallery.azure.ai/).
30
-
2.Click the profile picture in the top-right corner, and then the account name to load your profile page.
31
-
3.The profile page displays all items published to the gallery, including unlisted entries.
31
+
1.Sign in to the [Azure AI Gallery](https://gallery.azure.ai/).
32
+
2.Click the profile picture in the top-right corner, and then the account name to load your profile page.
33
+
3.The profile page displays all items published to the gallery, including unlisted entries.
32
34
33
35
## Use the AI Gallery Catalog API to view your data
34
36
@@ -39,9 +41,9 @@ Catalog responses are returned in JSON format.
39
41
### Get an author ID
40
42
The author ID is based on the email address used when publishing to the Azure AI Gallery. It doesn't change:
41
43
42
-
1.Sign in to [Azure AI Gallery](https://gallery.azure.ai/).
43
-
2.Click the profile picture in the top-right corner, and then the account name to load your profile page.
44
-
3.The URL in the address bar displays the alphanumeric ID following `authorId=`. For example, for the URL:
44
+
1.Sign in to [Azure AI Gallery](https://gallery.azure.ai/).
45
+
2.Click the profile picture in the top-right corner, and then the account name to load your profile page.
46
+
3.The URL in the address bar displays the alphanumeric ID following `authorId=`. For example, for the URL:
@@ -53,12 +55,12 @@ You need an access token to view unlisted entities through the Catalog API. With
53
55
54
56
To get an access token, you need to inspect the `DataLabAccessToken` header of an HTTP request the browser makes to the Catalog API while logged in:
55
57
56
-
1.Sign in to the [Azure AI Gallery](https://gallery.azure.ai/).
57
-
2.Click the profile picture in the top-right corner, and then the account name to load your profile page.
58
-
3.Open the browser Developer Tools pane by pressing F12, select the Network tab, and refresh the page.
58
+
1.Sign in to the [Azure AI Gallery](https://gallery.azure.ai/).
59
+
2.Click the profile picture in the top-right corner, and then the account name to load your profile page.
60
+
3.Open the browser Developer Tools pane by pressing F12, select the Network tab, and refresh the page.
59
61
4. Filter requests on the string *catalog* by typing into the Filter text box.
60
-
5.In requests to the URL `https://catalog.cortanaanalytics.com/entities`, find a GET request and select the *Headers* tab. Scroll down to the *Request Headers* section.
61
-
6.Under the header `DataLabAccessToken` is the alphanumeric token. To help keep your data secure, don't share this token.
62
+
5.In requests to the URL `https://catalog.cortanaanalytics.com/entities`, find a GET request and select the *Headers* tab. Scroll down to the *Request Headers* section.
63
+
6.Under the header `DataLabAccessToken` is the alphanumeric token. To help keep your data secure, don't share this token.
62
64
63
65
### View user information
64
66
Using the author ID you got in the previous steps, view information in a user's profile by replacing `[AuthorId]` in the following URL:
@@ -90,9 +92,9 @@ For example:
90
92
91
93
This query displays only public entities. To view all your entities, including unlisted ones, provide the access token obtained from the previous section.
92
94
93
-
1.Using a tool like [Postman](https://www.getpostman.com), create an HTTP GET request to the catalog URL as described in [Get your access token](#get-your-access-token).
94
-
2.Create an HTTP request header called `DataLabAccessToken`, with the value set to the access token.
95
-
3.Submit the HTTP request.
95
+
1.Using a tool like [Postman](https://www.getpostman.com), create an HTTP GET request to the catalog URL as described in [Get your access token](#get-your-access-token).
96
+
2.Create an HTTP request header called `DataLabAccessToken`, with the value set to the access token.
97
+
3.Submit the HTTP request.
96
98
97
99
> [!TIP]
98
100
> If unlisted entities are not showing up in responses from the Catalog API, the user may have an invalid or expired access token. Sign out of the Azure AI Gallery, and then repeat the steps in [Get your access token](#get-your-access-token) to renew the token.
This topic describes how to choose the right hyperparameter set for an algorithm in Azure Machine Learning Studio (classic). Most machine learning algorithms have parameters to set. When you train a model, you need to provide values for those parameters. The efficacy of the trained model depends on the model parameters that you choose. The process of finding the optimal set of parameters is known as *model selection*.
18
20
19
21
@@ -36,7 +38,7 @@ You can define the parameter set at the model initialization step. The parameter
36
38
37
39

38
40
39
-
Alternately, you can define the maximum and minimum points of the grid and the total number of points to be generated with **Use Range Builder**. By default, the parameter values are generated on a linear scale. But if **Log Scale** is checked, the values are generated in the log scale (that is, the ratio of the adjacent points is constant instead of their difference). For integer parameters, you can define a range by using a hyphen. For example, “1-10” means that all integers between 1 and 10 (both inclusive) form the parameter set. A mixed mode is also supported. For example, the parameter set “1-10, 20, 50” would include integers 1-10, 20, and 50.
41
+
Alternately, you can define the maximum and minimum points of the grid and the total number of points to be generated with **Use Range Builder**. By default, the parameter values are generated on a linear scale. But if **Log Scale** is checked, the values are generated in the log scale (that is, the ratio of the adjacent points is constant instead of their difference). For integer parameters, you can define a range by using a hyphen. For example, "1-10" means that all integers between 1 and 10 (both inclusive) form the parameter set. A mixed mode is also supported. For example, the parameter set "1-10, 20, 50" would include integers 1-10, 20, and 50.
This article presents a reference implementation of a customer churn analysis project that is built by using Azure Machine Learning Studio (classic). In this article, we discuss associated generic models for holistically solving the problem of industrial customer churn. We also measure the accuracy of models that are built by using Machine Learning, and assess directions for further development.
Net# is a language developed by Microsoft that is used to define complex neural network architectures such as deep neural networks or convolutions of arbitrary dimensions. You can use complex structures to improve learning on data such as image, video, or audio.
18
20
19
21
You can use a Net# architecture specification in these contexts:
Download this easy-to-understand infographic overview of machine learning basics to learn about popular algorithms used to answer common machine learning questions. Algorithm examples help the machine learning beginner understand which algorithms to use and what they're used for.
18
20
19
21
## Popular algorithms in Machine Learning Studio (classic)
Once you deploy an Azure Machine Learning Studio (classic) predictive model as a Web service, you can use a REST API to send it data and get predictions. You can send the data in real-time or in batch mode.
18
20
19
21
You can find more information about how to create and deploy a Machine Learning Web service using Machine Learning Studio (classic) here:
Azure Machine Learning Studio (classic) gives you the tools you need to develop a predictive analytics model and then operationalize it by deploying it as an Azure web service.
17
19
18
20
To do this, you use Studio (classic) to create an experiment - called a *training experiment* - where you train, score, and edit your model. Once you're satisfied, you get your model ready to deploy by converting your training experiment to a *predictive experiment* that's configured to score user data.
In this quickstart, you create a machine learning experiment in [Azure Machine Learning Studio (classic)](what-is-ml-studio.md) that predicts the price of a car based on different variables such as make and technical specifications.
@@ -128,7 +130,7 @@ Now that the data is clean, we're ready to specify what features we're going to
128
130
129
131
## Define features
130
132
131
-
In machine learning, *features* are individual measurable properties of something you’re interested in. In our dataset, each row represents one automobile, and each column is a feature of that automobile.
133
+
In machine learning, *features* are individual measurable properties of something you're interested in. In our dataset, each row represents one automobile, and each column is a feature of that automobile.
132
134
133
135
Finding a good set of features for creating a predictive model requires experimentation and knowledge about the problem you want to solve. Some features are better for predicting the target than others. Some features have a strong correlation with other features and can be removed. For example, city-mpg and highway-mpg are closely related so we can keep one and remove the other without significantly affecting the prediction.
0 commit comments