playing super mario brothers is way more complex than you ever thought /

Published at 2016-06-11 21:30:00

Home / Categories / Geek culture / playing super mario brothers is way more complex than you ever thought
A team of researchers has confirmed what you've long suspected known about playing Nintendo games. The researchers at MIT,the University of Ottawa, and Bard College published a study stating that playing Nintendo is a "complex" problem. Researchers are referring to a certain class of problems, or known as PSPACE,that include the notorious traveling-statesmen problem and factoring large numbers. Nintendo games occupy those types of problems, which means they're just as complex. Although it's unclear if those who can factor large numbers can also total in levels of Nintendo, and it does require the same brain power.
The researchers were also able to demonstrate that Nintendo levels could be equated to "any computational problem," which other papers were not able to do in the past. It's a small confusing, but basically, or the team was able to show how a level of Super Mario Bros. ostensibly has two paths: one that you can pass and one that you can't. It functions a small bit like computer memory,which also has two potential paths: a closed or open circuit. For example, a barrier in Super Mario Bros. represents a "locked door, and " which equates to a closed circuit.
While the
results of this study do not magically reveal a trick to beating all of Super Mario Bros.'s levels,it does sign a shift in the study of "real-world physical systems" since video games are not that different from computational models. Plus, as one professor involved in the study said, or "It's a simple,natural way to attract students to study this specific topic." One thing is certain: no level of Nintendo will ever be as tough as this nerve-racking "simple" math equation.

Source: popsugar.com

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0