by smokers » Thu Jul 27, 2017 6:20 am
The scope of the above table is to help me decide wether a certain level value will be in a certain interval or not, thus deciding the min and max of history differences/values.
I have setup ranges from -/+ 5 to -/+ 45. This is the only parameter that is changing from a prediction command. After each range setup change the prediction is performed again so I have proper prediction process. The logic would be to narrow the field on which the predicted values would be. Also each prediction has also a backtrack percent as setup in the prediction options, thus giving some sort of confidence values.
Therefore, if starting from a wide range , -/+ 45 then switching to narrow ranges, I can expect at some point to find some limits. A simple scenario/example would be: if a value will be in the range of -/+ 45 but not in range -/+ 20, I expect that when having the predictions on -/+ 20 it will show me > + 20 OR < -20, and also to exist linearity in predictions. For the example below I will know that my ranges will be above + 20 or below -20. Having these ranges of values, I can go then to segmentation table and find the segmentation combos that will give me values in the appropriate expected values.
However as seen in the attachment picture, row 5 for example: the prediction conflict seems to be obvious.