The theater model as software architecture
zondag 25 februari 2007 10:36
Bernard Baars' Theater model of the human mind lends itself well as a software architecture for a human-like mind. It is distinct from any of the software architectures that I discerned before. It's main components are:
Contexts do the actual work of the architecture. The solve problems, plan actions, interpret input, etc. Any context can be a complete application in itself. Contexts are not static. They can be created and be destroyed. Contexts receive their input from outside (perceptual contexts) or from WM. Contexts are connected to WM in an active way. They constantly monitor the contents of WM, to see if it contains parcels that may serve as input to their process. If so, they send a request to the Action Scheduler to get access to the WM. If this is granted, the context can act upon the WM parcel or parcels.
The Input Scheduler receives requests from all contexts to place their parcels onto the WM workbench. Based on some criteria of importance it decides which parcel (parcels?) to place there.
The Action Scheduler does the same. Only the requests are actions, not parcels.
The architecture is interesting in areas where:
- Working Memory
- Contexts
- Input scheduler
- Action scheduler
Contexts do the actual work of the architecture. The solve problems, plan actions, interpret input, etc. Any context can be a complete application in itself. Contexts are not static. They can be created and be destroyed. Contexts receive their input from outside (perceptual contexts) or from WM. Contexts are connected to WM in an active way. They constantly monitor the contents of WM, to see if it contains parcels that may serve as input to their process. If so, they send a request to the Action Scheduler to get access to the WM. If this is granted, the context can act upon the WM parcel or parcels.
The Input Scheduler receives requests from all contexts to place their parcels onto the WM workbench. Based on some criteria of importance it decides which parcel (parcels?) to place there.
The Action Scheduler does the same. Only the requests are actions, not parcels.
The architecture is interesting in areas where:
- Many diverse problems are solved simultaneously
- The agent needs to be flexible and respond to interrupting threats/requests immediately
- Input is highly ambiguous and can be interpreted in many ways (the active contexts); interpretation requires a large top-down component, and this component may change all the time
- Many processes are active at the same time, not necessarily solving problems, but also just performing complex tasks; these tasks should be performed in parallel as well
- Labels
- cognitive architecture
Archief > 2007
december
september
- 22-09-07 12:46 - Implementation of the parser
- 18-09-07 16:47 - Saga - Duitse rock uit de jaren 80
- 04-09-07 21:18 - Rah band - Clouds across the moon - YouTube
augustus
juli
juni
mei
februari
- 25-02-07 10:36 - The theater model as software architecture
- 20-02-07 21:39 - A Semantic Web Primer
- 07-02-07 22:13 - My position on consciousness
- 05-02-07 21:31 - In the theater of consciousness
Reacties op 'The theater model as software architecture'
Geen berichten gevonden
Log in om te kunnen reageren op nieuwsberichten.