Difference between revisions of "The CINDY Cognitive Architecture"
| Line 1: | Line 1: | ||
| − | + | == Long-term Goal == | |
| − | + | CINDY stands for '''Ci'''rcular '''N'''etwork '''Dy'''namics. As a project in developing a cognitive system, it is just beginning. It is based on several other cognitive architectures, especially the iCub cognitive architecture which was never fully realized. | |
| − | + | CINDY is a very early work-in-progress but the long-term goal is to design and implement of an emergent artificial cognitive system that builds on the principles of growth and development through circular causality, sharing many of the principles of the field of Systems Dynamics and Dynamical Systems Theory (e.g. positive feedback, circular causality, non-linearity, far-from equilibrium stability, endogenous change, structurally-determined dynamic patterns). | |
In the long-term, CINDY will feature: | In the long-term, CINDY will feature: | ||
| Line 11: | Line 11: | ||
* value-system driven development | * value-system driven development | ||
* action selection based on internal simulation | * action selection based on internal simulation | ||
| + | |||
| + | == Short-term Relevance == | ||
| + | |||
| + | Right now, though, apart from some utility functions, it comprises just two prototype components that serve simply as examples of how a typical component in the architecture should be implemented. Over the coming months, additional components will be added, some based on the original iCub cognitive architecture and some completely new. These will provide to the functionality expected in a cognitive architecture. | ||
| + | |||
| + | '''These prototype components can also be used as the basis for developing applications using the component-port-connector model of component-based software engineering. One of the prototypes features a graphic user interface (GUI) implemented using FLTK, while the other does not.''' | ||
| + | |||
| + | == What to Do Next == | ||
The following sections will help you install the current implementation and run some test applications. It also provides a comprehensive overview of how to develop a new component for the architecture. | The following sections will help you install the current implementation and run some test applications. It also provides a comprehensive overview of how to develop a new component for the architecture. | ||
Revision as of 14:21, 15 February 2015
Contents
Long-term Goal
CINDY stands for Circular Network Dynamics. As a project in developing a cognitive system, it is just beginning. It is based on several other cognitive architectures, especially the iCub cognitive architecture which was never fully realized.
CINDY is a very early work-in-progress but the long-term goal is to design and implement of an emergent artificial cognitive system that builds on the principles of growth and development through circular causality, sharing many of the principles of the field of Systems Dynamics and Dynamical Systems Theory (e.g. positive feedback, circular causality, non-linearity, far-from equilibrium stability, endogenous change, structurally-determined dynamic patterns).
In the long-term, CINDY will feature:
- exogenous and endogenous attention (both overt and covert)
- joint perceptuo-motor representations (e.g. joint episodic-procedural memory)
- value-system driven development
- action selection based on internal simulation
Short-term Relevance
Right now, though, apart from some utility functions, it comprises just two prototype components that serve simply as examples of how a typical component in the architecture should be implemented. Over the coming months, additional components will be added, some based on the original iCub cognitive architecture and some completely new. These will provide to the functionality expected in a cognitive architecture.
These prototype components can also be used as the basis for developing applications using the component-port-connector model of component-based software engineering. One of the prototypes features a graphic user interface (GUI) implemented using FLTK, while the other does not.
What to Do Next
The following sections will help you install the current implementation and run some test applications. It also provides a comprehensive overview of how to develop a new component for the architecture.
There are also a set of software engineering standards which have been adopted to make sure the software can be maintained in the long term. Please respect these standards if you are developing code that you intend to be integrated into the architecture.
Developer Guides
- Software Installation Guide
- Software Users Guide
- Software Development Guide
- Software Integration Guide
- System Architecture Guide
- Component Reference Manual
