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-deploy-models-timegen-1.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,11 +100,11 @@ These steps demonstrate the deployment of TimeGEN-1. To create a deployment:
100
100
1. Once you subscribe the workspace for the particular Azure Marketplace offering, subsequent deployments of the _same_ offering in the _same_ workspace don't require subscribing again. If this scenario applies to you, you'll see a **Continue to deploy** option to select.
101
101
1. Give the deployment a name. This name becomes part of the deployment API URL. This URL must be unique in each Azure region.
102
102
1. Select **Deploy**. Wait until the deployment is ready and you're redirected to the Deployments page.
103
-
1. Take note of the **Target URI** and the secret **Key**, which you can use to call the deployment and generate completions. For more information on using the APIs, see the [reference](#reference-for-timegen-1-deployed-as-a-serverless-api) section.
103
+
1. Take note of the **Target URI** and the secret **Key**, which you can use to call the deployment and generate completions. For more information on using the APIs, see the [reference](#reference-for-timegen-1-deployed-as-a-standard-deployment) section.
104
104
1. Select the **Test** tab to start interacting with the model.
105
105
1. You can always find the endpoint's details, URI, and access keys by navigating to **Workspace** > **Endpoints** > **Serverless endpoints**.
106
106
107
-
To learn about billing for the TimeGEN-1 model deployed as a standard deployment with pay per token offer billing, see [Cost and quota considerations for TimeGEN-1 deployed as a standard deployment](#cost-and-quota-considerations-for-timegen-1-deployed-as-a-serverless-api).
107
+
To learn about billing for the TimeGEN-1 model deployed as a standard deployment with pay per token offer billing, see [Cost and quota considerations for TimeGEN-1 deployed as a standard deployment](#cost-and-quota-considerations-for-timegen-1-deployed-as-a-standard-deployment).
108
108
109
109
### Consume the TimeGEN-1 model as a service
110
110
@@ -126,7 +126,7 @@ You can consume TimeGEN-1 models by using the forecast API.
126
126
|Exogenous Variables|Exogenous variables are external factors that can influence forecasts. These variables take on one of a limited, fixed number of possible values, and induce a grouping of your observations. For example, if you're forecasting daily product demand for a retailer, you could benefit from an event variable that may tell you what kind of event takes place on a given day, for example 'None', Sporting', or 'Cultural'. Or you might also include external factors such as weather.|[Exogenous Variables](https://aka.ms/exogenous-variables)|
127
127
|Demand Forecasting|Demand forecasting involves application of historical data and other analytical information, to build models that help predict future estimates of customer demand, for specific products, over a specific time period. It helps shape product road map, inventory production, and inventory allocation, among other things.|[Demand Forecasting](https://aka.ms/demand-forecasting-with-TimeGEN1)|
128
128
129
-
For more information about use of the APIs, visit the [Reference](#reference-for-timegen-1-deployed-as-a-serverless-api) section.
129
+
For more information about use of the APIs, visit the [Reference](#reference-for-timegen-1-deployed-as-a-standard-deployment) section.
130
130
131
131
### Reference for TimeGEN-1 deployed as a standard deployment
0 commit comments