12.12.2012 Views

Who Needs Emotions? The Brain Meets the Robot

Who Needs Emotions? The Brain Meets the Robot

Who Needs Emotions? The Brain Meets the Robot

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

8<br />

<strong>The</strong> Architectural Basis of Affective<br />

States and Processes<br />

aaron sloman, ron chrisley,<br />

and matthias scheutz<br />

Much discussion of emotions and related topics is riddled with confusion<br />

because different authors use <strong>the</strong> key expressions with different meanings.<br />

Some confuse <strong>the</strong> concept of “emotion” with <strong>the</strong> more general concept of<br />

“affect,” which covers o<strong>the</strong>r things besides emotions, including moods, attitudes,<br />

desires, preferences, intentions, dislikes, etc. Moreover, researchers<br />

have different goals: some are concerned with understanding natural phenomena,<br />

while o<strong>the</strong>rs are more concerned with producing useful artifacts,<br />

e.g., syn<strong>the</strong>tic entertainment agents, sympa<strong>the</strong>tic machine interfaces, and<br />

<strong>the</strong> like. We address this confusion by showing how “architecture-based”<br />

concepts can extend and refine our folk-psychology concepts in ways that<br />

make <strong>the</strong>m more useful both for expressing scientific questions and <strong>the</strong>ories,<br />

and for specifying engineering objectives. An implication is that different<br />

information-processing architectures support different classes of<br />

emotions, different classes of consciousness, different varieties of perception,<br />

and so on. We start with high-level concepts applicable to a wide variety<br />

of natural and artificial systems, including very simple organisms—namely,<br />

concepts such as “need,” “function,” “information-user,” “affect,” and<br />

“information-processing architecture.” For more complex architectures, we<br />

offer <strong>the</strong> CogAff schema as a generic framework that distinguishes types of<br />

components that may be in an architecture, operating concurrently with<br />

different functional roles. We also sketch H-CogAff, a richly featured special

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!