Logbook group 8

This is the logbook of PRE2020 3 Group8

Week 1

Meeting Monday 1 February

Topics:

• Introducing ourselves to group
• Figuring out how wiki works
• Discussion of ideas, organization
• Create GitHub repository
• Create Discord server for communication
• Next meeting: Thursday 4 February 2021

Done

• All: meeting (70 min) (Emi took notes: [1])

Do for next time:

• Search for literature, read a bit -> figure out what feasible, what already done (State of Art), what is new about our idea
• [optionally] write down ideas, summaries, edit wiki, etc.

Week 2

The wiki was down for most of the week

Meeting 11 February

Main decisions:

• We are going to narrow the variables that will be recorded down. Emi and Fanni are deciding which information needs to be gathered and how it should be presented back to users.Having the users decide on which variables to track made it difficult to research how people could be motivated,as most scientific studies focus on motivation in a very specific context.
• Edwin and Lulof are going to do literature research how to create an anthropomorphized interface.
• Morris is still researching the GUI.

Carnival Holiday

Meeting 15 February

Only with software subteam (Edwin, Lulof & Morris)

Agenda

• Current state:
  • Psychology team decides what data to track and how to give feedback based on it.
  • Need at least a database.
  • Need at least a GUI.
  • Decided that try to increase user-engagement and perceived social presence via anthropomorphism.
• Discuss literature research
  • Mixed results on what does and what does not work.
  • Responses that take context into account seem to work significantly.
• Decide how to continue
  • More research?
  • Make programming plan?
  • Individual tasks and deadlines.
• Inform psychology team on results of meeting.

Minutes

• Extensive discussion of literature.
• Graphs may provide better insight that a textual description.
• We keep the restricted input. Since users need to input the same data every day, it does not make sense to ask for complete sentences every day.
• We will focus on natural language generation.
  • Whether we will use GANs or other architectures requires more background research.
  • We will explain the output in a way that is not the same every day.
  • We may accompany the output with graphs and numeric data. Perhaps we could generate a textual description of the data presented.
• Morris is playing around with the Kivy framework, to figure out what it can do. It appears promising and efficient.
• Planning:
  • Week 3: Lulof -> Create design for communication between components. This will be a UML class diagram.
  • Week 3: Edwin & Lulof -> read more on Natural Language Generation. Experiment where possible.

Week 3

Meeting 24 February 2021

Present: Lulof & Edwin

• Discuss of class diagram of communication components, managing questions and answers, output rules, etc.
• Discuss challenges RNN.

Plans:

• Start with question generating part while also reading Dialogue generation literature.
• Code sessions:
• Tuesday 13:30 ~ 17:00
• Thursday 10:00 ~12:00 (One time: Friday 24 February 10:00 ~ 12:00)
• Use unittest (Python)
• Make installable package

Meeting 25 February 2021

Present: everyone

• Lulof and Edwin worked on the backend design
• Morris worked on the GUI. He already got a textbox, shapes (smiley) and buttons
• Fanni and Emi described user cases, with specific characters, and extended the Wiki
  • User-centered Design
  • Economical perspective
  • Problem statement and objectives

Do for next time:

• Read each others work (Wiki, class diagram, etc)

Meeting with teacher:

• The wiki uses outdated software, that is why many things broke and are still broken.
• No strict set of requirements. Present what you know and what you have. Important to reflect and communicate. Technical part must be aligned well with user analysis part. Really need to solve a problem.
• Do use academic style argumentation.
• Ensure that things come together at the end. Prevent people specializing and forgetting to communicate.
• Time sheets are not required. But an overview of who did what is useful for the teachers.
• Minutes especially useful for decisions and recording who did what, not required by teachers.
• It is possible to customize the style (font, fontsize, etc.) of the wiki page.

Lulof Logbook

Week 1

• Update wiki page (abstract, logbook, etc.) [0.5h]
• Look up papers [1.5h]
• Read and summarize Li et al. (2016) [~5h:10min] --> Progress delayed due to issues with displaying math
• Visualize idea of organizing task division/software architecture [0.5h]
• Read NLP paper [2h]
• Meeting Friday [2:18]
• Read papers about GANs [6:40]

Week 2

• Meeting Monday [1h]
• Create this log [10 min]
• Work on user description, goals, fallacies and software milestones [1:50h]
• UML Use case diagram (30 min)
• Meeting Thursday [2h]
• Fixing wiki, starting literature research [1h]
• Literature research on anthropomorphism [6:00]

Carnival holiday

• Meeting Monday [1:17]

Week 3

• Class diagram for question production and storage [3:24]
• Update class diagram: add output process and update question process [2:21]
• Meeting with Edwin [~50 min]
• Large Thursday meeting [1:36]
• Friday coding session with Edwin (set up directories, Variable, create db file) [2:09]
• Sunday: work on database, functions to set it up and add variables (incl. testcases) [2:43]

Week 4

• Monday: implement remaining (i.e. most) database functions and DatabaseWriter [3:37]