We look forward to your participation!

Predictive Server Beta

Thanks for participating in the Predictive Server Beta for Alteryx associates! Find resources, ask questions, share ideas, and collaborate with fellow participants.

Not sure where to start? CLICK HERE.
Beta Walkthrough

Missed the live session? No problem! Check out the recorded version for an in-depth overview on how to participate.

Watch Video

Couple of Wonky UX Items

Alteryx Alumni (Retired)

Have just been working through a couple of new models on the server: 


- First up: the classic Alumni donation dataset (that we use in the Model Comparison Tool Sample on the Public Gallery). Performed well, no issues at all. Nice resulting model, albeit for a tiny dataset. 


- Next: I tried the classic Telco churn dataset (https://www.kaggle.com/kennydevarapalli/customer-churn-prediction-made-easy) and spotted a couple of small UX items that are worth correcting: 


First, when you import data from a CSV, you get a message saying 'We're bringing in your 1 files[sic]. After you go to the next step you can't add anymore[sic] files. Make sure to bring in all files now.'  -except I couldn't see a way to add more files at this stage?


Second - when the AutoModel page is reached it says 'Select Run to start the modeling process.' but it seems that the process starts automatically?


(pics attached)


Next feedback - the model (Extra Trees classifier) did well - as well as Logistic Regression in the Kaggle notebook above (which required a lot of manual processing), but adding in the holdout data took *ages* relative to all the other steps - any reasons why? 


Final feedback: the number of features used in this model was quite high (58 in total, vs around 20 in the original dataset) - what's the strategy for ensuring that we don't overfit as part of the model building/evaluation? It's not clear from the model pipeline image what feature selection strategy we use to make sure that we're not throwing everything into the kitchen sink before stirring the algos.....


Thanks all!

Nick Jewell | datacurious.ai