Skip to content

Commit f507944

Browse files
Address bookmark warnings.
1 parent ca986c8 commit f507944

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

articles/machine-learning/how-to-auto-train-forecast.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -257,6 +257,8 @@ training:
257257

258258
---
259259

260+
<a name="forecasting-job-settings"></a>
261+
260262
### Forecast job settings
261263

262264
Forecasting tasks have many settings that are specific to forecasting. The most basic of these settings are the name of the time column in the training data and the forecast horizon.
@@ -536,6 +538,8 @@ forecasting:
536538
> [!CAUTION]
537539
> Padding can impact the accuracy of the resulting model, since you introduce artificial data to avoid training failures. If many of the series are short, you might also see some impact in explainability results.
538540

541+
<a name="frequency--target-data-aggregation"></a>
542+
539543
#### Frequency and target data aggregation
540544

541545
Use the frequency and data aggregation options to avoid failures caused by irregular data. Your data is irregular if it doesn't follow a set cadence in time, like hourly or daily. Point-of-sales data is a good example of irregular data. In these cases, AutoML can aggregate your data to a desired frequency and then build a forecasting model from the aggregates.
@@ -763,6 +767,8 @@ az ml job show -n $run_id --web
763767

764768
After the job is submitted, AutoML provisions compute resources, applies featurization and other preparation steps to the input data, and begins sweeping over forecasting models. For more information, see [forecasting methodology](./concept-automl-forecasting-methods.md) and [model search](concept-automl-forecasting-sweeping.md).
765769

770+
<a name="orchestrating-training-inference-and-evaluation-with-components-and-pipelines"></a>
771+
766772
## Orchestrate training, inference, and evaluation with components and pipelines
767773

768774
[!INCLUDE [preview v2](includes/machine-learning-preview-generic-disclaimer.md)]
@@ -1036,6 +1042,8 @@ You can find the metrics results in *./named-outputs/metrics_results/evaluationR
10361042

10371043
For more information on rolling evaluation, see [Inference and evaluation of forecasting models](concept-automl-forecasting-evaluation.md).
10381044

1045+
<a name="forecasting-at-scale-many-models"></a>
1046+
10391047
## Forecast at scale: many models
10401048

10411049
[!INCLUDE [preview v2](includes/machine-learning-preview-generic-disclaimer.md)]
@@ -1313,6 +1321,8 @@ For a more detailed example, see the [demand forecasting with many models notebo
13131321
> [!NOTE]
13141322
> The many models training and inference components conditionally partition your data according to the `partition_column_names` setting so that each partition is in its own file. This process can be very slow or fail when data is very large. In this case, we recommend partitioning your data manually before running many models training or inference.
13151323

1324+
<a name="forecasting-at-scale-hierarchical-time-series"></a>
1325+
13161326
## Forecast at scale: hierarchical time series
13171327

13181328
[!INCLUDE [preview v2](includes/machine-learning-preview-generic-disclaimer.md)]

0 commit comments

Comments
 (0)