modeling cognitive dissonance in neural networks progress report

MODELING COGNITIVE DISSONANCE IN NEURAL NETWORKS

Progress Report

Introduction

The Client: Dr. WatsonThe Problem: Dr. Watson needs software to

accurately model cognitive dissonance.

2

Dissonance occurs when two ideas stem from an act and contradict each other.

The ideas in question are Cognitions.

Cognitive Dissonance

3

Responsibility

Belief

Cognition 1

Cognition 2

Dissonance decreases by removing (or attempting to remove) the conflict between cognitions.

Neural Network

Simulates biological neuron interactions.Cognitions will be comprised of two neural

network nodes.Cognitions can be connected between one

another by positive or negative relations.

4

Belief

Cognition

Node 1

Node 2

Neural Network

5

Algorithms for modeling the cognitive dissonance reduction are provided..

..but must be mapped into the software.

Previously Used Software

Very Complicated User InterfaceIs not that useful for modeling cognitive

dissonance

6

Development Environment

Operating System: WindowsHardware: Standard PCProgramming Language: C++Libraries: OpenGL, LibUFO

Graphical and easy to use interface that hides the complicated algorithms underneath.

7

Requested Features

Algorithm to simulate biological neuronsReplication of consonance and dissonance

models Simulate a dissonant event Follow the reduction of dissonance

User adjustable weights on cognitions and resistances

Template for value input – i.e. matrix

8

Interface Mockup

Whiteboard used to place ideas based off of meetings with Dr. Watson.

9

Interface Mockup

10

Whiteboard images scanned to paper and gone over with the client.

Interface Mockup

11

Inspect graph at a particular point.

Edit specific nodes during a run.

Monitor individual nodes.

Use Cases

Use Cases presented to Dr. Watson.

12

What’s Next..

13

Documenting the Requirements Analysis.Work on generating the Contract document.

You are here.

Credits

Team leader - Cory Lehan- Led…

Process - Tim Meyer- Still getting requirements

Plan - Jarrod Capps- Mapped out rough future plan with

FujinokiDesign - Jon Bridges

- Basic plan of the software designInterface - Cory Lehan

- Made mock-up interface14

Credits

Implementation - Jarrod Capps- Not yet required

Tester - Tim Meyer- Not yet required

Quality - Jon Bridges- Made Use Cases- Critiqued interface

Support - Cory Lehan- Found graphics libraries

Questions?

Team NeuroticCory LehanTim MeyerJarrod CappsJonathan Bridges

16