Help with Time Series Tools

[Goran]

Hi everyone,

I'm trying to forecast data out 12 months using the Time Series tool set.  I've used TS filler to find any missing months, ARIMA as the forecasting method and TS Forecast to enable the forecasting.  Most of the data seems right, however the Period and and Sub-Period columns in the TS Forecast tool don't make any sense to me.  I've seen screenshots where these two columns are supposed to be the dates (Year and Month respectively), but I'll I'm getting is a seemingly random group of numbers: 

End of the Flow

Results

I've only include one Date measure in this data set prior to forecasting, but I still can't seem to get any idea what these numbers are:

Select Tool

TS Filler

ARIMA

TS Forecast

Any suggestions as to what I'm doing wrong would be greatly appreciated.  

Thank you!!

[IraWatt]

Hey @Goran,

Have you checked other options and set the start date?

[Goran]

Hi @IraWatt,

Yes I have in the ARIMA tool.  Sorry I forgot to include this screenshot (the options look a bit different than yours)

[IraWatt]

Hey @Goran,

That's very strange, when you right click on the TS forecast and click example, does the example workflow work alright?

Can you give some example dummy data to look at? 

Thanks,

Ira

[Goran]

@IraWatt, the workflow runs fine with predictable results up until I start using the Team Series tool and then nothing makes sense.  I assume the TS tools can't seem to read the date columns but I'm really not certain.  

[IraWatt]

@Goran the TS tools dont read the date column other then the TS Filler tool. The only thing that should matter is the start date

[leozhang2work]

Given you have chosen 2022 monthly as starting period, but Period in the output runs to almost 7000.

So my questions/guess without seeing the data:

1. how many rows do you have in the input data?
2. Is there grouping variable here?

[ddiesel]

Just wanted to chime in that this exact same thing happened to me when I was completing a weekly challenge recently. I played around with my workflow for awhile, but for the life of me I cannot recreate this issue. 

@Goran did you get this resolved yet?