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-auto-train-forecast.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -257,6 +257,8 @@ training:
257
257
258
258
---
259
259
260
+
<aname="forecasting-job-settings"></a>
261
+
260
262
### Forecast job settings
261
263
262
264
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:
536
538
> [!CAUTION]
537
539
> 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.
538
540
541
+
<a name="frequency--target-data-aggregation"></a>
542
+
539
543
#### Frequency and target data aggregation
540
544
541
545
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
763
767
764
768
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).
@@ -1313,6 +1321,8 @@ For a more detailed example, see the [demand forecasting with many models notebo
1313
1321
> [!NOTE]
1314
1322
> 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.
0 commit comments