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
Last revisionBoth sides next revision
lirec:m14 [2009-01-28 16:55] – davegriffithslirec:m14 [2009-01-29 13:30] – davegriffiths
Line 3: Line 3:
 **D9.2. First skeleton companions M14 Result of completion of T9.1.2 Report, live experiment** **D9.2. First skeleton companions M14 Result of completion of T9.1.2 Report, live experiment**
  
-Very sketchy ideas at this point, pending more information and getting hands dirty with ION. Will be chopped and solidified as more information is acquired.+=====Questions===== 
 + 
 +Trying to understand the role of foam in lirec, in order to start working on what deliverables can be for this milestone. 
 + 
 +Dissemination: 
 +  * Do we need to start thinking about Lirec in art galleries, art installations - for wider dissemination to the public? 
 +  * How to convey long term companionship in such a format? 
 +  * What about downloadable companions/games for the masses? 
 +  * Downloadable iphone/android/equiv apps? 
 +  * Get these available early - and with source - to start collecting a momentum of interest 
 +    
 +Pleo and existing communities of robot hackers: 
 +  * Can we use the pleo as a tool for dissemination to a community with an existing robot framework? 
 +  * Are there any other similar communities? (Lego Mindstorms?) 
 +  * Is the pleo being used in any of the scenarios? 
 +  * Can we get/do we need an PDK for any of this to work? 
 + 
 +ION 
 +  * What nature is the development of companions using ION?  
 +    * Java/other code? 
 +    * XML descriptions of personalities etc? 
 +    * Where will this development material live?  
 +    * Will it be shared between partners? 
 +  * Can we use the Pleo with ION?
  
 ======Some Directions====== ======Some Directions======
  
-These are some vague ideas and directions to head in. I'm not sure whether foam's work is best done as theming and adapting the existing lirec scenarios, or how much we need to/can head in our own direction. I guess the nature of this will become clearer after forthcoming meetings.+These are some vague ideas and directions we could head in. I'm not sure whether foam's work is best done as theming and adapting the existing lirec scenarios, or how much we need to/can head in our own direction. I guess the nature of this will become clearer after forthcoming meetings. 
 + 
 +I'm assuming foam needs to look at widening the interest of the work done to as big an audience as possible. This means the other research partners can concentrate on the scientific nature of the scenarios/experiments. 
  
 We need to consider what access to hardware we will have in the short term, and how far we could get with development for this deliverable. It would be good to have some foam specific goals which can give direction to the development... so with that in mind: We need to consider what access to hardware we will have in the short term, and how far we could get with development for this deliverable. It would be good to have some foam specific goals which can give direction to the development... so with that in mind:
Line 77: Line 102:
     * Anger - needs calming, physical contact     * Anger - needs calming, physical contact
     * Sadness - needs singing to     * Sadness - needs singing to
 +    * Gets over excited - needs calming down
   * All of the above?!   * All of the above?!
   * It may be important that they are entirely unnecessary needs    * It may be important that they are entirely unnecessary needs 
Line 92: Line 118:
 ======Scenarios====== ======Scenarios======
  
-How can some of this relate to the existing scenarios?+How can some of this relate to the existing scenarios? [TODO]
  
-^ Scenario ^ Froth ^ +^ Scenario ^ Hardware ^ Target audience ^ Notes ^ 
-|**HW Team buddy**| | +|**HW Team buddy**| Mobile Robot | Students | Collective memory for a small group of workers, knows who is present, and where people are who are not. Knows about collective events, deadlines and such. Learns personalisation for each team member. Remembers bits of personal information volunteered by group members. | 
-|**HW Personal guide**| | +|**HW Personal guide**| PDA | Students | Portable companion which knows it's location and can act as a guide, and tell anecdotes and stories about places. Includes route planning, knowledge of weather conditions. | 
-|**HW In the wild**| Artificial Dependency | +|**HW In the wild**| Graphical display | Students | A gossip robot, converses with individuals and remembers who they are. Uses a text based chat interface, also simple games included. One of the main motivations is to deal with deliberate rudeness gracefully. | 
-|**INESC-ID Game companion**|  | +|**INESC-ID Game companion**| Static robot or graphical agent | Children and teenagers | A companion for playing games which will learn the individuals it interacts with, and their histories of playing together | 
-|**INESC-ID Personal trainer**| | +|**INESC-ID Personal trainer**| PDA/graphical display | Not specified | A companion which will create and update a fitness program for the user, migrating to different embodiments as required | 
-|**INESC-ID Welcome to the jungle**| Automatic Theatres |+|**INESC-ID Welcome to the jungle**| Mobile robot/graphical display | Not specified | A robot augments a game world which it can migrate into when required, communicating with the user at all times |
 |**UH Fetch and carry**| | |**UH Fetch and carry**| |
 |**UH Cognitive prosthetic**| | |**UH Cognitive prosthetic**| |
Line 106: Line 132:
 |**UH Teaching proxemic preferences**| | |**UH Teaching proxemic preferences**| |
 |**UH Travelling companion**| Artificial Dependency | |**UH Travelling companion**| Artificial Dependency |
 +
 +
  
  • lirec/m14.txt
  • Last modified: 2009-01-29 14:41
  • by davegriffiths