Ask any data scientist in your workplace. Any Data Science Supervised Learning ML/AI project will go through many steps and iterations before it can be put in production. Starting with the question of “Are we solving for a regression or classification problem?”
Every step above has a myriad of challenges. Today, all the above are very painful to do, even for the best data scientists in a team. If your data has 200 columns are features that are a mix of numeric, categorical and text data, the problem becomes exponentially hard. Even the savvy data scientists avoid running exhaustive tests, procedures and scientific methods and try stick to basic stuff or may decide to automate one or two steps above. The most automation you get today is available from a few cloud/SAAS vendors – they allow you to choose the algorithm with your base features and it will do some repetitive hyper-parameter tuning to get you the best model that you can use in production.
In reality, to do above right, it takes a lot more other than repetitive model tuning or using one algorithm. We are not even talking about a big data problem – even with just 1 million rows, you could be spending days, weeks to a month to get an AUC measure of 0.94 or a really low LOG LOSS with no overfitting, only to find your next batch of data has you chasing this problem all over again.
What if you had a tool that solves the above end-to-end problem using AI?
Driverless AI from H2O (AI to do AI)
Load your ground truth CSV file or point to your data source and push a button. The tool does all the steps like feature engineering, evolution, etc., multiple algorithms on GPUs, etc., etc., under the hood and then outputs the code to put in production, all with an in-depth explainability report! How about getting to the leaderboard in a few minutes or an hour or so with a tool with Kaggle Grandmaster smarts?
A screenshot from above where I was building a classification model with the “Wine Data Set” from UCI ML repository. With 15 seconds of running the classification, you can see the first XGBoost model itself gave me 0.9267 AUC showing me the variable importance in the screen. As Driverless AI evolves the features and runs multiple algorithms (running on 8 GPUs in this instance), you can watch how the AUC continuously is improved by tuning LightGBM, XGBoost, TensorFlow, GLM, etc., with hyper-parameter optimization and feature evolution.
The next time I ran it, I used LOGLOSS as my scorer, and it finished with 0.7876 based on my initial settings. The evolution of both models and features is shown in this graph below:
Driverless AI can run on Docker in your PC/Mac or one of EC2, Azure or GCP (with multiple GPUs!) instances in the cloud. After you load your data and finish the experiment, you can deploy a java or python scoring pipeline package at the end that has all the workflow inside. All one has to do is to call the hooks from your production application with your new data stream to get results – whether its’ binary outcome or numeric estimate/forecast or a multi-class decision.
Does Driverless AI replace Data Scientists?
Driverless AI makes Data Scientists super productive and helps them automate the end to end process – just like using any other automated tool to make mundane/repetitive tasks exciting and efficient. The data scientists have options to set up, monitor, influence the model building and override default decisions to accelerate model building or increase accuracy further. Driverless AI can also help data scientists to build models across multiple applications simultaneously and simplify the model deployment/lifecycle chore – even think about how much time a business can save solving various complex ML/AI problems and running it in production – all without the loss of explainability.