Predicting earthquake damages with Azure ML Workspace
In the last few years, artificial intelligence (AI) has become more and more prevalent and powerful. Many speeches around AI nowadays explain how these technologies can be benefitted to predict stock prices and create value for an organization. In fact, even the online courses that are meant to educate newcomers in the field are focusing on the financial benefits of AI.
In today’s materialistic world, I would like to focus on how the very same technologies can be benefitted to predict natural disasters and eventually increase survival rates and improve quality of life.
The disasters caused by natural phenomena have been present all along human history; nevertheless, their consequences are greater each time. This tendency will not be reverted in the coming years; on the contrary, it is expected that natural disasters will increase in number and intensity due to the global warming.
According to world statistics, the increase in the number of world disasters between the decades of 1987-1996 and 1997-2006 was 60% (going from 4,241 to 6,806), whereas the number of dead people during these periods increased a hundred percent (it went from more than 600,000 to more than 1,200,000). Source: Using Machine Learning for Extracting Information from Natural Disaster News Reports
More than nine million Australians have been impacted by a natural disaster or extreme weather event in the past 30 years. And the number of people affected annually is expected to grow, as the intensity, and in some areas the frequency of these events continues to grow. These costs include significant, and often long-term, social impacts, including death and injury, as well as impacts on employment, education, community networks, health, and wellbeing. Source: Natural Disasters in Australia
Humans have been trying to predict earthquakes at least since first-century China, when they used this device: like a jar, with metal dragons facing each compass direction, and surrounded by frogs with their mouths open. If the ground shook somewhere in the region, the metal ball in the dragon’s mouth would drop out into the frog’s mouth, roughly indicating the direction of the earthquake. Many similar predictions actually sounded reasonable, but after some research, those things were concluded to be natural phenomena with little to no correlation to earthquakes. Source: 7 ways humans have tried to predict earthquakes
AI however relies solely on data.
Multiple researchers are creating their own applications to predict earthquakes and aftershocks. Moreover, these systems also monitor aging infrastructure. AI can detect deformations in structures, which can be used to reduce the damage caused by collapsing buildings and bridges, or subsiding roads.
In this article, you will read about a real-life example of saving more lives with Artificial Intelligence: how to examine a natural disaster, and how to use that observation to save more lives.
In April, 2015 there was an earthquake with 7.8 magnitude, and an epicenter in the Gorkha District of Nepal. The disaster killed almost 9000 people and injured 22000. This horror was in most cases caused by the collapsed buildings in the earthquake.
Many data scientists have been working hard to improve the survival rate of the next earthquake. Our mission is to build a predictive machine learning model to investigate and understand the risks of damage in case of another natural disaster. The result of our findings is available for mitigation of which buildings might need strengthening before the next earthquake. By this not only the memorial buildings and homes could be saved, but also thousands of lives.
What is Data Science?
Data science is really just an umbrella term, it refers to figuring out ways to study and solve problems with data. To do that effectively, you need a range of skills: computer science, mathematics, statistics and whatever domain you are in, you need expertise in that domain. For example, for this project you might need to understand architecture and some kind of forecasting of natural disasters.
Data scientists are absolutely obsessed with data. The first thing we always do if we have a problem to solve, that we are looking around for all the possible data sources which we can bring to bear on this problem.
Now we have to figure out how do we acquire the data, how do we get it into some system, such as a data warehouse, Databricks or maybe Azure Machine Learning Studio.
But of course, the data is not always arriving in the shape we hoped for, so we might have to spend a lot of time on transformation, cleaning, re-shaping and so on. Then we need to understand the relationships in the dataset, like, what is the data trying to tell us about the problem we are trying to solve, which of the features or variables actually seem to be useful, and which may just add noise to the situation.
And finally, we are going to do some predictive analytics or modeling, and through that we hope to deliver value back to our customers or end-users, which helps them drive decisions and make them even better also.
I often see confusion around the term Machine Learning and AI. Let me clarify how these are connected to each other.
Artificial intelligence (AI) is a technique that enables computers to mimic human intelligence. It includes machine learning, which is a subset of artificial intelligence. Machine Learning includes techniques such as deep learning which are neural networks that permit a machine to train itself. With Machine Learning techniques we can enable machines to improve at tasks with experience.
But how a machine can be trained?
Learning can be defined as “the process of knowledge acquisition. Humans learn differently, but all involve experience, whilst human have the ability to reason, computers do not have that ability therefore they learn through algorithms.
Supervised learning generally includes a set of labels along with data, in here “the algorithm generates a function that maps inputs to desired outputs”. This learning type commonly used for classification and regression problems, for instance, it can be used for classifying whether a building is in danger when another earthquake comes.
Unsupervised learning does not deal with labels, only includes input data, meaning that the model has to find structure or patterns within the dataset itself. Common techniques include clustering and dimensionality reduction. Unsupervised learning technique can be used for instance in speech recognition.
Reinforcement learning is “where the algorithm learns a policy of how to act given an observation of the world. Every action has some impact in the environment, and the environment provides feedback that guides the learning algorithm”. This technique is commonly used in autonomous driving or game development.
Machine learning models generally have an iterative nature, involving four stages. Let me sketch up the main steps you need to take while working with a machine learning model:
- Prepare data: We pull in the data into some system and prepare it for training. Data can come from various sources, generally speaking – in machine learning solutions-the more reliable data the better. Prepare data step involves data cleaning, data exploration and splitting.
- Exploration of the data helps developers understand the dataset and its structure. It is crucial to interpret what data is available and how it can be utilized for a model, this stage typically include checking the data type and understanding different rows and columns within the dataset.
- After dataset is understood, irrelevant observations can be deleted as those would only add noises to the dataset. Typically, datasets include missing values and duplicates, whilst duplicates are generally get removed, to avoid a biased model, missing values are simply not understood by many algorithms.
- and splitting (to train and test data, train data will be used to train the model, and we can also evaluate our model with the test data)
- Train model: Training a machine learning model starts with choosing, which specific algorithm we want to configure our model with.
- Raw data is transformed into features that the model can understand or in other words, feature engineering is done, which can include feature generation often used to make machine learning models more reliable.
- After the goal of what the model will be used for is clear, available datasets are known together with the learning task the right algorithm must be selected. Typically, machine learning problems can be solved in many different ways, therefore, multiple solutions are usually developed and compared for the same problem to find the most feasible solution.
- There are several approaches to each of these steps, but selecting the right algorithm is a rather complex task, but Microsoft provides us a cheat sheet which we can review before getting started..
- Score model: this is the process of generating values based on a trained machine learning model. The generic term “score” is used, rather than “prediction,” because the scoring process can generate so many different types of values: list of recommended items, numeric values, a predicted outcome and so on, depending on what data you provide, and how you train the model.
- Evaluate model: evaluation basically is metrics that tell you how good your model works, for example, the accuracy of a predictive model means that how well does it predict the future.
And this is a never ending iteration process as when we find during evaluation that our model doesn’t work well enough, you would start over by reviewing the data, possibly further feature engineering and hyper parameter tuning to achieve better performance!
What we want to do is to build a predictive model which is able to answer our question, by learning from the data we provide: Which buildings are in danger when another earthquake comes?
Predictive analytics deal with designing statistical models or machine learning models that predict. These models are calibrated on past data or experience (features and labels), they learn from it to predict the future.
Azure ML Workspace
Teaching a machine might sound like some kind of black magic, but thanks to the tools provided by Azure, you have the chance to easily get started with machine learning, and learn about the different training algorithms, and then understand what the result tells you with the use of Azure Machine Learning.
This web experience brings together data science capabilities and ML assets into a single web pane that streamlines machine learning workflows. It is considered as the top-level resource providing a centralized place to work with all the artifacts required to build a solution. The workspace keeps history of all training runs, including logs, metrics, output and snapshot of scripts.
Access machine learning for all skills to boost productivity
- Rapidly build and deploy machine learning models using tools that meet your needs regardless of skill level.
- Use the no-code designer to get started with machine learning or use built-in Jupyter notebooks for a code first experience.
- Accelerate model creation with the automated machine learning UI and access built-in feature engineering, algorithm selection, and a lot more features to develop high accuracy models.
Operationalize at scale with robust MLOps
- MLOps or DevOps for machine learning, streamlines the machine learning lifecycle, from building models to deployment and management.
- Use ML pipelines to build repeatable workflows and use a rich model registry to track your assets.
- Manage production workflows at scale using advanced alerts and automation capabilities.
Take advantage of built-in support for popular open-source tools and frameworks for model training and inferencing
- Use familiar frameworks like PyTorch, TensorFlow, scikit-learn and more
- Choose the development tools that best meet your needs, including popular IDEs, Jupyter notebooks and CLIs or languages like Python and R.
Build responsible AI solutions on a secure trusted platform
- Access state-of-the-art technology for fairness and model transparency. Use model interpretability for explanations about predictions, to better understand model behavior.
- Reduce model bias by applying common fairness metrics, that is automatically making comparisons and using recommended mitigations.
- Enterprise-grade security with role-based access control, and virtual network support to protect your assets.
- Audit trail, quota and cost management capabilities for advanced governance and control.
Azure Machine Learning Workspace is distributed into three components: Manage, Assets, Author.
Create new compute with memory optimized standard CPU. Provide a name, on the advanced you can schedule start up and shut down time. It is a good idea to shut it down, so it wont charge you if you forget to switch if off yourself.
You can connect different Azure services to your Azure ML Workspace, for example Synapse workspace.
You can create labeling projects with image classification or object detection here.
Here you can import data into the workspace, so it is available to use for your pipelines. You can upload the data from your own pc, a datastore, a web file or open source, these physically are stored in Azure Storage. These datasets are versioned, so you can easily monitor the changes in the data. Statistics and graphics give a good insight, you can profile the data as you upload it, or later in the overview.
When we run something within the workspace, those runs can be monitored here.
Here you will find your custom components created as building blocks for your ml projects, which is a self-contained piece of code that does one step in a machine learning pipeline. Components are the building blocks of advanced machine learning pipelines. Components can do tasks such as data processing, model training, model scoring, and so on.
This is where you can see the available pipelines for your jobs, these can be triggered from connected services too, with eg. Synapse.
There are different setups that contain several already installed packages, rest assured you would find your favorite ones here too: Scikit-learn, TensorFlow and more.
Deployed models are visible here. Models can be deployed to Azure Container instances, Azure Kubernetes Service (AKS), to (FPGA), and to an Azure IOT edge device as a module
The dedicated endpoint for a deployed model where you can leverage the capabilities of your deployed model through an API call in your applications
Notebooks: Understand data
Azure ML Notebooks is a fully managed cloud-based code-first environment for data scientists to author models, transform and prepare data with Python or R. You can also build Automated ML (AutoML) experiments from the notebooks. It enables you to collaboratively debug models and share notebooks within the boundaries of the workspace. Managed VM form-factor ensures compliance with enterprise security requirements. They are pre-configured with up-to-date Machine Learning packages, GPU drivers and everything data scientists need to save time on setup tasks.
To demonstrate how Notebooks works, let’s have a first view on the data provided by The Central Bureau of Statistics, they collected the largest dataset, which contains valuable information about numerous properties (area, age, demographic statistics and more) of buildings that have collapsed in earthquakes in Nepal. Download the data from here.
Create a new Azure Machine Learning Workspace and when the deployment is done, go to the resource and click on the Launch now button at the Overview page. You should see a panel on the main page with the Notebooks, AutoML and Designer options.
Start the Notebooks.
The folder structure is on the left, here you can create new files and folders. From the Samples tab, you can import a project built by Microsoft, to get started. On the left side, Files tab, create a new file, and give it a name – make sure the extension is .ipynb. The compute can be created from here as well, it will be used for running our code. To create one, you can press the + sign next to Compute on the top of the notebook, or at the icon in the bottom left side of the menu – as shown with the arrow on the picture below.
I use Python’s Pandas package. Pandas stands for “Python Data Analysis Library”, it has a lot of great functions to use on objects called dataframes. Dataframes are interactive tables, which you can easily manipulate and transform.
import pandas as pd
dfValues = pd.read_csv(“values.csv”)
The display function shows us how many columns and rows we have in our dataset, and you also get an overview of the stored values. Also, we can get the type of each columns using this code:
The field of statistics is often misunderstood, but it plays an essential role in our everyday lives. Statistics, done correctly, allows us to extract knowledge from the complex, and difficult real world. A clear understanding of statistics and the meanings of various statistical measures is important to distinguishing between truth and misdirection.
When we have a set of observations, it is useful to summarize features of our data into a single statement called a descriptive statistic. As their name suggests, descriptive statistics describe the quality of the data they summarize. It is useful when you have so much data to observe, like we have here, and instead of scrolling through and try to understand just like by looking at it, we can use some nice python functions.
What we can see here in the first row that how many not-null values are in the column (as Python’s describe() function counts only the not empty fields), and by this information we can be sure that each of the rows in each of the observed columns hold not-null values. This is important, otherwise it gives a lot of noise into any calculations and predictions, for example calculating mean:
(0 + 1+ 2+ 3) / 4 = 1,5
(1 + 2 +3) / 3 = 2
Have you also noticed the number of columns of the results? The describe() function returns information only about the numerical columns, and removes the other types from the observation. For simplicity, we are not going to discuss how to use these features during modelling.
Another observation you can make here is the min and the max values for each column. For example, the buildings have minimum 1 and maximum 9 floors, or that the age of the building is at least 0 and can go up to 995.
Another important observation is at the columns starting with has_, that it’s minimum is 0, and the maximum is 1. I could assume, that these are probably true or false, but I cannot be sure about it right now. We can make a check on for example this has_superstructure_adobe_mud column with the use of the unique function.
This shows the distinct values of the chosen column, so now we are sure, that these columns hold true and false values.
Descriptive statistics fall into two general categories: the measures of central tendency and the measures of spread. As we have used the describe() function, now we have some important statistics for the dataset.
The mean is a descriptive statistic (falls into the central tendency category) that looks at the average value of that specific column. The measures of spread (also known as dispersion) answer the question, “How much does my data vary?”
The standard deviation is also a measure of the spread of your observations but is a statement of how much your data deviates from a typical data point. That is to say, the standard deviation summarizes how much your data differs from the mean.
For standard deviation we can also use a visualization tool – just in case, to have a graphical overview of the data. For example, let’s observe the age.
In the case of the we can see the mean as a blue box, and the age of most of the buildings are between 0 and 200 years, which are very close to the mean, and there are some outlier values, with around 995 years – which are probably memorial buildings that have collapsed in the earthquake.
The label column is the damage_grade, which indicates how high is the risk of damage for the buildings in case of another earthquake (1 – low, 2 – medium, 3 – high). So our model is going to predict the risk by learning from “experience” data. We can further investigate the label column, by running the following code.
You can see that there are 3 different values in the damage_grade column, and also the number of features that are available for each of the labels. The best case would be if these numbers were quite close to each other, though it is visible that the number 2 has much more examples than the label 1 and 3. This is a problem, because if the model is trained on more examples with label 2, it more often returns the label 2 even when the risk is supposed to be high or low. We shouldn’t train the model on unbalanced data, so we are going to deal with this issue when we start the transformation and preparation of the data before training.
When we prepare for the work with the predictive model, we can already have a good understanding of which features we keep, and which ones we leave out. For now, we can conclude the information we learned with statistics and some investigations. If you want to learn more about your data, create a profiled dataset.
Conclusion of the dataset:
- 10000 rows
- 41 columns: 3 ids, 6 numerical, 8 non-numerical, 23 true/false, 1 label column
- age (int): age of the building in years
- area (int): area of the building in m2
- height (int): height of the building in m
- count_ﬂoors_pre_eq (int): number of ﬂoors in the building before the earthquake.
When two buildings are the same height, the one with less floors has higher damage risk, because the construction is weaker than another one that has more floors.
- count_families (ﬂoat): number of families that live in the building.
- has_secondary_use (binary): indicates if the building was used for secondary purpose
- square (float): square root of the area
- difference (float): difference between the square root of the area and the height of the buildings
The next 10 features are indicating which material was used for building the superstructure. The first one is the weakest with high risk of damage, and the last one is the strongest with low risk of damage.
- has_superstructure_bamboo (binary): Bamboo
- has_superstructure_mber (binary): Timber
- has_superstructure_adobe_mud (binary): Adobe/Mud
- has_superstructure_mud_mortar_stone (binary): Mud Mortar – Stone
- has_superstructure_stone_ﬂag (binary): Stone
- has_superstructure_cement_mortar_stone (binary): Cement Mortar – Stone
- has_superstructure_mud_mortar_brick (binary): Mud Mortar – Brick
- has_superstructure_cement_mortar_brick (binary): Cement Mortar – Brick
- has_superstructure_rc_non_engineered (binary): non-engineered reinforced concrete
- has_superstructure_rc_engineered (binary): engineered reinforced concrete.
This is all nothing, you can even write your own machine learning models and data science tasks here in the Notebooks. You can create experiments, automated workflows and you can also create an automated machine learning run.
For POC you have to provide results quickly, instead of building data wrangling actions, and predictive machine learning models from scratch, let me show you how the next tool in Azure Machine Learning Workspace can support your presales or POC work.
Designer: Data preparation, training, deployment
Do you also have the situation when the manager walks up to you and asks: “How long time do you need to build a machine learning model?” After some questions asked, you would receive data and understand the aim of the model. A first step from here could be to put together a POC which shows the analytical workflow and allows easier estimation of development time.
Data scientists can use a rich set of built-in components for data transformation and preparation, feature engineering, model training, scoring and evaluation. ML experts can visually craft their complex end-to-end ML training pipelines with their own code. ML engineers can construct the operations pipeline in the similar drag-n-drop approach. Azure Machine Learning Designer visualizes complex machine learning training pipelines and simplifies the process of building-, and testing models and operation tasks by bringing built in components, data visualization, model evaluation and MLOps (DevOps for Machine Learning) integration. It enables user to automatically generate scoring files, register models, and build images using Azure Kubernetes Service (AKS) for scale. The cloud-based asset also provides user with a set of built-in algorithms, feature engineering, and model evaluation to further simplify and dramatically accelerate the process of building machine learning solutions.
From the welcome screen of the workspace, start the Designer. Note that you can try out already generated sample pipelines to get started.
Create a new Easy-to-use prebuilt components pipeline. This environment is really similar to the old Studio, but numerous new features are added, like pretrained models for anomaly detection or computer vision and so on. You can drag and drop the components for you experiment and when you run this, you can review the results in the Jobs asset.
Let’s upload the dataset that we used in the previous section with the plus sign. This dataset is stored in a Storage Account, which was provisioned together with your workspace. Pull in the uploaded dataset to the authoring area, and then right click on the component to Preview data.
If you click on the Profile tab, we can see some visualization showing an analytical overview of our unbalanced dataset, additionally some information we learned in the Notebooks with the describe() function.
To exclude noisy values (such as non-numerical columns that were not shown in the describe function’s result), we can use the Select columns from dataset component. In the left panel choose the Components tab and search for the component. After you dragged and dropped the component to the authoring area, connect the dataset to the component. Click on the component twice to open the parameters window, and click Edit columns.
A new window opens, and put in the following list, and press Enter, then save.
Even though we know that we do not have empty fields, I would like to show another important component, the Clean missing data, which can exclude or transform all rows with missing values. Why do we need to choose first the relevant columns and then exclude null values instead of the other way around? Imagine that there are missing values in the columns which we would exclude anyway. If we first remove the entire row because of that missing value, we could exclude maybe useful features. So, therefore we first must include only the useful features, and then remove the possible null values. Instead of removing rows I will just choose to use a custom value and replace the empty values with 0 – this only works on numerical columns. On the left side, click Edit columns and choose Numeric Column types to operate on. In the Cleaning mode, choose Custom substitution value and as Replacement value write 0.
Another important step of data preparation is called Normalization, to exclude outlier values like we have seen for example at the age column. The goal of normalization also to change the values of numeric columns in the dataset to use a common scale, without distorting differences or losing information. This is useful since most of the columns have different metrics with different scale, now all the numerical columns will be on the same range of values.
The component we use is called Normalize Data, transformation method I chose ZScore, and Columns to transform are all numerical columns except the damage_grade. ZScore uses the mean and the standard deviation for calculating each values. It takes the value and decreases it with the mean of it, and then divides it with the standard deviation of it.
Let’s make our pipeline runnable! Click on Settings and Create Azure ML compute instance.
Give your machine a name and for this experiment you can use the default settings (CPU, Standard D4s, v3), then click Create.
When the compute is ready to use, on the authoring area, you can find a Submit button and create a new experiment. Specify the experiment’s name, how the running job’s name should be displayed and you can also provide a description. These are good to do, so later you will have some logs of your previous runs.
The job is now submitted, and you can review it by clicking on the Jobs in the left panel menu or next to the authoring area at the Submitted jobs tab.
The challenge of working with imbalanced datasets in most machine learning techniques is ignored, and in turn have a poor performance. Although if you think about it, typically the performance on the minority class is also very important. In our case the high risk of damage is a minority class for example. I’m using the SMOTE approach to solve this issue with oversampling and with the help of this technic I can provide the model close to equal number of samples for the labels.
Note, that there are a lot of features for the level 2, and a very low amount for the level 1 and 3 damage_grade. The component only works with two categories at once, but I have a great workaround for you.
First we are going to split the data twice with Relative expressions. Use Split Data components on both sides and choose Relative Expression as splitting mode. On the left we want only the level 1 and 2, on the right only level 2 and 3, because we are going to compare the level 1 and 3 features to the level 2.
Code for the left side: \”damage_grade” < 3
right side: \”damage_grade” > 1
Now let’s get the SMOTE components, and choose the damage_grade column to operate on, then set the percentage like on the picture below. The percentage specifies how much more features should be generated from a level, to align with the others.
Percentage on left side: 400
right side: 40
Remember, we have now two dataset, one of them includes damage_grade 1 and 2, the other includes 2 and 3, we have to put these together. For this we are going to use the Add Rows component, and from the right side we pull in the damage_grade 1 and 2, but from the other side we only need the 3, otherwise the labels would be biased again: 1, 2, 2, 3. So on the right side we also need to split the dataset again. So Split Data on the right with Relative Expression: \”damage_grade” > 2. The model now should look something like this:
Let’s submit this updated pipeline as a job, and review the results. On the job view, right click on the Add Rows component and choose to review the result dataset. Note that the damage_grade column is now holding a much more balanced data.
Now finally, with the help of the Split data component, we will prepare data for training and for validating the model. I set the fraction of splitting to 0.7, in which case 70% will be train data and 30% will be used to validate the model.
Now we are ready to train our model. For this we need to choose the best fitting algorithm.
There are several specific types of supervised learning that are represented within the Designer, for example: classification, regression, or anomaly detection. When you are not entirely sure which algorithm works better for your specific dataset, you can investigate that by pulling in two – or more – algorithms in the same time. I chose a Classification model which is used when a category needs to be defined – like in our case with the damage_grade. Since we have more than two categories, we need to find a best fitting Multiclass Classification algorithm. Find suggestions in the cheat sheet provided by Microsoft. After thorough investigation, in my case, the best fitting algorithm was the Multiclass Boosted Decision Tree. During training we can use the Tune Model Hyperparameters, so the best fitting parameters will be defined and used for the iteration, to reach better prediction results.
Scoring the model means, that it does the prediction. Use the Score model component for this, and connect the Trained best model output of the Tune Model Hyperparameters component and as Dataset, pass the second output of the Split Data component.
Submit the pipeline, and the result can be visualized. Right click on Score Model component, and choose to preview the Scored dataset. It shows the chosen damage_grade for a specific building, and the confidentiality of choosing the specific categories.
Evaluation is an essential step while building machine learning models, it tells us how well our model works. Use the Evaluate model component for this task.
- Accuracy refers to the average model-performance involves root mean square error (RMSE), which is the standard deviation of the errors in the prediction and mean absolute error, (MAE), the errors between paired observation calculations
- Precision is a measure of goodness that determines the proportion of label items from the available ones. In short precision is one of the most commonly used evaluation metrics show the percentage of accurate recommendations.
- Recall is a measure of completeness that gives the proportion of relevant results made out of all the relevant ones – meaning the results are correctly calculated for this percentage of the data.
Thanks to all these built-in components, you can quickly build an experiment, and find out by incremental trials, which setup works best for your scenario. When you are happy with the model, it can be deployed and used in production too. Deployment and usage of pipelines are discussed in another article. If you don’t want to spend your time on figuring out the best fitting algorithm for your scenario, maybe you want to look at the third element of the Azure ML Workspace.
Automated Machine Learning
If you are unsure which model fits best your dataset or solution, the no-code UI of Automated Machine Learning is the first you should try out. It allows you to easily create accurate models customized to your dataset and refined by different algorithms (deep learning for classification, time series forecasting, text analytics, image processing) and hyperparameters. You can increase productivity with easy data exploration and profiling with intelligent feature engineering. You can simply download the best model and improve it on your own PC too, and by pressing the Deploy button, your model is ready to be used from an API endpoint. And last but not least, you can build responsible AI solutions with model interpretability, and fine-tune your models to improve accuracy.
The Automated Machine Learning (AutoML) SDK allows you to run Deep learning solutions for Classification, Regression, Text Classification with BERT (on GPU) and Time series forecasting with ForecastTCN & HyperDrive.
As I mentioned before, the UI is quite understandable, we just go ahead and create a new run. Start the Automated ML from the welcome page, and click New Automated ML job. We provide the exact same dataset as we used in the previous two sections.
We can create a new experiment, we define a name for it, and say that the label – or the target column – is the damage_grade. We also provide a cluster where the experiment should run, click New, and for this project we can just leave every settings on default.
On the next window, specify a name for this compute and click Create. When the compute is done, choose it in the window we specified the label and other details, like on the image below.
Click Next and then choose classification. We can enable deep learning here, so we get better results. When clicking on Finish, the run starts up. After initializing the run, we can observe the models that have been tried on the Models tab. The one on the top has the best accuracy.
Click on the name of the algorithm and observe the top menu. We can download the code from here, and further improvements can be applied on it before deploying the model. You can easily deploy the chosen model as well by simply clicking on the Deploy button. If you want to learn more about how your data has been transformed, you can see that in the Data transformation tab.
If you want to learn more about your model, you could take a look at the metrics as well, where you can visualize all kind of details. For example, my favorite is the confusion matrix, which tells us how well the model was able to define the specific damage_grade, or how confused is the model.
For example, the dark blue box shows 12622. This means that in 12622 cases, the model correctly predicted the label “2” (medium risk of damage) for buildings. The lightest box with 42 in it shows that it predicted label “1” (low risk of damage) 42 times for buildings when they actually have high risk of damage, label “3”.
Azure Machine Learning Workspace can be used for simple and complex problems as well, for code-first and no-code scenarios. I think it is a great place to get started with understanding machine learning, learning about the algorithms and the flow of training.
The best choice of algorithms and data features are highly dependent on what problem you try to solve, and what kind of dataset you have.
And remember, spend as much time as possible with feature engineering, because that has the biggest impact on the accuracy of the model. Training and testing the model helps you to see where the model needs to be improved to get better accuracy of prediction. Iterative improvements are key to machine learning modeling and the best result is the aim – this is the reason, I think, why Artificial Intelligence is an always improving field.