A Bit of Theory: Consciousness as Integrated Information

It's essential that we determine to what extent different neural architectures can generate integrated information

5 min read

If the level of consciousness has to do with how much integrated information a conscious entity generates, it is essential that we determine to what extent different neural architectures can generate integrated information. The integrated-information theory of consciousness, or IIT, is an attempt to do so, and to approach consciousness from first principles.

IIT introduces a measure of integrated information, represented by the symbol ο and given in bits, that quantifies the reduction of uncertainty (that is, the information generated when a system enters a particular state through causal interactions among its parts) This measure is above and beyond the information generated independently within the parts themselves. The parts should be chosen in such a way that they can account for as much nonintegrated (independent) information as possible.

Keep Reading ↓Show less

This article is for IEEE members only. Join IEEE to access our full archive.

Join the world’s largest professional organization devoted to engineering and applied sciences and get access to all of Spectrum’s articles, podcasts, and special reports. Learn more →

If you're already an IEEE member, please sign in to continue reading.

Membership includes:

  • Get unlimited access to IEEE Spectrum content
  • Follow your favorite topics to create a personalized feed of IEEE Spectrum content
  • Save Spectrum articles to read later
  • Network with other technology professionals
  • Establish a professional profile
  • Create a group to share and collaborate on projects
  • Discover IEEE events and activities
  • Join and participate in discussions

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"]}