CorrectStubPeriod: CorrectStubPeriod;
CorrectStubPeriod: Prognoz.Platform.Interop.Ms.CorrectStubPeriod;
The CorrectStubPeriod property determines parameters of date extension for modeling problem if its periods go beyond source periods.
By default periods cannot be extended, and the user is given a warning that modeling problem periods do not correspond to its sources, that is, CorrectStubPeriod is set to CorrectStubPeriod.NotCorrect.
On using CorrectStubPeriod only modeling problem sources, being time series databases, are taken into account.
If modeling problem calculates models for which their proper calculation periods are set, the data is loaded taking into account model periods. For example, there are following sources:
The TSDB1 time series database with the period 2010 - 2020.
The TSDB2 time series database with the period 2005 - 2015.
The TSDB3 time series database with the period 2007 - 2017.
The TSDB4 time series database with the period 2004 - 2021.
All sources contain data by annual frequency and the same attributes: Country and Indicator.
There is model which on modeling problem calculation will be calculated by its proper periods:
{TSDB4!Albania|BCA[t]} = {TSDB1!Albania|BCA[t]} +{TSDB2!Albania|BCA[t]}+ {TSDB3!Albania|BCA[t]}
Series used in the expression contain the following data:
| Series/Date | 2005 | 2006 | 2007 | 2008 | 2009 | 2010 | 2011 | 2012 | 2013 | 2014 | 2015 | 2016 | 2017 | 2018 | 2019 | 2020 |
| TSDB1!Albania|BCA | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | |||||
| TSDB2!Albania|BCA | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | |||||
| TSDB3!Albania|BCA | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 |
Consider an example of forming model periods:
| Week periods | How CorrectStubPeriod is used | How loading periods will be determined, how model will be calculated |
| Identification start - 2004 Identification end - 2021 End 2021 |
NotCorrect | The warning that calculation periods are out of source periods (TSDB1, TSDB2, TSDB3) will be received. |
| CorrectProblemPeriod | Calculation/loading periods will be straightened by crossing period of the 2010 - 2015 periods. | |
| CorrestStubPeriod | Source periods will be extended, the loading period is 2004 - 2021. |
Total series when CorrectStubPeriod = CorrectProblemPeriod:
| Year | 2010 | 2011 | 2012 | 2013 | 2014 | 2015 |
| Total series | 11 | 14 | 17 | 20 | 23 | 26 |
Total series when CorrectStubPeriod = CorrestStubPeriod:
| Year | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| Total series | 1 | 2 | 4 | 6 | 8 | 11 | 14 | 17 | 20 | 23 | 26 | 17 | 19 | 9 | 10 | 11 |
Similar results can be obtained if autoperiods are used. For example, if Today is considered as 2014 year, the autoperiods can be the following:
Identification start: from identification end - 17.
Identification end: today + 7.
End: today + 7.
Identification start: today - 10.
Identification end: from identification start + 17.
End: from identification end + 0.
The property use is given in the example for IMsProblemCalculationSettings.DefaultLevel.
See also: