Is Machine Learning Getting Us Closer to Predicting Eruptions?
The 2019 tragedy at New Zealand White Island might have been prevented if there was more warning. Could machine learning allow for better, true prediction of volcanic eruptions?
When Whakaari (White Island) in New Zealand unexpectedly erupted in December 2019, more than 40 tourists found themselves trapped on a small island that was exploding. The hot gases and water, flying rocks and ash killed 21 people during that eruption. This tragedy was a wake-up call for tour operators who would regularly bring people to this restless volcano in the Bay of Plenty. It is a volcano that produces steam-driven explosions that come with little warning, and it is these types of blasts that have killed dozens of people on volcanoes around the world over the past decade.
Part of the problem is how we think about volcanic danger. What people want is a prediction — when exactly will the volcano erupt? The volcanological community isn’t in the game of prediction because we just don’t know enough about what exactly triggers an eruption to be that precise.
Instead, volcano monitoring relies on forecasts that capture a probability of eruption. Seeing many earthquakes and increasing gas emissions from a volcano? We can say that the likelihood of an eruption has increased. Maybe we can even say it could happen in the next month. However, it is not going to be “tomorrow at noon,” just like a weather forecast.
These forecasts and probability models lead to volcanic alert levels. The scientists monitoring volcanoes and emergency managers need to communicate the risk, so most countries use some volcanic alert system to show how potentially dangerous a volcano is at a given moment. Alert Level 1? The chances of an eruption are low. Alert Level 3? The chances are very high for an eruption.
Both forecasts and alert levels are defined by people looking at all the data coming in from a volcano — earthquakes, gas emissions, deformation, thermal and more — and interpreting what all the signs might mean. Usually, a probability tree (or decision tree) is used. These branching flow charts allow for taking the signs at the volcano and its past activity to produce a probability for specific events.
Unrest at a volcano? Based on its past activity and the type of unrest, it might be 85 percent chance that nothing happens, 15 percent chance of an eruption. In that 15 percent chance, it might be 95 percent chance of a small eruption and 5 percent chance of something larger.
With people involved, these decisions of alert level can take time. A new study in Nature Communications by Dempsey and others has developed a machine learning approach to forecasting volcanic eruptions and setting alert levels at volcanoes. They examined nine years’ worth of data from Whakaari to train a computer to look for the precursory signs of volcanic blasts — especially the steam-driven eruptions whose precursors can be subtle — and then developed criteria for the computer to decide if an alert is needed.
Dempsey and his colleagues set limits on when the computer would call for an increased alert. If 80 out of 100 outcomes in the probability tree led to an eruption, then an alert was needed. With that threshold, almost all the eruptions over the past nine years were caught. The December 2019 eruption produced an alert four hours before the blast, which could have been enough time to get tourists away from danger. Only a purely hydrothermal eruption in 2016 was missed and this might have been because it was unlike other blasts at Whakaari (more on this in a bit).
Using this method, alert status can be changed faster as signs change. The data can be reinterpreted on a minute-by-minute scale. As the authors point out, this also takes out the potential bias caused by personal, political or economic influences on setting alerts.
Yet, there are problems. The missed eruption in 2013 is an example of how the computer can’t identify potential eruptions if the precursors have not been seen before — remember, it “learns” based on the data it is fed. Dempsey and colleagues point out that it still needs a review by people to watch for such unique events.
The biggest question, though, ends up outside the computations. Who has access to this information? When do emergency managers or scientists publicize the changes? Without clear guides to how the computer forecasts can be integrated with effective management plans, the value is diminished.
However, this is all a big step forward. With these unexpected blasts like what happened at Whakaari in 2019 or Ontake in 2014, warning even a few hours beforehand could save many lives. We aren’t yet “predicting” an eruption, but we are getting more refined in interpreting the signs of impending explosions.
This article originally appeared on discovermagazine.com To read the full article and see the images, click here.
Nastel Technologies uses machine learning to detect anomalies, behavior and sentiment, accelerate decisions, satisfy customers, innovate continuously. To answer business-centric questions and provide actionable guidance for decision-makers, Nastel’s AutoPilot® for Analytics fuses:
- zAdvanced predictive anomaly detection, Bayesian Classification and other machine learning algorithms
- Raw information handling and analytics speed
- End-to-end business transaction tracking that spans technologies, tiers, and organizations
- Intuitive, easy-to-use data visualizations and dashboards
Nastel Technologies is the global leader in Integration Infrastructure Management (i2M). It helps companies achieve flawless delivery of digital services powered by integration infrastructure by delivering Middleware Management, Monitoring, Tracking, and Analytics to detect anomalies, accelerate decisions, and enable customers to constantly innovate, to answer business-centric questions, and provide actionable guidance for decision-makers. It is particularly focused on IBM MQ, Apache Kafka, Solace, TIBCO EMS, ACE/IIB and also supports RabbitMQ, ActiveMQ, Blockchain, IOT, DataPower, MFT and many more.
The Nastel i2M Platform provides:
- Secure self-service configuration management with auditing for governance & compliance
- Message management for Application Development, Test, & Support
- Real-time performance monitoring, alerting, and remediation
- Business transaction tracking and IT message tracing
- AIOps and APM
- Automation for CI/CD DevOps
- Analytics for root cause analysis & Management Information (MI)
- Integration with ITSM/SIEM solutions including ServiceNow, Splunk, & AppDynamics