Skip to Content

Changes for page Humanoid Robot

Last modified by Pierre Bongrand on 2022/04/05 20:48
From version Icon 31.1 Icon
edited by Mathieu Jung-Muller
on 2022/04/03 14:49
Change comment: There is no comment for this version
To version Icon 29.1 Icon
edited by Sneha Lodha
on 2022/04/03 13:12
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Mathieu
1 +XWiki.snehalodha
Content
... ... @@ -1,12 +1,9 @@
1 1  = Robot Choice =
2 -
3 3  We were offered to work with three robots: [[Pepper>>https://www.softbankrobotics.com/emea/en/pepper]], [[Nao>>https://www.softbankrobotics.com/emea/en/nao]] and [[Miro>>https://www.miro-e.com]].
4 4  As our main goal is to improve the quality of life of the patient with dementia by providing some some social support. We believe that the human size semi-humanoid form of Pepper and its capacity to communicate easily with humans are great comparative advantages to choose it.
5 5  
6 6  = Pepper Description =
7 -
8 8  Pepper is a robot that allows easy communication robot/user, thanks to its ability kit that includes:
9 -
10 10  * Speech recognition
11 11  * Voice
12 12  * Tablet
... ... @@ -17,11 +17,9 @@
17 17  Figure 1: All sensors and actuators provided by Pepper
18 18  
19 19  = Pepper usage =
20 -
21 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 arms movement of Pepper.
22 22  
23 23  The actions we implemented for our prototype include:
24 -
25 25  * Playing music
26 26  * Listening and understanding the PwD
27 27  * Speaking to the PwD
... ... @@ -31,10 +31,8 @@
31 31  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.
32 32  
33 33  = Iterative Process =
34 -
35 35  Through the course of the development of Pepper, we followed an iterative process of design where we programmed and re-programmed certain aspects to accommodate weekly feedback. This approach aided us in ameliorating existing functionality, while adding new features. The following is brief indication of how this iterative process looked for our development pipeline:
36 -
37 -1. Research overview of how Pepper works, and look into the Interactive Robotics platform and Choregraphe
30 +1. Research overview of how Pepper works, and look into the interactive robotics platform and Choregraphe
38 38  2. Use the virtual version of Pepper on Choregraphe to make some initial behaviors (based off usecases)
39 39  3. Review implemented behaviors using physical version of Pepper
40 40  4. Make some adjustments and debug according to observed behaviors of previous iteration
... ... @@ -41,9 +41,7 @@
41 41  5. Add new behaviors and test once again with physical version of Pepper
42 42  6. Test and improve the final behaviors!
43 43  
44 -== PACT analysis ==
45 -
46 -
37 +== PACT analysis ==
47 47  ->need to add a bit of text
48 48  **People** perform **activities** in specific **contexts** with **technologies**, which affect the situated activities, which set new user requirements.
49 49