Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
lirec_notes [2009-01-06 15:17] davegriffithslirec_notes [2009-01-06 15:28] davegriffiths
Line 2: Line 2:
  
 LIREC aims to establish a multi-faceted theory of artificial long-term companions (including memory, emotions, cognition, communication, learning, etc.), embody this theory in robust and innovative technology and experimentally verify both the theory and technology in real social environments. Whether as robots, social toys or graphical and mobile synthetic characters, interactive and sociable technology is advancing rapidly. However, the social, psychological and cognitive foundations and consequences of such technological artefacts entering our daily lives - at work, or in the home - are less well understood. LIREC aims to establish a multi-faceted theory of artificial long-term companions (including memory, emotions, cognition, communication, learning, etc.), embody this theory in robust and innovative technology and experimentally verify both the theory and technology in real social environments. Whether as robots, social toys or graphical and mobile synthetic characters, interactive and sociable technology is advancing rapidly. However, the social, psychological and cognitive foundations and consequences of such technological artefacts entering our daily lives - at work, or in the home - are less well understood.
 +
 +==Links==
 +
 +http://www.lirec.org
  
 ==Agent platforms== ==Agent platforms==
Line 48: Line 52:
   - Reuse code across these platforms   - Reuse code across these platforms
   - Support migration at runtime between platforms   - Support migration at runtime between platforms
- 
-Platforms can consist of 4 main types, mobile robot, fixed robot, handheld device or fixed graphical system. Each has it's inherent restrictions.  
  
 ==Existing robot architectures== ==Existing robot architectures==
-In the whole, there is a lack of sharing of this kind of technology. This is partly because generalising is hard in this field, considering all types of robots possible. However, Lirec has to generalise as it's using a wide variety of architectures.+In the whole, there has historically been a lack of sharing of this kind of technology. This is partly because generalising is hard, considering all types of robots possible. However, Lirec has to generalise as it's using a wide variety of architectures and needs to share as much as possible.
  
-NASREM/NIST RCS NASA + ESA use generic system with their subcontractors.+While some existing architectures are available, none of them address the needs of lirec, given the focus: 
 +  Long term companionship rather than purely technical problem 
 +  - Working across different platforms
  
 ==Methodology== ==Methodology==
Line 62: Line 66:
 This can be summed up as predictive vs reactive. This can be summed up as predictive vs reactive.
  
-The plan is to use a hybrid approach, example BIRON. Where the predictive constrains the reactive to combine local decisions with a world model.+The plan is to use a hybrid approach, example [[http://www.techfak.net/ags/ai/projects/BIRON/welcome.html|BIRON]]. Where the predictive constrains the reactive to combine local decisions with a world model.
  
 The architecture will consist of 3 layers of abstraction: The architecture will consist of 3 layers of abstraction:
Line 77: Line 81:
   * Obstacle avoidance   * Obstacle avoidance
  
-YARP+[[http://eris.liralab.it/yarp/|YARP]] is a good example of sharing code in this way on a Linux platform. 
  • lirec_notes.txt
  • Last modified: 2020-06-05 22:30
  • by nik