CIS 693, EEC 693/793
Autonomous Intelligent Robotics -- Spring 2018



Final projects


Important dates (due 11:59 AM on respective days)

  • Proposal draft (at least 1 page) due: Feb 21 (Wed) Feb 22 (Thu) .
    • Students will talk to each other and form teams by this time.
    • One team member sends it as an attachment in PDF (less than 2M) to the instructor's Gmail address (CC'ing all other team members), with subject line "class project: proposal draft".
    • No format requirement for the proposal draft.

  • Written proposal (3 pages or more, 10% of the total grade): March 9 (Fri).
    • One team member sends it as an attachment in PDF (less than 2M) to the instructor's Gmail address (CC'ing all other team members), with subject line "class project: proposal".
    • LaTex template: link is required.

  • Proposal presentation (15 minutes each team): March 7 (Wed) and 9 (Fri).
    • What is the problem you are trying to solve?
    • Why should we care about this problem?
    • Are there existing methods aiming at the problem? References are needed.
    • What is your approach? Be as specific (and concise) as possible. I assume you are not developing your solution from scratch. Make it clear what is from the others (as a result, I can see what is from you).
    • What are you expecting by the end of this course?

  • Written final report (8 pages or more, 30% of the total grade): May 4 (Fri).
    • One team member sends it as an attachment in PDF (less than 2M) to the instructor's Gmail address (CC'ing all other team members), with subject line "class project: final report"
    • LaTex template: link is required.
    • What to be included in the final report?
      • An one-two paragraph abstract that helps people understand your work, and decide if he/she should continue reading your paper.
      • What is the problem that you are trying to solve? Why is it an important problem? Is this a good time to work on the problem? For instance, focusing on an Android APP 10 years ago might not be a good idea.
      • It's unlikely that you are building everything from scratch. One should discuss the ideas, tools, algorithms, and conclusions from the literature. Among them, alternative solutions should be clearly identified, and discussed.
      • The above sections may look similar to those that were included in your proposal. However, I am sure you want to make some changes, or add new materials here and there.
      • Now, we are ready to hear about what you actually did. There is no gold standard on how to create the technical sections. Generally, people may appreciate diagrams, pictures, figures, tables, etc, in comparison to text-only representation. The overall goal here is to help a non-expert understand how your system works.
      • OK. You built a fantastic system that completely meets your expectation. Could you be specific on what we are expecting, and how your system succeeds there?
      • How is the work distributed among the team members?
      • Have a conclusion that serves as the take-home message. Any lessons, technical or non-technical, learned from this project?
      • Any one(s) whose name(s) are not in the author list helped in this project? Their names should be included in the acknowledgment section.
      • IMPORTANT: References should be professionally included. Generally, we should only include peer-reviewed research papers there (such as the readings in this course), which means one should not list web links or media reports.

  • Final presentation: 15+5 minutes each team. May 2 (Wed) and May 4 (Fri). I suggest to use Google Slides to create and host your slides.

    • Schedule (May 4):

      12:15 - 12:26 Danye Luo, Henglong Ma, Nuo Zhou:
      Control TurtleBot Through a Webpage

      12:26 - 12:37 Brandon Marlowe, Kaylee Yuhas:
      Multi-robot Autonomous Soccer using OpenCV and Hough Transform Gradients

      12:37 - 12:48 Humberto De las Casas, Holly Warner:
      Rabbit: A Robot for Child-Robot Interaction

      12:48 - 12:59 Xiaodan Liu, Zhan Wang, Suhua Wei:
      Augmented Reality Application on Robot trajectory with ROS system

      12:59 - 13:10 Mahmoud Hamandi, Labhesh Popli:
      Robot Companion: Escort Me Home

      13:10 - 13:21 Saeid Amiri, Azin Shamshirgaran:
      DoorBot, a Platform for Interacting with Humans and Monitoring Crowd


Teams

  1. Team: Danye Luo, Henglong Ma, Nuo Zhou
    Final Report [PDF]

  2. Team: Kaylee Yuhas, Brandon Marlowe
    Final Report [PDF]

  3. Team: Humberto De las Casas, Holly Warner
    Final Report [PDF]

  4. Team: Suhua Wei, Zhan Wang, Xiaodan Liu
    Final Report [PDF]

  5. Team: Mahmoud Hamandi, Labhesh Popli
    Final Report [PDF]

  6. Team: Saeid Amiri, Azin Shamshirgaran
    Final Report [PDF]