1. Select which series to evaluate by adding them to an Autotune template in the tab Home.
2. Select which settings to test in tab Config, table Autotune Settings
Several Setting templates can be set up, and run in the same Autotune batch.
3. Set everything together as Work items in tab Config, table Autotune Template, together with selecting period.
In the Autotune settings, an extract can be attached. The extract primarily works as a limiter. The approach to Autotune is to either test the best model under the most optimal conditions, this would result in the best model settings for the tested series, or the other approach would be to simulate the best model for the most realistic circumstances. In the extract you can limit when the forecast is to be done, for instance, Day Ahead and also when you had the last values of both energy and weather values.
The extract below shows an example of a basic extract to use to filter the use of forecast series and weather data for Autotune calculations. The highlighted areas in extract settings are the ones valid for Autotune.
4. Set up a bat-script to initiate and run Autotune via ConsoleUI.
Sample of content in bat-script to run Autotune:
"C:\inetpub\wwwroot\NewAiolosService\bin\AiolosConsoleUI-local.exe" /settingsfile:RunAutotune.autopar /configuration:Demo
5. Set up an Autopar-file to call for the Run Autotune bat-script. Settings in the Autopar-file can be:
RunAutotune.autopar | ||
Name |
Description |
Example |
/name |
Name of Autotune batch. Can be set freely. |
/name:AutotuneDemo |
/action |
To let ConsoleUI know that an Autotune run should be performed. |
/action:Autotune |
/selection |
The name of the Autotune template set in AFS-Config to run with selected work items. |
/selection:Demo-A |
/logfile |
Boolean to write logfile or not. If true, the logfile is created in folder <>\tmp\Autotune\ |
/logfile:True |
/successrate |
Sets a restriction that at least a fraction of the forecasts should have been created Can be used to protect from unsecure Autotune results. (E.g. Setting of 10, requires at least 10% of the forecasts to have been made to give a result.) |
/successrate:10 |
Sample of content in an autopar-file to run Autotune:
/name:AutotuneDemo
/action:Autotune
/selection:Demo-A
/logfile:True
/successrate:10
6. Set up a bat-script to apply the result from Autotune
Sample of content in a bat-file to Apply the Autotune result:
"C:\inetpub\wwwroot\NewAiolosService\bin\AiolosConsoleUI-local.exe" /settingsfile:AutotuneApply.autopar /configuration:Demo
7. Set up an Autopar-file for the Apply Autotune bat-script to call. Settings in the Autopar-file can be:
ApplyAutotune.autopar | ||
Name |
Description |
Example |
/name |
Name of Autotune Apply batch. Can be set freely. |
/name:AutotuneApplyDemo |
/action |
To let ConsoleUI know that an Autotune Apply run should be performed. |
/action:applyautotuneresult |
/file |
The name and folder of the result file. |
/file:<>\tmp\Autotune\Demo-A.at |
/type |
Decides if to update or create a new forecast model, if a forecast model already exists in the given model place. (E.g. update to change an already existing model, or create to create a new model if one already exists in the given model place.) |
/type:update or /type:create
|
/successrate |
Sets a restriction that at least a fraction of the forecasts should have been created Can be used to protect from applying unsecure Autotune results. (E.g. Setting of 10, requires at least 10% of the forecasts to have been made to give a result.) |
/successrate:10 |
Sample of content in an autopar-file to Apply the Autotune result:
/name:AutotuneApplyDemo
/action:applyautotuneresult
/file:<>\tmp\Autotune\Demo-A.at
/type:update
/successrate:10