Skip to content

Project Overview

Jump to bottom
James Dunn edited this page Sep 7, 2017 · 3 revisions

level5-engineers

level5-engineers

CarND Capstone Project: System Integration
It’s not about the pieces but how they work together.

Team slack handles

  • James William Dunn: @jwdunn1
  • Aman Agarwal: @aman
  • Oleg Leizerov: @leyzerov
  • Yousof Ebneddin: @yousof_ebneddin
  • Rajesh Bhatia: @rajesh_bh

Ground rules

  1. Communication: Team-members are active and courteous on two modes:
  • Slack for team-member coordination (information, updates, questions, asynchronous discussions)
  • Github repository for code coordination (pull-requests, code review)

  1. Respect: Be aware of team-members' daily wake/sleep cycles. Tip: set up four clocks (UTC-7, UTC, UTC+2, UTC+5:30) here: https://www.timeanddate.com/worldclock/personal.html

  2. Expected duties: Team-members work together professionally, contribute technical expertise, learn, and have fun. We all want to have a positive experience. We are on this team because of our dedication to the SDC-ND program and we all want to succeed.

  3. Non-activity: Results in rectification beginning with an email inquiry. A lack of communication for one week will result in team-member replacement. Please inform the team lead in the event of an emergency.


Goal

Drive Carla successfully in the simulator and around the test track. We will develop, test, integrate, and deliver ROS nodes to implement the core functionality of an autonomous vehicle system based on the provided framework in the repository.


Milestones

  • waypoint updater preliminary node
  • twist controller class
  • drive-by-wire controller node
  • traffic light detection node
  • waypoint updater enhanced node
  • integration complete
  • deliver by Oct 23rd

Preliminary schedule

preliminary schedule


Action items

  1. Confirm in your classroom the Oct 23rd due date. We all need to be on the same deadline.
  2. Visit our Slack channel frequently.
  3. Create a branch from our team repository.
  4. Familiarize yourself with git operations, ROS nodes, and the Carla system architecture presented in class.
  5. Be certain your email alias matches that in Udacity. The project README will contain the names and Udacity account emails of all team members.
  6. Consider the following approaches for task assignment:
  • silo: team member volunteers to develop one module and review others
  • collaborative: everyone develops modules together sequentially
  • competition: each writes all modules, best is selected by review

Time overlap matrix

The following chart lists the team members' time zones with respect to UTC.

preliminary schedule


Identity

The team logo integrates multiple concepts: advancing autonomy to level 5, a pavement directional arrow, engineering tools, the five-member team, and the tag line: "It’s not about the pieces but how they work together." The engineer's square and protractor combine to create an abstract numeral five. Scalable to any size (minimum 16x16 pixels). Design by Alyce N. Hoggan, MDes.


Posted by James: 20170906.2200

Clone this wiki locally