Wiki source code of Humanoid Robot

Last modified by Pierre Bongrand on 2022/04/05 20:48

version	line-number	content
20.3	1	= Robot Choice =
31.1	2
25.2	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]].
34.1	4	As our main goal is to improve the quality of life of the patient with dementia by providing 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.
2.1	5
20.3	6	= Pepper Description =
31.1	7
16.1	8	Pepper is a robot that allows easy communication robot/user, thanks to its ability kit that includes:
31.1	9
20.2	10	* Speech recognition
16.1	11	* Voice
	12	* Tablet
20.2	13	* Cameras
16.1	14	* Humanoid form
2.1	15
38.1	16	[[image:Pepper-robot-sensors-18.jpg]]
28.1	17	Figure 1: All sensors and actuators provided by Pepper
3.1	18
20.3	19	= Pepper usage =
31.1	20
34.1	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 tablet display and the arms movement of Pepper.
14.1	22
20.5	23	The actions we implemented for our prototype include:
31.1	24
20.5	25	* Playing music
	26	* Listening and understanding the PwD
	27	* Speaking to the PwD
	28	* Displaying information on the tablet
	29	* Moving arms to convey message
6.1	30
20.5	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.
8.1	32
20.4	33	= Iterative Process =
31.1	34
29.1	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:
31.1	36
33.1	37	1. Perform a research overview of how Pepper works, and look into the Interactive Robotics platform and Choregraphe
32.1	38	1. Make simple initial behaviours on Choregraphe (unrelated to our use cases) tested with the virtual robot
	39	1. Make some simple behaviours for our use cases tested with the virtual robot
34.1	40	1. Review implemented behaviours using physical version of Pepper
32.1	41	1. Make some adjustments and debug according to observed behaviours of previous iteration
	42	1. Add new behaviours and test once again with physical version of Pepper
	43	1. Test and improve the final behaviours!
20.4	44
38.1	45	= PACT analysis =
31.1	46
22.2	47	People perform activities in specific contexts with technologies, which affect the situated activities, which set new user requirements.
20.4	48
23.1	49	Using this method leads to a cyclic process of progression as can be seen on the image [1] below presented during the lecture.
22.2	50
23.1	51	[[image:PACT.png\|\|width="700" height="576"]]
22.2	52
34.1	53	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 lectures.
20.4	54
	55
16.1	56	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.
12.1	57
23.1	58	[1]: Benyon, David (2019). Designing User Experience: A Guide to HCI, UX and Interaction Design. Pearson UK.