We've recently made an accessibility improvement to the community and therefore posts without any content are no longer allowed. Please use the spoiler feature or add a short message in the message body in order to submit your weekly challenge.

Weekly Challenge

Solve the challenge, share your solution and summit the ranks of our Community!

Also available in | Français | Português | Español | 日本語

We're actively looking for ideas on how to improve Weekly Challenges and would love to hear what you think!

Submit Feedback

Challenge #24: ARIMA Time Series

11 - Bolide

As mentioned by others, slightly different values -- I changed "units" to double to be able to use the decimals in the average. Took me ages to realize I needed the TS forecast to visualize output...

16 - Nebula
16 - Nebula

Predictive can vex and perplex me... but here it is. Solution attached.


challenge_24 - Snip.PNG
12 - Quasar

Solution attached.

5 - Atom

Done! In my solution I first checked how the ARIMA performed against the ETS model by scoring each against the last 6 weeks of withheld data and then used the scored ARIMA model's settings instead of AUTO settings as these may be different to the scored model. This is perhaps the reason why some get slightly different results as the settings aren't set manually.

11 - Bolide

Slightly different results, partly because I changed Units to "double" to take the monthly/yearly average 

7 - Meteor

my solution is very similar to some of the others. time series forecast made easy! 




8 - Asteroid

That was a fun one! I might have to bring this tool combo into my daily work...

Week 24.png
8 - Asteroid

Also got some minor differences to the answer due to field type rounding I believe. Thanks!

16 - Nebula
16 - Nebula

Challenge Completed

11 - Bolide

Solution attached. The was my first exposure to the predictive tools, and it was very useful. I first did this problem a couple of months ago, and it worked fine. However, I was reviewing it recently on a new laptop, and the ARIMA tool was throwing an error. I see that a couple of others have encountered the error too.




I hope Alteryx can figure out how to reproduce and resolve it.