Wiki source code of Mathieu Jung-Muller

Version 25.1 by Mathieu Jung-Muller on 2022/04/02 00:24

Hide last authors
Mathieu Jung-Muller 8.1 1 French engineering student doing the CS Masters in TUD for a double degree.
2 //I enjoy writing code and programming for something else than computer science itself (biology, social sciences, teaching, etc). For this reason, I am really motivated by this course as it provides the opportunity to create a prototype of a robot agent that would have a real positive impact on people and society.//
3
Mathieu Jung-Muller 5.1 4 **Week 1:**
5 For this week, we had to decide in which direction we wanted to go. For this reason, we split research to do among the six of us.
6 My part was focused on how old people interact with technology, and how to make it the most adapted for the elderly.
7 We met on Sunday to put all our research together and decide the specifics for our project.
Mathieu Jung-Muller 3.1 8
Mathieu Jung-Muller 5.1 9 **Week 2:**
10 I was tasked this week with "IT tasks".
11 I had to check Interactive Robotics first, to see whether it would be adapted for our needs.
12 It turned out this platform seemed too simple for what we wanted to do, and I thus told the team that we should move to Choregraphe instead, to be able to implement our own Python blocks as well as customize those that already exist whenever we need it.
13 I watched tutorials and built some dummy behaviours to get started on Choregraphe.
Mathieu Jung-Muller 10.1 14 I also started to try and understand how to do the activity part for our project, with little success however.
Mathieu Jung-Muller 3.1 15
Mathieu Jung-Muller 5.1 16 **Week 3:**
Mathieu Jung-Muller 10.1 17 I read Wikis from other groups, and realized we were a bit late compared to them, so I updated most of our wiki pages.
18 I continued on the activity behaviour on Choregraphe and discussed it with Manolo, we made some progress on it.
Mathieu Jung-Muller 11.1 19 I wrote an activity behaviour on Choregraphe, that works on the virtual robot. I also made one with speech recognition, so that we can test it the week later when we book a real robot. I also wrote the reminder behaviour.
Mathieu Jung-Muller 12.1 20
21 **Week 4:**
Mathieu Jung-Muller 15.1 22 I made a behaviour that we would use for the demo video. We then tested our Choregraphe behaviours on an actual Pepper robot.
Mathieu Jung-Muller 17.1 23 I also wrote all our evaluation plan after we agreed that the one written by my teammates was not adapted. (My evaluation also got updated again afterwards by my teammates.)
24
25 **Week 5:**
Mathieu Jung-Muller 18.1 26 I prepared most of the presentation, then presented.
Mathieu Jung-Muller 17.1 27
Mathieu Jung-Muller 18.1 28 **Week 6:**
29 I implemented the activity that we would use for the evaluation. I also prepared what the participants would do and planned the evaluation in a more general way (make form with availabilities, send messages, etc).
Mathieu Jung-Muller 19.1 30
31 **Week 7:**
Mathieu Jung-Muller 25.1 32 I had to correct the evaluation forms that were not done properly.
33 I improved the Pepper behaviour for the evaluation. I showed to the other team members how to use Choregraphe and how to run the behaviour for the evaluation, as well as telling them what they should say to the participants and how the experiment should be conducted.
Mathieu Jung-Muller 23.1 34 I organized the sessions (which participants and team members should come when). I also did 8 evaluation sessions on Monday and 3 on Thursday. (I took part in two evaluations of other groups as well. I wanted to do the four of them, but was not available.)
Mathieu Jung-Muller 22.1 35 On top of that, I also went through many of our wiki pages to update them based on the comments the professors gave us.
36 I prepared my part of the presentation as well.
37
Mathieu Jung-Muller 24.1 38 **Week 8:**
Mathieu Jung-Muller 22.1 39 I finished the preparation of the presentation, then presented.
Mathieu Jung-Muller 25.1 40 I verified that all our behaviours of the prototype worked properly, before marking the code as final and ready for submission.
41 I also contributed a lot to the wiki, in order to finish the parts that still needed to be done or improved.