Project homeWiki source code of TDP: Human-Robot Painting Management
Version 4.1 by Varun Singh on 2023/03/14 18:36
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
2.1 | 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" %)((( | ||
| |
4.1 | 3 | [[image:1678815385023-332.png]] |
| |
2.1 | 4 | |
| |
4.1 | 5 | [[image:1678815402609-918.png]] |
| |
2.1 | 6 | ))) |
 |
1.1 | 7 | |(% style="width:385px" %)Solution Description|(% style="width:726px" %)((( |
| |
2.1 | 8 | All actors (Pepper, humanoid robot) are present. |
| |
1.1 | 9 | |
| |
2.1 | 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 it's 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. | ||
| |
1.1 | 19 | ))) |
| 20 | |(% style="width:385px" %)Human RQ|(% style="width:726px" %)((( | ||
| |
2.1 | 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. | ||
| |
1.1 | 23 | ))) |
| 24 | |(% style="width:385px" %)Machine RQ|(% style="width:726px" %)((( | ||
| 25 | * [[RQ01.0: Lead the bingo game>>doc:2\. Specification.Requirements.RQ01\.0\: Lead the bingo game.WebHome]] | ||
| 26 | * [[RQ02.0: Personalize game assignments>>doc:2\. Specification.Requirements.RQ02.WebHome]] | ||
| 27 | * [[RQ03.0: Reflect on game performance>>doc:2\. Specification.Requirements.RQ03\.0\: Reflect on game performance.WebHome]] | ||
| 28 | * [[RQ04.0: Respond to players conversations.>>doc:2\. Specification.Requirements.RQ04\.0\: Respond to players conversations\..WebHome]] | ||
| 29 | ))) | ||
| 30 | |(% style="width:385px" %)Consequences|(% style="width:726px" %)((( | ||
| 31 | **+** Offload of coordinator so that (s)he can concentrate on advancing players individual and social experiences. | ||
| 32 | |||
| 33 | **~ -** The game play may be constrained by robot's limitations to sense and understand players' game experience | ||
| 34 | ))) | ||
| 35 | |(% style="width:385px" %)Grounding|(% style="width:726px" %)((( | ||
| 36 | Status: Proto Pattern. | ||
| 37 | |||
| 38 | Instantiations: [[UC01.0: Music Bingo>>doc:2\. Specification.b\. Use Cases.UC01\.0\: Music Bingo.WebHome]]. | ||
| 39 | ))) | ||
| 40 | |(% style="width:385px" %)Related Patterns|(% style="width:726px" %)[[IDP: Title>>doc:Design Patterns.Interaction Design Patterns.IDP\: Title.WebHome]] |