Skip to content
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.

Latest commit

 

History

History
52 lines (41 loc) · 3.64 KB

README.md

File metadata and controls

52 lines (41 loc) · 3.64 KB

Car Logic API

A project to help make the roads a smarter and safer place

Description

Our vision: cars, trucks, buses, intersections, even the street itself should eventually be able to communicate and collaborate to improve efficiency and safety without compromising personal security or safety.

The project we are proposing includes developing prototype communication standards, and a proof of concept as to how they would be used. Seeing as we will not be implementing this software in actual cars, we will need to leverage an existing open-source traffic simulation engine to develop and test our work. See the list of open source traffic sims below.

Audience

Traffic engineers and car manufacturers are the main audience for this project. Traffic engineers will be interested in the potential traffic efficiency gains of the project. The project will work best when it is fully integrated into cars, this requires the cooperation of the car manufacturers. They could market the technology as a safety and efficiency feature. Ultimately, as cars become smarter and computers are more tightly integrated with the driving experience, solutions like this will optimize and improve driving for all people who own such a car.

Installation

During our project, we have documented our installation processes for Windows, Mac, and Linux. Click on those links to get to our installation processes, then be sure to head over to the wiki and check out our tutorials.

Documentation

We've spent a significant amount of time documenting what we've learned and how our project is structured over on our wiki. Head over there to read about what we've done, and our struggles.

Proposed Timeline

The goal to achieve by the end of the semester is a working demo of two or more simulated “smart cars” communicating to improve safety and efficiency.

Step 1: design algorithms and specify data requirements Step 2: William: Decide on which traffic sim to use. Greg: Design communication layer Step 3: Produce prototypes of algorithms and communication layer Step 4: Integrate two parts into demo (in sim?)

Week starting day Goals
8/29(first week) Work on Proposal, Goals, Timeline
9/5(Labor Day) Research algorithms / scenarios
9/12 Decide on traffic sim
9/19 Outline communication layer
9/26 First list of required functionality from comm. layer by algos.
10/3 First list of algorithms and scenarios to implement/test
10/10(Columbus Day) Demo communication layer functionality( no algos, just comms)
10/17 Implement a small number of algorithms/scenarios
10/24 Bug test and document both algorithms and comm. layer
10/31 Improve the comm. layer and and scenarios handled
11/7 Above Continued 11/11 Big Group Presentation
11/14 Above Continued
11/21(Thanksgiving break) Take a break.
11/28 Bug testing and clean up
12/5 Improve documentation and more testing.
12/12(Study days and finals) Done?

Contributing

Check out the Contributing document for details about contributing to the project.

Learn More

Head over to the project's Wiki to read the documentation we've written about the project.

License

We have one! Apache 2.0