Skip to Content

Changes for page Humanoid Robot

Last modified by Pierre Bongrand on 2022/04/05 20:48
From version Icon 20.3 Icon
edited by Pierre Bongrand
on 2022/04/01 04:23
Change comment: There is no comment for this version
To version Icon 21.1 Icon
edited by Pierre Bongrand
on 2022/04/01 04:38
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Content
... ... @@ -16,16 +16,30 @@
16 16  [[image:Pepper-robot-sensors-18.jpg]]
17 17  
18 18  = Pepper usage =
19 -Moreover, using [[Choregraphe>>http://doc.aldebaran.com/2-4/software/choregraphe/choregraphe_overview.html]], Pepper is highly parameterizable, it is relatively easy to expand the functionalities by programming new blocks, and prototypes can also be done quickly. This is very valuable as we expanded every week our prototype to include new features based on the content from the lecture.
19 +We tried to make full use of the sensors provided within Pepper. As we had limited amount of time we mainly focused on working with: the microphones, the speakers, the display and the arms movement of Pepper.
20 20  
21 -We tried to make full use of the sensors provided within Pepper. As we had limited amount of time we mainly focused on working with: the microphones, the speakers, the display and the
21 +The actions we implemented for our prototype include:
22 +* Playing music
23 +* Listening and understanding the PwD
24 +* Speaking to the PwD
25 +* Displaying information on the tablet
26 +* Moving arms to convey message
22 22  
28 +For the actual implemented version, we have enabled Pepper to show images about the current activity when interacting with the PwDs, which can not only improve the efficiency of communication between them, but also makes PwDs feel more cared.
23 23  
24 -In assumption, we planned to make it possible for the HCP to modify the calendar/reminder
25 - features with touching the tablet. Besides, to enable Pepper moving around to take care of the PwDs with the help of sensors. Also, it's better to let Pepper communicate with the PwDs both by dictating and showing images, for the decline of recognition ability of PwDs.
30 += Iterative Process =
31 +-> Describe a bit a philosophy from slides: SCE framework & PACT analysis.
26 26  
27 -For the actual implemented version, we have enabled Pepper to show images about the current activity when interacting with the PwDs, which can not only
28 -improve the efficiency of communication between them, but also makes PwDs feel more cared.
33 +based on:
29 29  
35 +[1]: Neerincx, Mark & van Vught, Willeke & Blanson Henkemans, Olivier & Oleari, Elettra & Broekens, Joost & Peters, Rifca & Kaptein, Frank & Demiris, Yiannis & Kiefer, Bernd & Fumagalli, Diego & Bierman, Bert. (2019). Socio-Cognitive Engineering of a Robotic Partner for Child's Diabetes Self-Management. Frontiers in Robotics and AI. 6. 118.
36 +
37 +[2]: Benyon, David (2019). Designing User Experience: A Guide to HCI, UX and Interaction Design. Pearson UK.
38 +
39 +
40 +Moreover, using [[Choregraphe>>http://doc.aldebaran.com/2-4/software/choregraphe/choregraphe_overview.html]], Pepper is highly parameterizable, it is relatively easy to expand the functionalities by programming new blocks, and prototypes can also be done quickly. This is very valuable as we expanded every week our prototype to include new features based on the content from the lecture.
41 +
42 +
30 30  For more information on our use of Pepper to help people with dementia, please check the [[Robotic Partner >>https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/view/Foundation/Human%20Factors/Robotic%20Partner/]] section.
31 31  
45 +