Assignments

WEEK 11: FINAL VIDEO & DEMONSTRATION (20 points)

Due: JUN 9, 5pm

1. VIDEO PRESENTATION: You final assignment involves creating a video that presents your project, based on the script you prepared in Week #9. Your video should be three minutes or shorter. Your video should both introduce and "sell" your design. The following example videos might inspire you:

Videos on Kickstarter (e.g. apps, software, robots, web, wearables, or any other) or Indiegogo (e.g. technology, search results for "apps")
Videos created for projects in previous robotics capstones: 2016, 2017, 2018, 2019
Videos created in HCI courses, e.g. iDrinkSafe, TasteBud, Aqueous, Neighborly, Broccoli for All

Your video script (Week #9 blog) should include a plan for narration and accompanying visuals (footage or images). Your script should be in the form of a three column table.

The first should include a section number and a short section title (e.g. "introduction", "demonstration of task 1" or "testimonial from test user").
The second should be the a description of visual elements that will be shown in the video (e.g. "talking head of team member A", "video of robot manipulating object", "screen recording of someone using the UI"). Include sufficient details such that someone who reads your description could go and shoot that video for you.
The last should be the narration text that will be read voice-over on the video, if the video does not already include relevant audio. This includes what will be said in "talking head" shots.

To allow for creative freedom and avoid obtaining many cookie-cutter videos, we are not constraining the sections in your video. But please make sure that your video follows these guidelines:

Your video should clearly describe and motivate the problem. Get the viewers to care about the problem.
Your video should clearly describe your solution and convince the viewer that it addresses the problem.
- It should be clear what your design is useful for to someone who is hearing about the project for the first time.
- Your video should demonstrate the use of your robot. This can be done by walking through different tasks that your robot supports. Be sure to set context for the use and demonstrate the outcome (just like in your storyboards).
Your video should feature positive feedback from potential users regarding your design (quotes from your interviews or new recordings of people saying what they like about your design or describing contexts in which they would use your design if it were real).
Your video should introduce you, the team.

You will receive feedback about your scripts shortly after submitting them. Afterwards you will have a week to shoot and edit your videos. Try to incorporate any feedback you received about your script.

The evaluation of this assignment will be done by a panel of judges and it has two components:

Evaluation of the video: In addition they will assess the quality of your video. Besides covering important content, it is important for your video to have appeal.
Evaluation of the project: The judges will assess the importance and quality of your project. Note that this assessment depends on the judge's ability to understand your project based on the video.

The rating sheet that the judges will use is available here. To avoid file format related challenges and allow judges to view videos remotely, we request that you upload your video to YouTube (you can make it Unlisted if desired) and submit a link to the video on Canvas.

2. DEMONSTRATION: In addition to the video, you will demonstrate your project live to the TA and/or instructor during the finals week over video. We expect to see the core functionality shown in the video to work similarly on the robot and will ask to see variations of the demonstration.

WEEK 10: TEAM ASSIGNMENT #6 (5 points)

Due: JUN 8, 5:00pm

We are in the home stretch.

Post #1: Report on your progress in completing your project implementation. This does not need to be as detailed as in previous weeks as we will see the final result in your video; a bullet list of what you got done is sufficient.
Post #2: We would like you to reflect on your teamwork and write a brief blog post about your reflection. In particular, talk about which strategies from Team Assignment #1 did you actually adopt as a team, what other strategies did you adopt along the way, which ones worked well, and which did not.
Post #3: Perform a mini evaluation of your integrated system. The main goal of your evaluation is to demonstrate that your system works in more than one setup. You could vary a number of things about the setup: types of objects, initial configurations of objects, environment (e.g. different home), users, among others. Pick at least one dimension to vary, and at least two different instances of each dimension. Think of at least one quantitative measure to assess the performance of your system (e.g., % of successful trials out of N, time to complete task). Also think about qualitative observations you can make to potentially explain differences in performance (e.g., "success was lower in second home because the robot seemed to have many false positive detections, possibly due to more challenging background color"). Perform your evaluation and write a brief post describing what you did and reporting the performance.

Submission: Submit links to your posts on Canvas. Only one team member needs to submit.

WEEK 10: INDIVIDUAL ASSIGNMENT #5 (1 points)

Due: JUN 7, 5:00pm

A couple of things you need to do on your own this week.

Peer evaluations: It is time to fill out your peer evaluations; see instructions on Canvas.
Course evaluation: The robotics capstone is a continually changing course, and the Spring 2020 offering is the first (possibly not the last) attempt at doing it remotely; we would really like to hear from you any information that can help make future offerings better. Hence we strongly encourage you to fill out the official course evaluation: https://uw.iasystem.org/survey/226209 You will recognize the standard questions, but we would especially like to hear your reflections about (a) what was most fun, (b) what was most useful, (c) what was not so useful, (d) what would have been useful but was missing.

WEEK 9: TEAM ASSIGNMENT #5 (4 points)

Due: JUN 1, 5:00pm

Crunch time continues this week.

Post #1: Report on your progress in implementing the capabilities for your project. Please provide concrete evidence for your progress, including visuals (photos, videos) when possible.
Post #2: Write a draft script for your final presentation video. See the final video assignment posted above for more details and example videos.

Submission: Submit links to your posts on Canvas. Only one team member needs to submit.

WEEK 8: TEAM ASSIGNMENT #4 (2 points)

Due: MAY 25, 5:00pm

This week, all hands on implementation.

Post #1: Report on your progress in implementing the capabilities described in last week's assignment. Use visuals (photos, videos) when possible. [Sample progress reports: Nectar, Auxie, Bow-tie-bot]

Submission: Submit a link to your post on Canvas. Only one team member needs to submit.

WEEK 7: TEAM ASSIGNMENT #3 (6 points)

Due: MAY 18, 5:00pm

This week you will detail your implementation plan and start making progress towards implementation.

Post #1: After refining the technical capabilities list from last week, create a system diagram showing different components of the software you will create for Cozmo. Examples of components are "detect and localize pill bottle" (perception), "move to pill bottle" (navigation), or "pick up pill bottle" (manipulation). Indicate the information passed between different components, e.g. "pill bottle pose (x, y, theta)" or "navigation successful". Indicate which components are part of your minimum viable product (needed to produce basic capabilities, high priority) and which ones provide additional features (secondary priority). Assign each team member to lead the implementation of a component. In addition indicate which team members are working on hardware aspects of the project implementation. [Sample system diagrams: Nectar, Auxie, Bow-tie-bot]
Post #2: Create an initial visual draft of a Finite State Machine or flow diagram that describes the behavior of your robot. Focus on a possibly simplified scenario (possibly illustrated in your storyboard from last week) that you would like to be able to demonstrate at the end of the quarter.
Post #3: Report on your progress in implementing the capabilities described in Post #1. Use visuals (photos, videos) when possible. [Sample progress reports: Nectar, Auxie, Bow-tie-bot]

Submission: Submit three links, one for each of your posts described above on Canvas. Only one team member needs to submit.

WEEK 6: TEAM ASSIGNMENT #2 (8 points)

Due: MAY 11, 5:00pm

Based on the feedback you get about your project ideas from team assignment #1, you will select one project idea and start refining, detailing, and possibly implementing it.

Choose a company/team name and a product name (they could be the same) and create a logo. Update your team blog with this information. You can change these later, but pick something to start with.
Post #1: Watch this video about creating a one-page business model ("lean canvas") for product ideas. Create a lean canvas for your selected project as described in the video. You can use the tool mentioned in the video or just make a slide or drawing with text. This exercise will ensure you are thinking through different aspects of the problem you would like to address in your project and you will be able to "sell" it later. Post an image of your lean canvas on your team blog with a brief description making sure it is readable.
Post #2: Create a storyboard describing the problem and solution for your project. Also create a sketch of your robot and its environment, including any modifications made to the robot and the environment and special objects in the environment. Someone who looks at these two visuals for the first time should understand what problem you are solving and how you are solving it; it should also convince them that your solution is feasible. Post the two visuals on your team blog with a brief description.
Post #3: Write a comprehensive list of all the technical capabilities you will need to implement for your project. You can group the basic capabilities in the same way we covered robot capabilities in the earlier labs: navigation, perception, and manipulation. You might also need higher level reasoning, planning, and interaction capabilities. For each capability you list, indicate what prior code from the labs you might be able to use, or what Cozmo SDK or external library implementation seem promising. Also indicate if you plan to use any external devices, such as a camera for environment perception or a smartphone for user interaction.

Submission: Submit three links, one for each of your posts described above on Canvas. Only one team member needs to submit.

WEEK 5: TEAM ASSIGNMENT #1 (6 points)

Due: MAY 5 (TUE), 5:00pm

Once you have finalized your team, create a private team Github Repository and add all team members, as well as Maya and Vinitha, to it. You can use the Wiki page of your repo or create a Github webpage to post write-up assignments and videos to document your project for the rest of the quarter. For this week, we would like to see two new posts:

Post #1: Assign team roles to everyone in your project team, considering common potential roles in this class. Write a blog post that describes everyone's roles and concrete responsibilities. Consider weekly responsibilities as well as quarter-term project responsibilities. In addition, write a paragraph about strategies you will follow to ensure everyone in the team acquires the knowledge and skills they hope to get out of the class.
Post #2: Pick top two project ideas you would like to pursue this quarter and write a short description for each idea. Your descriptions should:
- State the problem that you will address with the supporting evidence (stats or personal experience) and identify the target user group. Provide pictures and quotes if available. The problem statement should be completely independent of the proposed solution.
- Describe the proposed Cozmo-based solution. Answer the question of why a robot is a good solution for the problem, as opposed to solutions using other technologies. Present an argument for the tractability and feasibility of the solution.

Submission: Submit two links, one for each of your posts described above on Canvas. This is set up as a team assignment on Canvas, so only one team member needs to submit.

WEEK 5: ASSIGNMENT #4 (8 points)

Due: MAY 7 (THU), 5:00pm

Labs: Complete Lab 8 on the Course GitHub wiki.

Submission: Obtain a video of the robot (1) picking up and releasing an object using two different strategies as described in the labs, and (2) moving an object from a start pose to two different target poses by pushing it. Upload to Youtube or Vimeo and submit a link to the video and your code for Lab 8 on Canvas.

WEEK 4: ASSIGNMENT #3 (4 points)

Due: APR 27, 5:00pm

Labs: Complete Lab 7 on the Course GitHub wiki.

Submission: Obtain a video of the robot moving to a cube and executing a cube action in two different initial cube poses. Upload to Youtube or Vimeo and submit a link to the video and your code for Lab 7 (pose_transform.py) on Canvas.

WEEK 3: ASSIGNMENT #2 (8 points)

Due: ~~APR 20~~ APR 23, 5:00pm

Labs: Complete Labs 4-6 on the Course GitHub wiki.

Submission: Obtain a video of the two robot behaviors described in Lab 6. Combine the two videos into one and upload to Youtube or Vimeo. Submit a link to the video and your code for Lab 4 (find_ball.py), Lab 5 (imgclassification.py), and Lab 6 (goto_ball.py, react_cards.py) on Canvas.

WEEK 2: ASSIGNMENT #1 (8 points)

Due: APR 14 (TUE), 5:00pm

Labs: Complete Labs 1-3 on the Course GitHub wiki.

Submission: Obtain a video of the four different Braitenberg vehicle behaviors from Lab 3. You might want to use a flash light to control brightness while demonstrating the behaviors. Combine the four videos into one and upload to Youtube or Vimeo (you can make it unlisted). Submit a link to the video on Canvas, together with a short description of each of the vehicle behaviors in the order they appear in the video.

WEEK 1 NO ASSIGNMENT

Google Sites

Report abuse