|
Wk02: Social Robots and Agents
Page last edited by Per Bækgaard (pgba) 18/01-2021
Social Robots are (autonomous) systems that are designed to interact with humans (or other robots) following social behaviour and rules. Social Robots in a strict sense is physically embodied, whereas Social Agents may exists primarily as a representation on computer system.
This week will focus on designing systems that incorporate elements of (social) interaction between fully or semi-autonomous systems and humans, using a broad definition of the term. Such systems may need to adapt more to humans than the other way round.
One element of this is to communicate the intent of the robot (or the person controlling it) in a way that can be understood even by users without prior training that may accidentally encounter the system. In addition to allowing observers to perceive the system state, there is often a need to interact with the system by the same untrained users.
One way of doing this is create some kind of embodied human-like interface on the system, but there are other ways too. This way, humans may perceive the system having agency (even if it doesn't "think" in any traditional way ascribed to human agents).
Examples within scope could be systems like (or similar to or based on):
The week will generally follow the overall concept of the course, with (daily) build-measure-learn cycles.
This page will be continuously updated through the week; the schedules below are therefore only tentative.
09:45: Group work (discord; research examples of robots and their interfaces and create your own ideas)
13:00: Lunch break
14:00: Inspirational lecture on robots by Professor John Paulin Hansen ( recorded lecture)
15:30: Group work (discord; create a lean canvas and landing page of your idea)
17:00: Hand-In to DTU Inside of your rough idea (lean canvas and landing page named GroupNN_xxx.pdf)
Assignment
- You will this week create a system of your own choice that employs elements of social robotics, interfacing with users. You may look at some of the existing solutions mentioned above for ideas to get you started or read some of the papers listed below. Include proper literature study/research.
-
Hold your own small brainstorming workshop within the group (you may find some ideas here or here, just adapt the program to the time you have available -- 45-60 min for each group), identifying problems and pain points (define) that could benefit from a social robotic solution, and generate multiple ideas (ideate). You may benefit from observing or engaging with your intended users (empathise). Create whatever artefacts you think may be helpful to discuss your proposals, including snippets of LC, User Journeys, USM, Wireframes, etc.
-
Select one or two ideas, and generate at least a lean canvas and landing page for both. Then test with other groups in suitable ways and select one idea by the end of the day, for which you hand in an updated lean canvas and landing page to DTU Inside.
Tuesday
09:30: Each group prepare a 45-60 min "mini-workshop" (discord, own group rooms)
12:30: Lunch break
13:00: Mini workshops I (see below; hosted by uneven groups)
14:00: Mini workshops II (see below; hosted by even groups)
15:00: Continued group work (discord)
17:00: Hand-In presentation to DTU Inside
Tuesday assignment:
- In the morning, prepare a mini-workshop using guidelines from the morning lecture.
- In the afternoon: Within the groups ( Gr 01-08 ), ( Gr 9-16 ) and ( Gr 17-25 ) uneven groups are hosting the first workshop, with even groups distributing their members between the hosting groups.
- In practice this would mean (for group 1-8) that groups 1,3,5,7 are hosting the first workshop with groups 2,4,6,8 distributing their members between those groups. E.i. if group 2 consists of 5 members then 1 member goes to 1,3,5,7 with the last member joining group 1. In group 4s case the ‘last’ person joins group 3 and so on.
- The workshops are expected to take place in the hosting groups room, with additional rooms being available for break-out groups (neighbouring empty rooms and the additional breakout rooms available (in the voice channels and breakout room categories)). Every Group x can freely use Breakout 2x-1 and 2x, i.e. Group 01 can use Breakout 01 and 02, Group 02 can use Breakout 03 and Breakout 04, Group 03 can use Breakout 05 and 06, etc. When running a Workshop, we additionally suggest that uneven groups also use the group rooms available to the even group one higher, and vice versa. This means that Group 01 can then additionally use Breakout 03 and 04, and Group 02 can use Breakout 01 and 02 when running workshops
- Then continue working on your ideas and start preparing prototypes for validation.
- Also prepare a presentation for next days "poster" session (some reuse of mondays handin is fine).
Wednesday
08:30: Virtual poster Sessions (zoom ( Gr 01-08 ), ( Gr 09-16 ) and ( Gr 17-25 ); otherwise same format as last week)
10:00: Group work (discord)
12:30: Lunch break
13:00: Group work (discord, TA and lecturer will visit groups)
17:00: Hand-In (LC, LP, USM, WF (don't forget to start adding annotations), Validation) to DTU Inside
-
Continue working on your solution, creating prototypes and validating.
-
Hand in the current set of all artefacts at the end of the day (LC, LP, USM, WF, Validation)
Thursday
08:30: Brief session focused on evaluation and some feedback on reports ( recorded lecture)
12:30: Lunch break
13:00: Group work (discord)
17:00: Hand-In (Presentations for Friday morning in pdf format!)
Assignment:
- Continue working on your solution, creating prototypes and validating.
- Also prepare and hand in a presentation for friday morning (similar format as previous week; only pdf!).
Friday
08:30: Group Presentations (zoom ( Gr 01, 04, 07, 10, 13, 16, 19, 22, 25 ), ( Gr 02, 05, 08, 11, 14, 17, 20, 23 ) and ( Gr 03, 06, 09, 12, 15, 18, 21, 24 ))
10:00: Group work (discord)
17:00: Hand-In of Report (0.5 page/group member) with Lean Canvas, Landing Page, User Story Map and Annotated (Micro-interactions/Back-end) Wireframes and Validation documentation as appendices in one pdf file to CampusNet.
Name your file "GroupNN_title.pdf" (where title is a description of your work). Include also links to your "executable prototypes" and any video lins, but make sure you have all details of the wireframes readable in the PDF file you hand in.
This page will be permanently deleted and cannot be recovered. Are you sure?
|