Wiki source code of Timetable
Version 41.1 by Laura Ottevanger on 2022/03/31 10:02
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | Week 1: | ||
2 | In the meeting (8-2) tasks were divided. Deadline is before the meeting next week. | ||
3 | |||
4 | Ricardo: Work on the report: Personas and problem scenario | ||
5 | Rohan: Work on the report: Operational demands: environments and stakeholders | ||
6 | Doreen: See if Bluetooth connection with Miro would be possible (and if we can check distance) | ||
7 | Jeffrey: Look at the basic behavior of the Miro robot (and maybe try it a bit) | ||
8 | Harmen: Look into the sounds help | ||
9 | Tim: Check if the Miro robot can listen to a name/respond to a name | ||
10 | Laura: Check and possibly code a path tracking possibility in Miro | ||
11 | |||
12 | Reflection on Week 1: | ||
13 | Ricardo made personas. Rohan made the Environments and Stakeholders. | ||
14 | Doreen made connections between her phone and an Arduino and was able to let the Arduino detect when the distance was too great. | ||
15 | The accounts weren't there yet so Harmen, Jeffrey, Tim and Laura did some research on the necessary packages and code. | ||
16 | |||
17 | Week 2: | ||
18 | Ricardo: Personas & persona scenarios | ||
19 | Rohan: Robotic Partner / Music recognition | ||
20 | Harmen: Problem scenarios | ||
21 | Doreen: State diagram / Leash | ||
22 | Tim: Commandos/voice recognition, help with personas & scenarios | ||
23 | Jeffrey: Look into basic behaviour, what does the dog do when touched/petted etc. | ||
24 | Laura: Look into pathmaking | ||
25 | |||
26 | Reflection on Week 2: | ||
27 | Ricardo extended the personas and made persona scenario. | ||
28 | Rohan made the part on Robotic Partner and Music recognition | ||
29 | Harmen made the problem scenario. | ||
30 | Doreen made a flowchart about the behavior of the robot. | ||
31 | Laura made the first storyboard. | ||
32 | Jeffrey tested out with the blockly environment and the Python conversion. | ||
33 | Tim did research on voice recognition and which Python packages are necessary to implement that | ||
34 | Wednesday morning we went to the robot lab and were able to upload a basic program to the robot. | ||
35 | |||
36 | Week 3: | ||
37 | Ricardo: Design Patterns | ||
38 | Rohan: Claims | ||
39 | Harmen: Ontology | ||
40 | Doreen: Extending problem scenario, installing MDK. | ||
41 | Tim: Objectives, Humanoid Robot, name recognition (Is it possible without the mdk) | ||
42 | Jeffrey: Use cases, figure out object/wall detection | ||
43 | Laura: Storyboards, test program | ||
44 | |||
45 | Reflection on week 3: | ||
46 | Ricardo made the Design Patterns with a drawing of the system. | ||
47 | Rohan made the claims | ||
48 | Harmen: Figured out the program to create an ontology but did not create the ontology yet. | ||
49 | Doreen installed the MDK and made an explanation on how to install it. Doreen did not extend the problem scenario yet. | ||
50 | Tim made the Objectives and worked on humanoid Robot. Tim also found some Python libraries for name recognition. Tim also made user value stories at stake holders. | ||
51 | Jeffrey took a look into use cases but did not make them yet. | ||
52 | Laura made the storyboards and some test programs to test the robots. | ||
53 | |||
54 | Week 4: | ||
55 | |||
56 | Ricardo: Specify design patterns + human factors design patterns. | ||
57 | Rohan: Evaluation + Presentation 1 | ||
58 | Harmen: Ontology + human factors ontology | ||
59 | Doreen: Extend problem scenario + work on wristband for prototype + Prototype + make a "hondenriem" prototype out of cardboard | ||
60 | Tim: Extend functions + specify design patterns | ||
61 | Jeffrey: Use Cases + presentation 1 | ||
62 | Laura: Evaluation + Presentation 1 | ||
63 | |||
64 | We are going to create small videos: | ||
65 | Snoezelen = demoversion of Miro | ||
66 | Wristband = Doreen creates is with Arduino | ||
67 | Walking = Wizard of Oz with remote control | ||
68 | |||
69 | When person with dementia walks in the wrong direction: follow the person, make a sound/bark, turn head as if confused, turn back in correct direction, walk some steps, check if the dog is followed = Harmen | ||
70 | Ask for attention: (bark as real dog) = Doreen | ||
71 | Positive response: wagging, turn ears, yap = Laura | ||
72 | |||
73 | Reflection on week 4: | ||
74 | Ricardo: Worked on design patterns and the human factors design patterns | ||
75 | Tim: Worked on design patterns and the human factors design patterns. Extended/rewrote functions and found parts to discuss about it. | ||
76 | Rohan: Made a start on evaluation, made the presentation and presented the presentation. | ||
77 | Harmen: Made ontology. Started on human factors ontology, made some code for demo | ||
78 | Doreen: Extended problem scenario, started working on a physical prototype | ||
79 | Jeffrey: Made use cases, presented presentation | ||
80 | Laura: Made and presented the presentation, made a start on evaluation, made some code for demo. | ||
81 | |||
82 | Week 5: | ||
83 | Ricardo: Going to work on ethics + test if we can connect miro to a server and/or with packets | ||
84 | Tim: Design pattern diagrams + reread all XWiki pages to check for consistency and todo's + refactor some pages | ||
85 | Doreen: Elaborate on evaluation + collaborate with Rohan on experimental setup | ||
86 | Rohan: Elaborate on evaluation + collaborate with Doreen on experimental setup | ||
87 | Harmen: Extra ontology schema + human factors ontology + research on existing robot dogs | ||
88 | Laura: Also do some research on existing robot dogs + make 4 prototypes/code: snoezelen 1,2,3 + alarm mode | ||
89 | Jeffrey: Make some MiRo code for an alarm when a PwD falls and for snoezelen with different levels of movement. | ||
90 | |||
91 | Reflection on Week 5: | ||
92 | Ricardo: Worked on ethics. | ||
93 | Tim: reread all XWiki pages to check for consistency and made a full to-do list for the rest of the project. Also gave feedback on the evaluation form. | ||
94 | Doreen: Elaborated evaluation + worked on experimental setup | ||
95 | Rohan: Elaborated evaluation + worked on experimental setup + created and worked on the questionnaire | ||
96 | Harmen: Due to Harmen being sick, he worked a little bit on some research for existing robot dogs but couldn't finish ontology | ||
97 | Laura: Started on some research on existing robot dogs + made 4 prototypes/code: snoezelen 1,2,3 + alarm mode | ||
98 | Jeffrey: Made and tested the four pieces of code Wednesday. | ||
99 | |||
100 | We decided to combine the pieces of code for alarm from Jeffrey and Laura to create an alarm mode. The snoezelen we decided to scrap as we noticed that it would be difficult to test snoezelen with the Miro, the miro is too easy to break | ||
101 | |||
102 | == Todos == | ||
103 | Format: Assignee | Todo | ||
104 | === Specification === | ||
105 | Objectives: | ||
106 | - Jeffrey | Expand product vision with Snoezelen and check incorporation in objectives | ||
107 | |||
108 | Use cases: | ||
109 | --- Laura | Review use cases-- | ||
110 | |||
111 | Functions: | ||
112 | - Tim | Update flowchart to remove snoezelen to be coherent with current idea of MiRo | ||
113 | - Tim | --Add textual description of walking with MiRo to incorporate what MiRo should do if PwD stops to talk during walk-- | ||
114 | Claims: | ||
115 | - --Rohan | Review current claims and perhaps add upon sections with small amounts of text/description-- | ||
116 | - --Rohan | Add sources on why autonomy is important (basically just link to Self Determination Theory)-- | ||
117 | - --Rohan | Check if we can validate claims with evaluation-- | ||
118 | |||
119 | Future work: | ||
120 | --- Laura | Add future work page indicating our future work, and also that we would have liked to incorporate snoezelen-- | ||
121 | |||
122 | === Foundation === | ||
123 | ====Operational demands ==== | ||
124 | Environments: | ||
125 | - Jeffrey | Expand and clarify technologies | ||
126 | |||
127 | Stakeholders: | ||
128 | - Tim | Create value stories for indirect stakeholders | ||
129 | - Tim | Incorporate Schwartz value model in the value stories | ||
130 | |||
131 | Personas: | ||
132 | - Ricardo | Lecture slides state "Persona's need to have goals". Cornelia and Constantijn have these (to some extent), but Marcus does not yet | ||
133 | --- Ricardo | Create technology disliking persona scenario-- | ||
134 | --- Ricardo | Create for each scenario a 'before' and 'after technology' piece-- | ||
135 | |||
136 | Problem scenario: | ||
137 | --- Doreen | Add sources for self-determination theory claims-- | ||
138 | --- Doreen | Look into "Design scenario's" (lecture 3 probably): a story that conveys a new vision, including activity: narratives of typical or critical services, information: details on info provision, interaction: details of user interaction & feedback-- | ||
139 | |||
140 | ====Human Factors==== | ||
141 | Robotic partner: | ||
142 | --- Laura | Elaborate on limitations of MiRo w.r.t. snoezelen-- | ||
143 | --- Unassigned | Describe what MiRo could mean as a robotic partner for elderly people / PwD. Perhaps this is not that relevant anymore to write here since snoezelen will be moved to future work.-- | ||
144 | - Laura + Harmen| Add research on interactions between elderly people and/or PwD's and robots + any other relevant research on effect of pets/robots on PwD's. | ||
145 | |||
146 | Design patterns: | ||
147 | - Ricardo | Make team design pattern into something that is not drawn | ||
148 | - Ricardo | Make team design pattern including the caretaker | ||
149 | - Ricardo | Create diagrams for IDP's | ||
150 | |||
151 | Ontology: | ||
152 | - Harmen | Add ontology image to XWiki | ||
153 | |||
154 | Music and Cognition: | ||
155 | - Tim | Describe each single signal, sound, movement that the PwD will receive/MiRo will make, the reasoning behind it and its desired effect | ||
156 | - Tim | Link to Technology - Music Management for the explanation why we do not use music. | ||
157 | |||
158 | Measuring instruments: | ||
159 | We do not yet know what should be here. | ||
160 | |||
161 | Group's core theoretical foundation: | ||
162 | - Unassigned | Add all sources here at the end of the project? | ||
163 | |||
164 | Inclusive design: | ||
165 | --- Doreen | Write this page-- | ||
166 | |||
167 | Human-Agent teamwork: | ||
168 | We do not yet know what should be here. | ||
169 | |||
170 | ==== Technology ==== | ||
171 | Humanoid robot: | ||
172 | --Done-- | ||
173 | |||
174 | Music management: | ||
175 | - Jeffrey | Explain why music is not suitable for our goal/case | ||
176 | |||
177 | ==== Report ==== | ||
178 | Unassigned | Proofread | ||
179 | Unassigned | Consistent use of MiRo (Change every mention of Miro to MiRo) | ||
180 | Unassigned | Talk about the name WAF (Walking Assisting Friend) | ||
181 | Unassigned | The group's core foundation | ||
182 | --Doreen | Write in Evaluation -> Test about the little interview I had with Erik and how the product was perceived by a hard of hearing person. | ||
183 | -- | ||
184 | |||
185 | |||
186 | |||
187 | |||
188 | =Todo list 2.0= | ||
189 | If you are assigned to a page, please also read the existing text and check for grammatical mistakes. If you are assigned a page, please put an introduction to that page for example: "In this chapter, we will introduce you to our Personas. Personas are <explanation of personas>. Personas are relevant because <enter text here>.". Please explain, what it is and why we use it if relevant. | ||
190 | |||
191 | == Introduction == | ||
192 | Laura | Introduction - Rewrite: problem, solution, what is where. | ||
193 | Laura | Move MiRo difficulties to Technology | ||
194 | |||
195 | == Foundation == | ||
196 | ==== Operational Demands ==== | ||
197 | |||
198 | === Environments and Personas === | ||
199 | Ricardo | Write 2 sentences as intro on basic Operational Demands page. | ||
200 | Ricardo | Read and check if correct | ||
201 | |||
202 | === Stakeholders and Problem Scenario === | ||
203 | Harmen | Write 2 sentences as intro on basic Operational Demands page. | ||
204 | Harmen | Read and check if correct | ||
205 | |||
206 | |||
207 | ==== Human Factors ==== | ||
208 | |||
209 | ==== Robotic Partner ==== | ||
210 | Unassigned | Read through and add one citation in the todo | ||
211 | |||
212 | ==== Music and Cognition ==== | ||
213 | Tim and Jeffrey (whoever gets to it first) | Explanation how doglike sounds could be beneficial based in literature. | ||
214 | = Design Pattern and Ontology = | ||
215 | Harmen and Ricardo | Cite some references | ||
216 | |||
217 | ==== Measuring Instruments ==== | ||
218 | Rohan and Doreen? | cite papers about what we use for evaluation | ||
219 | |||
220 | ==== Group's core theoretical foundation ==== | ||
221 | Unassigned and Unassigned | Talk about people with dementia getting lost, if walking helps by PwD, how good walking is for people, budget care homes | ||
222 | |||
223 | ==== Inclusive Design ==== | ||
224 | Doreen (Unassigned) | Clean up sources or notify what needs to be done on the page | ||
225 | |||
226 | ==== Human-agent Teamwork ==== | ||
227 | Unassigned and Unassigned | Talk about humans and robots working together based in literature | ||
228 | |||
229 | === Technology === | ||
230 | ==== Humanoid Robot ==== | ||
231 | Laura | Specify specific limitations and technical options for MiRo | ||
232 | |||
233 | ==== Music Management ==== | ||
234 | Tim and Jeffrey (whoever gets to it first) | Explanation why we do not use music + what we do use + talk about video of alarm here | ||
235 | |||
236 | == Specification == | ||
237 | === Objectives === | ||
238 | Unassigned | Remove Snoezelen and expand Objectives | ||
239 | |||
240 | === Use cases === | ||
241 | Unassigned | Read through and check for (grammatical) mistakes | ||
242 | |||
243 | === Functions === | ||
244 | Unassigned | Add reference to future work page. | ||
245 | |||
246 | === Claims === | ||
247 | Harmen | Expand Claims | ||
248 | |||
249 | == Evaluation == | ||
250 | === Prototype === | ||
251 | Laura | Add code to Github, | ||
252 | Laura | Talk about code in Prototype chapter | ||
253 | |||
254 | === Test === | ||
255 | Unassigned | Rewrite to make a bit more specific, ensure that the test is reproduceable, add Wilcoxon test | ||
256 | Unassigned | Add Discussion after the results and ensure that results is just numbers | ||
257 | |||
258 | == Design Patterns == | ||
259 | Ricardo | Reread and change picture | ||
260 | Ricardo | Add caretaker in team design pattern | ||
261 | Ricardo | Picture for IDP | ||
262 | |||
263 | == Ontology == | ||
264 | Harmen | Add second Ontology | ||
265 | |||
266 | == Planning == | ||
267 | Unassigned | Rewrite todo-list as a per week description of what happened | ||
268 | (Optional) Unassigned | Put everything into a nice table like: [[Timetable table >> https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group02/view/Timetable/TimeTable%20Table%20Format/]] | ||
269 | |||
270 | == Conclusion == | ||
271 | === Future Work === | ||
272 | Unassigned and Laura | Add limitations and how we would solve it in future work. | ||
273 | Unassigned | Talk about having only 8 participants, not a correct room (not a carehome hallway but single room), using PwD as test subjects = more realistic test. | ||
274 | Unassigned | Suggestions for other tests from presentation = test way of attention grabbing | ||
275 | === Conclusion === | ||
276 | Unassigned | Write a nice end chapter/conclusion on how it went and summarizing results. |