Wiki source code of Timetable

Version 29.1 by Rohan Sobha on 2022/03/18 16:05

version	line-number	content
1.1	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.
2.1	15	The accounts weren't there yet so Harmen, Jeffrey, Tim and Laura did some research on the necessary packages and code.
1.1	16
	17	Week 2:
2.2	18	Ricardo: Personas & persona scenarios
1.1	19	Rohan: Robotic Partner / Music recognition
	20	Harmen: Problem scenarios
	21	Doreen: State diagram / Leash
3.1	22	Tim: Commandos/voice recognition, help with personas & scenarios
1.1	23	Jeffrey: Look into basic behaviour, what does the dog do when touched/petted etc.
	24	Laura: Look into pathmaking
2.1	25
	26	Reflection on Week 2:
2.2	27	Ricardo extended the personas and made persona scenario.
2.1	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.
3.1	41	Tim: Objectives, Humanoid Robot, name recognition (Is it possible without the mdk)
2.1	42	Jeffrey: Use cases, figure out object/wall detection
	43	Laura: Storyboards, test program
4.1	44
	45	Reflection on week 3:
	46	Ricardo made the Design Patterns with a drawing of the system.
	47	Rohan made the claims
5.1	48	Harmen: Figured out the program to create an ontology but did not create the ontology yet.
4.1	49	Doreen installed the MDK and made an explanation on how to install it. Doreen did not extend the problem scenario yet.
7.1	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.
6.1	51	Jeffrey took a look into use cases but did not make them yet.
4.1	52	Laura made the storyboards and some test programs to test the robots.
5.1	53
	54	Week 4:
	55
8.1	56	Ricardo: Specify design patterns + human factors design patterns.
	57	Rohan: Evaluation + Presentation 1
	58	Harmen: Ontology + human factors ontology
11.1	59	Doreen: Extend problem scenario + work on wristband for prototype + Prototype + make a "hondenriem" prototype out of cardboard
8.1	60	Tim: Extend functions + specify design patterns
	61	Jeffrey: Use Cases + presentation 1
	62	Laura: Evaluation + Presentation 1
9.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
12.1	71	Positive response: wagging, turn ears, yap = Laura
13.1	72
14.1	73	Reflection on week 4:
	74	Ricardo: Worked on design patterns and the human factors design patterns
15.1	75	Tim: Worked on design patterns and the human factors design patterns. Extended/rewrote functions and found parts to discuss about it.
14.1	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.
13.1	81
	82	Week 5:
14.1	83	Ricardo: Going to work on ethics + test if we can connect miro to a server and/or with packets
15.1	84	Tim: Design pattern diagrams + reread all XWiki pages to check for consistency and todo's + refactor some pages
14.1	85	Doreen: Elaborate on evaluation + collaborate with Rohan on experimental setup
13.1	86	Rohan: Elaborate on evaluation + collaborate with Doreen on experimental setup
14.1	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
24.1	89	Jeffrey: Make some MiRo code for an alarm when a PwD falls and for snoezelen with different levels of movement.
15.1	90
19.1	91	Reflection on Week 5:
	92	Ricardo: Worked on ethics.
28.1	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.
19.1	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
27.1	98	Jeffrey: Made and tested the four pieces of code Wednesday.
15.1	99
27.1	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
19.1	101
20.1	102	== Todos ==
15.1	103	Format: Assignee \| Todo
	104	=== Specification ===
	105	Objectives:
25.1	106	- Jeffrey \| Expand product vision with Snoezelen and check incorporation in objectives
16.1	107
15.1	108	Use cases:
25.1	109	- Laura \| Review use cases
15.1	110
	111	Functions:
	112	- Tim \| Update flowchart to remove snoezelen to be coherent with current idea of MiRo
18.1	113	- Tim \| --Add textual description of walking with MiRo to incorporate what MiRo should do if PwD stops to talk during walk--
15.1	114	Claims:
29.1	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--
15.1	118
16.1	119	Future work:
20.1	120	- Laura \| Add future work page indicating our future work, and also that we would have liked to incorporate snoezelen
16.1	121
15.1	122	=== Foundation ===
	123	====Operational demands ====
	124	Environments:
24.1	125	- Jeffrey \| Expand and clarify technologies
15.1	126
	127	Stakeholders:
	128	- Tim \| Create value stories for indirect stakeholders
	129	- Tim \| Incorporate Schwartz value model in the value stories
	130
20.1	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
23.1	133	--- Ricardo \| Create technology disliking persona scenario--
26.1	134	--- Ricardo \| Create for each scenario a 'before' and 'after technology' piece--
15.1	135
	136	Problem scenario:
20.1	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
15.1	139
	140	====Human Factors====
	141	Robotic partner:
20.1	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.
15.1	145
	146	Design patterns:
	147	- Tim \| Make team design pattern into something that is not drawn
	148	- Tim \| Make team design pattern including the caretaker
	149	- Tim \| Create diagrams for IDP's
	150
	151	Ontology:
	152	- Harmen \| Add ontology image to XWiki
	153
	154	Music and Cognition:
17.1	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.
15.1	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:
20.1	165	- Doreen \| Write this page
15.1	166
	167	Human-Agent teamwork:
	168	We do not yet know what should be here.
	169
	170	==== Technology ====
	171	Humanoid robot:
21.1	172	--Done--
15.1	173
	174	Music management:
25.1	175	- Jeffrey \| Explain why music is not suitable for our goal/case
15.1	176
27.1	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)
15.1	181