Prediction Scope

There are multiple ways to define for which exact timestamps forecasts should be made. If not specified by the user, the default scope is determined based the forecasting horizon. A user can specify the prediction scope in several ways.

The first and most straightforward way is to define a range for which all timestamps should be included in the prediction scope.

A user can also define a specific number of timestamps, starting from a specified timestamp; this is done through the ‘CountFrom’ option.

A third option is to only define the number of timestamps that need to be included in the scope, in which case the initial timestamp for forecasting is automatically calculated based on the forecasting horizon; this is done through the ‘Count’ option.

Lastly, a user can specify a timestamp for which to start forecasting, in which case the number of forecasts will be automatically calculated based on the forecasting horizon; this is done through the ‘From’ option.

Where to set this in TIM connector and API

These settings can be set under the part

forecasting:
  configuration:

Ranges

predictionScope: 
  type: Ranges 
  ranges: 
  - from: 2011-01-01 00:00:00 
    to: 2011-12-31 23:00:00

Timestamps

predictionScope:
  type: Timestamps
  timestamps: [2011-01-01 00:00:00,2011-12-31 23:00:00]

Count From

predictionScope:
  type: CountFrom
  count: 39
  from: 2011-01-01 00:00:00    

Count

predictionScope:
  type: Count
  Count: 39

From

predictionScope:
  type: CountFrom
  From: 2011-01-01 00:00:00

Where to set this in TIM Studio

If you are doing a forecast from an existing model using the Forecasting screen, the only option available is CountFrom: image.png

If you are doing an experiment, the only option available is to use Ranges. image.png