Changes for page Humanoid Robot

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,25 +1,45 @@
	1	+= Robot Choice =
1	1	For this project on dementia, we chose to make use of a semi-humanoid robot namely [[Pepper>>https://www.softbankrobotics.com/emea/en/pepper]].
2	2
	4	+-> Need to find/write reasons
	5	+
	6	+
	7	+= Pepper Description =
3	3	Pepper is a robot that allows easy communication robot/user, thanks to its ability kit that includes:
	9	+* Speech recognition
4	4	* Voice
5	5	* Tablet
6		-* Cameras
	12	+* Cameras
7	7	* Humanoid form
8	8
9	9	The image below refers all the robot sensors.
10		-[[image:Pepper-robot-sensors-18.png]]
	16	+[[image:Pepper-robot-sensors-18.jpg]]
11	11
	18	+= Pepper usage =
	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.
12	12
13		-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.
	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
14	14
15		-We tried to make full use of the sensors provided within Pepper. As we had limited amount of time we mainly focused on using:
	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.
16	16
	30	+= Iterative Process =
	31	+-> Describe a bit a philosophy from slides: SCE framework & PACT analysis.
17	17
18		-In assumption, we planned to make it possible for the HCP to modify the calendar/reminder
19		- 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.
	33	+based on:
20	20
21		-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
22		-improve the efficiency of communication between them, but also makes PwDs feel more cared.
	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.
23	23
	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	+
24	24	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.
25	25
	45	+