Real-Time Crowd Simulator Could Help Prevent Deadly Stampedes

System collects real-time crowd data to help authorities predict and head off tragic stampedes that have left hundreds dead

2 min read
A new crowd-density simulator is designed to help authorities predict when a crush of people could turn deadly.
Photo: iStockphoto

As fatal crowd accidents in places like Shanghai and Mecca have shown, improved means of controlling crowd behavior and predicting dangerous congestion spots would be a boon to authorities such as police forces that are tasked with managing major public events. To this end, Mitsubishi Electric and the University of Tokyo’s Research Center for Advanced Science and Technology (RCAST) have jointly developed what they claim is the world’s first real-time crowd-congestion estimation system.

According to Mitsubishi, conventional systems rely on previously collected data concerning crowd conditions for a given location or event. The data is retrieved from a database and fed to a crowd-movement simulator, which then produces a crowd density map.

Rather than relying on historical data, the Mitsubishi system employs surveillance cameras positioned at strategic locations to capture the flow rate of crowds along major pathways in real time. To simulate pedestrian dynamics, the RCAST researchers used a mathematical tool known as a “floor field cellular automaton model,” which together with the flow-rate data can produce a crowd-movement simulation in real time.

The combined results are converted into a color-coded map showing areas where crowd density could be a concern [see figure below].

imgImage: Mitsubishi Electric

Mitsubishi says that whereas a conventional system bases its calculations on all the people estimated to be in a given location, the new system uses the real-time flow rate data to do a more accurate calculation, taking into account a more select group of people [figure, below].

imgImage: Mitsubishi Electric

Mitsubishi claims that this optimized way of modeling pedestrian dynamics reduces computational complexity and raises the accuracy of calculated crowd-density maps to 80 percent, compared with the roughly 50 percent accuracy yielded by conventional systems.

Mitsubishi claims that its system can increase the accuracy of crowd-density maps to 80 percent, compared with the roughly 50 percent accuracy yielded by conventional crowd simulators.

Given these improvements, Shunichi Sekiguchi, general manager of Mitsubishi’s surveillance system technology division, believes the new system could help prevent the kinds of crowd tragedies that happened in Shanghai and Mecca.

“Thanks to these more accurate predictions and visualizations made in real time, it makes early regulation of crowd traffic possible,” he says. “This would help authorities and security companies take preventive countermeasures when necessary.”

Mitsubishi tested the system at a popular firework festival held on the Tamagawa River in Tokyo last week. The company worked with local Setagaya Ward authorities and used eight cameras to measure crowd flow.

“We are currently reviewing the results from the field demonstration,” says Sekiguchi. “But what I can say is that it rained sometimes during the evening, and so we were able to verify the precision of the people count and congestion predictions in bad weather conditions.”

No word yet when the system will be ready for commercialization, though Sekiguchi said they are “speeding up research and development for early practical application.”

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less
{"imageShortcodeIds":["31996907"]}