Skip to Content
Last modified by Varun Singh on 2023/04/11 12:25
From version 1.1
edited by Ruud de Jong
on 2023/02/13 12:00
Change comment: Imported from XAR
To version 7.1
edited by Varun Singh
on 2023/03/21 12:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -TDP: Human-Robot Group Game Management
1 +TDP: Human-Robot Painting Management
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.RuuddeJong
1 +XWiki.varunsingh3000
Content
... ... @@ -1,38 +1,48 @@
1 -|(% colspan="1" style="width:385px" %)Problem|(% style="width:726px" %)The [[Activity Coordinator>>doc:Main.sdf.Stakeholders.Activity Coordinator.WebHome]] and [[Humanoid Robot>>doc:Main.c\. Technology.Humanoid Robot.WebHome]] have to manage the interactive game play and emerging social behaviors of a group of vulnerable game participants such as [[Person with Dementia>>doc:Main.sdf.Stakeholders.Person with Dementia.WebHome]]. The allocation of tasks should be harmonized to the momentary capacities of the coordinator and robot, the varying needs of the players, and to the context. Pausing the game is part of the game management, as a mitigation strategy for prevention and handling of troubles that appear during the game play.
2 -|(% style="width:385px" %)Solution Structure|(% style="width:726px" %)[[image:129826985.png||height="231" width="539"]]
1 +|(% colspan="1" style="width:385px" %)Problem|(% style="width:726px" %)The painting activity has to be assisted by Pepper not just for an individual PwD but for multiple PwDs. Various considerations like the navigation of the robot, and the interaction with PwD's even though it's for multiple Patients now have to be engaging and motivating. Pepper now has to be able to assist individually multiple patients for which the painting progress of each patient needs to be tracked by Pepper.
2 +|(% style="width:385px" %)Solution Structure|(% style="width:726px" %)(((
3 +[[image:1678815385023-332.png]]
4 +
5 +[[image:1678815402609-918.png]]
6 +)))
3 3  |(% style="width:385px" %)Solution Description|(% style="width:726px" %)(((
4 -All actors (activity coordinator, humanoid robot, players) are **co-located**.
8 +All actors (Pepper, humanoid robot) are present.
5 5  
6 -1. Robot leads the game (i.e., is the game master, GM).
7 -1. Vulnerable game participants play the game (i.e., are the players, PL).
8 -1. Robot reflects on game play.
9 -1. Activity coordinator (CO) supervises players' state and engagement;
10 -11. if (s)he identifies risks for troubles to appear, the coordinator initiates a takeover from scene A (Active) to B (Pause).
11 -11. if (s)he recognizes that the risk for troubles disappeared, the coordinator initiates a takeover (from scene B to A)
12 -1. Activity coordinator starts and leads a social activity,
13 -1. Players socialize under the guidance of the activity coordinator.
14 -1. Robot engages in small talk.
10 +1. Reminds the patient about painting.
11 +1. Recommends them a personal image to paint for better engagement and motivation.
12 +1. Assists them during the painting activity by providing suggestions and instructions.
13 +1. At certain intervals, Pepper would move to another PwD to start Scene A or check up on their progress.
14 +1. If at any point there is an anomaly or emergency, Pepper would automatically alert the caretaker, the patients can also manually call the caretaker if they want to.
15 +1. Once a patient finishes their painting, Pepper can take a picture using its eye cameras.
16 +1. The picture would be saved to a database and then sent to the family members.
17 +1. Pepper would then congratulate the patient for painting such a beautiful picture on their own.
18 +1. The painting activity is done and Pepper would leave to assist other patients with their painting.
15 15  )))
16 16  |(% style="width:385px" %)Human RQ|(% style="width:726px" %)(((
17 -* Player:  Show perceptual and cognitive capabilities to play the game.
18 -* Coordinator: Know the vulnerabilities of the players (memory). Show perceptual and cognitive skills to identify and mitigate risks for troubles in the game play.
21 +* PwD:  Have enough motor skills and cognitive capabilities to paint.
22 +* Caretaker: Know the vulnerabilities of the players (memory). Set up the painting apparatus and if alerted during an emergency, attend to the situation and de-escalate.
19 19  )))
20 20  |(% style="width:385px" %)Machine RQ|(% style="width:726px" %)(((
21 -* [[RQ01.0: Lead the bingo game>>doc:2\. Specification.Requirements.RQ01\.0\: Lead the bingo game.WebHome]]
22 -* [[RQ02.0: Personalize game assignments>>doc:2\. Specification.Requirements.RQ02.WebHome]]
23 -* [[RQ03.0: Reflect on game performance>>doc:2\. Specification.Requirements.RQ03\.0\: Reflect on game performance.WebHome]]
24 -* [[RQ04.0: Respond to players conversations.>>doc:2\. Specification.Requirements.RQ04\.0\: Respond to players conversations\..WebHome]]
25 +* [[RQ1: Knowledge about painting>>path:/xwiki/wiki/sce202302/view/2.%20Specification/Requirements/RQ1%3A%20Knowledge%20of%20different%20painting%20styles/]]
26 +* [[RQ2: Engage the PwD>>path:/xwiki/wiki/sce202302/view/2.%20Specification/Requirements/RQ2%3A%20Engage%20the%20PwD/]]
27 +* [[RQ3: Capture and store a picture of the painting>>path:/xwiki/wiki/sce202302/view/2.%20Specification/Requirements/RQ3%3A%20Capture%20and%20store%20a%20picture%20of%20the%20painting/]]
28 +* [[RQ4: Remote interface for the family members>>path:/xwiki/wiki/sce202302/view/2.%20Specification/Requirements/RQ4%3A%20Remote%20interface%20for%20interaction/]]
25 25  )))
26 26  |(% style="width:385px" %)Consequences|(% style="width:726px" %)(((
27 -**+** Offload of coordinator so that (s)he can concentrate on advancing players individual and social experiences.
31 +**+** Reduction of workload for caretaker so that (s)he can concentrate on other more critical tasks.
28 28  
29 -**~ -** The game play may be constrained by robot's limitations to sense and understand players' game experience
33 +**~ -** The painting activity may be constrained by the robot's limitations of not accurately being able to help out the patient since the suggestions given are general.
30 30  )))
31 31  |(% style="width:385px" %)Grounding|(% style="width:726px" %)(((
32 -Status: Proto Pattern.
36 +Status: Interactive Design Pattern.
33 33  
34 -Instantiations: [[UC01.0: Music Bingo>>doc:2\. Specification.b\. Use Cases.UC01\.0\: Music Bingo.WebHome]].
38 +Instantiations: [[Use Case - Remind PwD to paint.>>doc:2\. Specification.b\. Use Cases.WebHome]]
35 35  )))
36 -|(% style="width:385px" %)Related Patterns|(% style="width:726px" %)[[IDP: Title>>doc:Design Patterns.Interaction Design Patterns.IDP\: Title.WebHome]]
40 +|(% style="width:385px" %)Related Patterns|(% style="width:726px" %)(((
41 +IDP: [[Remind PwD to paint>>doc:Design Patterns.Interaction Design Patterns.IDP\: Title.WebHome]]
37 37  
38 -
43 +IDP: [[Help PwD to paint>>doc:Design Patterns.Interaction Design Patterns.IDP\: Explain a Group Activity.WebHome]]
44 +
45 +IDP: [[Save a picture of the painting>>doc:Design Patterns.Interaction Design Patterns.IDP\: Save a picture of the painting.WebHome]]
46 +
47 +IDP: [[Recommend a meaningful picture to paint>>doc:Design Patterns.Interaction Design Patterns.IDP\: Recommend a meaningful picture to paint.WebHome]]
48 +)))
1678815385023-332.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.varunsingh3000
Size
... ... @@ -1,0 +1,1 @@
1 +70.7 KB
Content
1678815402609-918.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.varunsingh3000
Size
... ... @@ -1,0 +1,1 @@
1 +33.5 KB
Content