Professors: John Bartholdi (ISyE), Russ Clark (OIT, CoC)
We will meet Tuesdays 10:10—11:00am in Groseclose 226 (the SCL/Georgia Freight Bureau seminar room in the ISyE building, on the same floor as academic advisement).
Sub-project teams will meet as necessary and at their convenience.
There will be no exams. You will be judged by your professors and peers on your contribution to and engagement with the project (details).
During the first two weeks we will organize into groups to match interests and skills with goals and tasks for this semester.
This is a project course and so fundamentally different from most other courses. We have a client to whom we have made commitments; and progress depends on teamwork. Therefore the pace of the class is set by the needs of the project. Unlike most other classes, you cannot neglect your work and catch up later. The project does not stop during mid-terms.
Failure to deliver on commitments inconveniences the entire team and endangers the success of the project. Lapses that might seem incidental in a lecture class will not be tolerated here. Do not enroll for this class unless you are prepared to work towards a team goal.
The best way to ensure the success of the project and enjoy your work is to find a piece of the project in which you are intensely interested and then take it on. Propose a clear goal and then learn what you need to achieve it. The object is to make a contribution that persists.
We encourage team members to return in following semesters, especially if they have shown potential to grow into positions of technical leadership.
The system has been running successfully for 4 years but we continue to improve it and to extend its capabilities.
Sometimes managers would like to know what happened on a route in the recent past, such as when investigating a report of poor service. Here is a framework to support this.
Any bus system must measure its ridership so that it can configure service to match demand. Ideally we would learn where each passenger boarded and de-boarded the bus, but it would help just to learn how many boarded and de-boarded at each stop.
Build counters: Configure a pair of infrared beams that, when broken, count a passenger and not their direction of travel. Build this with a kit such as Arduino that we will purchase. (Skills: hands-on hardware.)
Build a reporting tool that can provide useful insights into patterns of ridership.
Alternatively, can we make a rough but useful estimate of the number of passengers boarding/de-boarding simply by measuring how long the bus pauses at each stop? We have collected data from a counter but it must be cleaned and associated with bus stops and with stop times. (Skills: light scripting, data analysis.)
The GT person in charge of parking has requested a web app to help him manage parking issues when he is in the field. We will invite him to an early class to explain more.
These plug in to a standard receptacle on a vehicle and read data from various sensors to report location, speed, rpm’s, battery strength, etc. Develop tools to collect and interpret this information. (Skills: C++ programming)
If you have another idea you would like to tackle, make a proposal!
All our work lives on Github. To see it, you must log in with your GT user id and then email me your user id so I can grant access.
Look at the various projects underway and read their Wikis and examine their Issues. See any you want to work on? If not, propose something.
Do not start working without first having submitted a 1-page proposal explaining what you will do, how it will help the client, and what you expect to deliver.
It is expected that you will maintain a lab notebook according to VIP standards. Otherwise your grade will be based on lasting contribution to the project, plus attendance, punctuality, and engagement in class and as reflected on github.
github.gatech.edu, so github knows you exist, and then email me your GT user name so I can grant you access to the iTrans repositories. (Due on 2nd class meeting)