PlanIQ Backtest data automation and Backtest data should come for all Actual periods as we import data let's suppose of 60 months for forecasting of 3 months then Backtest result come out for only past 3 months not for 60 months
We cannot produce backtest for all the history because it works differently.
Let's assume we have 24 months of historical data and we want to forecast 6 months ahead.
When algorithms are training, PlanIQ will take the 24 months of history and split it into two parts. First 18 months are being used for training. The latter 6 months are being withheld from training process and during the model creation, PlanIQ is actually "forecasting" this period. The "forecast" produced is then compared to 6 months of actuals that were kept on the side. This is how quality metrics are generated.
As a result, we cannot provide backtest information for the entire history.
However, if you write backtest results into the same module where you will be writing your forecasted values, you will be able to continuously track performance of PlanIQ forecast compared to your actuals - as you are adding more actuals and generating more forecasts.
Hope this helps.
Now I can combine grids in the user interface, it would be useful to be able to retain any row totals and/or sub totals when I filter on a List or Text formatted column. In the example below, if I filter on Spread=Even, I lose the sub-totals for the numeric monthly data by Entity.
Hello, We need the ability to apply both summary methods in the same line item in the Polaris engine as we do in the Classic engine as soon as possible, please! Thanks.
Problem: Not able to combo modules within a Grid where you start with a module with a full list, then try to combo with a subsetted module of that same list. Example: When creating a Combo Grid with a Properties module (full list dimension) and a Calculation module (subset of the same list dimension), you are unable toβ¦
