APL problem with Cutting Strategy

[Former Member]

Hello,

I am working with APL (SAP Automated Predictive Library) to perform some analysis like  timeseries.

I wrote a sample Code to forecast 365 point  and I get this result

My input data range is from 10 to 63, I didn't know why i am getting forecasting data from -3 to 40.

I am confused and I don't know if I made a wrong thing or the training was not good.

Second, I insered APL/CuttingStrategy', 'sequential' in the config table

drop table FORECAST_CONFIG;
create table FORECAST_CONFIG like OPERATION_CONFIG_T;
insert into FORECAST_CONFIG values ('APL/Horizon', '365');
insert into FORECAST_CONFIG values ('APL/TimePointColumnName', 'DATE');
insert into FORECAST_CONFIG values ('APL/CuttingStrategy', 'sequential')

But when i take a look to Summury table i get ModelCuttingStrategy;sequential with no test

Is that any things to do to force the CuttingStrategy ?

Thanks in advance

Houssem

[marc_daniau · Accepted solution]

I have added the following row to my script and the cutting strategy was applied as expected ; after running the forecast the APL summary table says that the cutting strategy used is sequential, that estimation data set has 121 rows, validation 41 and test 41.

insert into FORECAST_CONFIG values ('APL/CuttingStrategy', 'sequential');

Make sure the APL input and output tables are cleaned up before doing a new APL call and double check that the cutting strategy parameter is inserted in the forecast_config table. 

As for the forecast you are showing in a graph, it seems the horizon is quite long. Try to bring more history. One thing I suggest you to do is to add the errors bars as shown in APL script: apl_forecast_with_error_bars.sql