Overall Process
General Brainstorming in a Lab early in the semester. (see
Final Project Guidelines
)
Each student writes up one or two project ideas to submit as homework
Students can work on these original projects or join a “Campus Rover” subproject. There are tradeoffs.
Teams are proposed by a group of 1, 2 or 3 students. Pito has to approve
In Class “Project Bazaar” where we talk and vote and choose projects
Teams commit to a project
Pursuing the project (either alone or with a teammate)
Weekly project updates (scrum style)
Preparing for the “Autonomous Robotics Final Project Showcase”
Writing a Project Report and adding it to the Lab Notebook (see below)
Demoing your project and
Posters
on Showcase Day
What to submit
Link to your clean GitHub repo, in the campusrover github organization. While we will start looking at this for grading, you can still make corrections and adjustments until demo day.
Each team member contributes one FAQ item to the Labnotebook
A Project Report in the Labnotebook
A
Posters
describing the project to people at the showdcase
Each teammate separately (and not in the lab notebook), is asked to provide a reflection, including specifically what their contribution was to the project was
Autonomous Robotics Final Project Showcase
You (and your teammates) prepare to demonstrate your work in the best possible light
You also prepare a
Posters
explaining your project
The teaching staff plus at least one outside robotics expert will visit and hear your presentation and ask you questions
Grading
The project as a whole is graded. All aspects of the work and deliverables are considered.
In the case of team, we grade the work of the team as a whole
Each team member however will be assigned a grade reflecting their level of participation and contribution to the group work.
In other words, you might not get the full project grade if you didn’t participate fully in the project.
This grade will count for 40% of your final grade.
Details
Github Repo
The code should be clean and well structured, and organized as a working ROS package.
It should not have any random left over files so that you would be proud to put the link on your resume
It should include the pdf of your
Posters
It should include a readme.md including links to the labnotebook Project Report (check
How to write a quality readme
for ideas)
Final Project report
Report should be around 10 pages
We pay attention to appearance, quality of writing, “fit and finish”.
You will add it to the appropriate section of the Lab Notebook.
Here are instructions on how to do that:
Lab Notebook Final Reports Section
Rough outline of report
Introduction
Problem statement, including original objectives
Relevant literature
What was created (
biggest section
)
Technical descriptions, illustrations
Discussion of interesting algorithms, modules, techniques
Guide on how to use the code written
Clear description and tables of source files, nodes, messages, actions and so on
Story of the project.
How it unfolded, how the team worked together
problems that were solved, pivots that had to be taken
Your own assessment
Presenting and Explaining Your Project
Show case what you’ve learned and what you built in the best possible light
Come up with a cool and interesting demo
Make sure that you reserve the robot you need for your demo
If you want to share a demo with another team that’s fine
But the assessment will be individual
Posters
Make a classic “Poster” describing your project
Format: pdf size: 27x36 inches (landscape)
See, e.g.
Poster Basics
,
Duke guide
,
google
Audience is someone familiar with robotics
Explain your objective and your project
Team members, dates
Make it look pretty! Don’t have too many words. Have some çdiagrams or pictures
Contribution to Lab Notebook
Each student should make one Notebook contributions.
Think about a how-to, tutorial, explanation, concept, that you had to figure out yourselves that was difficult to track down and write it up for the next generation of students
Here are some examples:
Communicating with Rosserial
,
AWS RoboMaker
,
Alexa Voice Integration