Advent of Code is back! Unwrap daily challenges to sharpen your Alteryx skills and earn badges along the way! Learn more now.
Free Trial

Weekly Challenges

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

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

Want to get involved? We're always looking for ideas and content for Weekly Challenges.

SUBMIT YOUR IDEA

Challenge #24: ARIMA Time Series

GeneR
Alteryx Alumni (Retired)

For those of you following along, thank you, you can find the solution to last week’s challenge (challenge #23) is HERE

 

This week’s challenge will use the predictive time series tool called ARIMA.  If you don’t have the predictive tools you can find the installer at http://downloads.alteryx.com/downloads.html look for the link to “Predictive tools only”.   The predictive tools in Alteryx execute the analytics in an open source application called ‘R’, the advantage of using Alteryx vs. R is that Alteryx provides a straight-forward user interface and eliminates the need to program directly in the R language.  If you want to read more about what is happening under the hood, here is a link to the Wiki on ARIMA. https://en.wikipedia.org/wiki/Autoregressive_integrated_moving_average

 

The use case:  A retailer would like to forecast how many units of a particular product will be purchased from their locations based on a historical trend.

 

The source data contains weekly data for 2012 and 2013 details how many units have been moved. Some of the data, however, is populated with NULL values. For the NULL values, please assign the monthly average. If the monthly average is also NULL, assign the annual average.

 

Objective:  Forecast the number of units that will be sold in the six weeks following the available data.

Have fun!

alex
11 - Bolide

I arrived at the same answer, but I'm not sure it's the best answer.  Based on the historical data, the forecast doesn't adjust for the drop off in sales each January.  How would we configure the tool for a better answer?  See spoilers below have the workflow plus what I came up when I exported to Tableau.

Spoiler

wk24.PNG
I added the the forecast back to the original data and came up with this chart in Alteryx.  See how forecast did not adjust to prior January trends.
wk24chartAlteryx.PNG

This is the data presented in Tableua plus the forecast solution that Tableau provided using the default settings.

Spoiler
wk24tb1.PNG

wk24tb2.PNG
TaraM
Alteryx Alumni (Retired)

Nice work @alex! Here is Gene's solution (attached and screenshot below):

Spoiler
2016-05-09 14_33_47-Alteryx Designer x64 - Week_24_Analytics_TimeSeries_solution.yxmd.png

 

Tara McCoy
SeanAdams
17 - Castor
17 - Castor

same solution as @GeneR & @TaraM - just structured slightly differently.

alexandra_hanna
7 - Meteor

Awsome! Forecasting made extremely easy with Alteryx. I've noticed  you fed 100 periods into forecast plot and I only did 6, do you know why we still get the same results?

NicoleJohnson
ACE Emeritus
ACE Emeritus

My solution! I like these Time Series predictive tools, pretty intuitive (especially for someone who never uses predictive analytics!)

 

Spoiler
Similar solution to the others, but I used a filter+join method rather than a join+formula method to replace the null values. However, I did discover when looking at others' solutions after I finished mine that there is an "AvgNo0" option in the summary tool, which would have eliminated having the filter to split off the Null values... will log that away for next time! :)
WeeklyChallenge24.JPG

 

estherb47
15 - Aurora
15 - Aurora
Spoiler
Spoiler
image.png
Laurap1228
11 - Bolide

Slightly different to the solution provided

 

Spoiler
challenge24.jpg
LordNeilLord
15 - Aurora

I've not really explored the TS Tools (except TS Filler), I ended up with the same solution as other however, my forecast scores are correct but the confidence scores are slightly out and I can't see why?

 

Spoiler
Weekly Challenge 24.png
nick_ceneviva
11 - Bolide

Solution attached.  Minor differences in the output for the confidence intervals as other people have noted.