Cyclops Ride Assist: Real-Time Monitoring System.
Team 9
Aaron Li (lia79)
Amos Cheung (cheuny2)
Amos Yu (yua25)
Brian Le (leb7)
Manny Lemos (lemosm1)
North American cities are shifting from a car-centric design to greener forms of transportation. It is expected that more people will adopt cycling as their primary method of commuting. However, it is difficult for a cyclist to keep track of everything going on around them, especially during busy times.
Cyclops Ride Assist (CRA) will be a user-friendly, all-in-one, and easily mountable system that adds modern automobile safety features on any bicycle that will allow its users to have full detection of their surroundings during their trip from start to finish. This includes rear view detection using LiDAR sensors and an LED display, crash identification through an accelerometer, as well as a front-facing camera to capture and record footage. In the event of an accident, the CRA will automatically record a min of footage, the LiDAR data, as well as an acclerometer log for future review and analysis.
Click the thumbnail to be directed to our promotional video!
| Date | Description |
|---|---|
| September 7, 2022 | Project started |
| September 21, 2022 | Problem Statement and Goals started |
| September 24, 2022 | Development Plan started |
| Oct 3, 2022 | Software Requirements Specification started |
| October 19, 2022 | Hazard Analysis started |
| October 25, 2022 | Verification and Validation Plan started |
| November 14, 2022 | Proof of Concept demo |
| January 17, 2023 | Design Document started |
| February 9, 2023 | Revision 0 demo |
| March 1, 2023 | Verification and Validation Report started |
| April 1, 2023 | Revision 1 demo |
| April 5, 2023 | User Guide started |
| April 5, 2023 | Reflection started |
| April 11, 2023 | Capstone EXPO |
We put all our code in the Code tab. The file structure of the code is as follows.
docs
- Documentation for the project
refs
- Reference material used for the project, including papers
src
- Source code
test
- Test cases
We report and keep track of bugs that need to be fixed and things that need to be done in the Issues tab.
We contribute to the codebase by making pull requests, which are tracked in the Pull requests tab.
We schedule weekly meetings to discuss progress, setbacks, and deadlines. Meeting minutes are kept in the Discussions tab.
We write down things we've learned so that we can refer to it in the future. Documentation is kept in the Wiki tab and is updated frequently.
See our license file.