Difference between revisions of "S16: Number 1"
Proj user17 (talk | contribs) (→Team Members & Responsibilities) |
Proj user17 (talk | contribs) (→Schedule) |
||
| Line 39: | Line 39: | ||
! scope="col"| Status | ! scope="col"| Status | ||
! scope="col"| Completion Date | ! scope="col"| Completion Date | ||
| + | ! scope="col"| Description | ||
|- | |- | ||
! scope="row"| 1 | ! scope="row"| 1 | ||
| Line 45: | Line 46: | ||
| Completed | | Completed | ||
| 3/20/2016 | | 3/20/2016 | ||
| + | | | ||
|- | |- | ||
! scope="row"| 2 | ! scope="row"| 2 | ||
| Line 51: | Line 53: | ||
| Complete | | Complete | ||
| 4/2/2016 | | 4/2/2016 | ||
| + | | | ||
|- | |- | ||
! scope="row"| 3 | ! scope="row"| 3 | ||
| Line 57: | Line 60: | ||
| Complete | | Complete | ||
| 4/2/2016 | | 4/2/2016 | ||
| + | | | ||
|- | |- | ||
! scope="row"| 4 | ! scope="row"| 4 | ||
| Line 63: | Line 67: | ||
| Complete | | Complete | ||
| 4/8/2016 | | 4/8/2016 | ||
| + | | | ||
|- | |- | ||
! scope="row"| 5 | ! scope="row"| 5 | ||
| Line 69: | Line 74: | ||
| Complete | | Complete | ||
| 4/8/2016 | | 4/8/2016 | ||
| + | | | ||
|- | |- | ||
! scope="row"| 6 | ! scope="row"| 6 | ||
| Line 75: | Line 81: | ||
| Incomplete | | Incomplete | ||
| | | | ||
| + | | Included blurring, edge detection, and Hough transform. | ||
| + | Problem 1: A lot of noise being picked up by Hough transform. | ||
| + | Status 1: Binarizing image seems to help decrease a lot of the noise. Gets rid of a lot of unnecessary objects | ||
| + | Problem 2: Gaps in lanes do not complete Hough transform. | ||
| + | Status 2: Currently working on Hough transform filters and Custom Region of Interest. Will possibly use birds-eye view. | ||
|- | |- | ||
! scope="row"| 7 | ! scope="row"| 7 | ||
| Line 81: | Line 92: | ||
| Incomplete | | Incomplete | ||
| | | | ||
| + | | | ||
|- | |- | ||
! scope="row"| 8 | ! scope="row"| 8 | ||
| Line 87: | Line 99: | ||
| Incomplete | | Incomplete | ||
| | | | ||
| + | | | ||
|- | |- | ||
! scope="row"| 9 | ! scope="row"| 9 | ||
| Line 92: | Line 105: | ||
| Testing in Lab and attach feedback system (sound for warning) | | Testing in Lab and attach feedback system (sound for warning) | ||
| Incomplete | | Incomplete | ||
| + | | | ||
| | | | ||
|- | |- | ||
| Line 98: | Line 112: | ||
| Testing on the road | | Testing on the road | ||
| Incomplete | | Incomplete | ||
| + | | | ||
| | | | ||
|} | |} | ||
Revision as of 03:08, 2 May 2016
Contents
Grading Criteria
- How well is Software & Hardware Design described?
- How well can this report be used to reproduce this project?
- Code Quality
- Overall Report Quality:
- Software Block Diagrams
- Hardware Block Diagrams
- Schematic Quality
- Quality of technical challenges and solutions adopted.
Project Title
Abstract
This section should be a couple lines to describe what your project does.
Objectives & Introduction
Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.
Team Members & Responsibilities
- YuYu Chen
- OpenCV Programmer
- Kenneth Chiu
- Programmer/Video supplier
- Thinh Lu
- OpenCV Programmer
- Phillip Tran
- OpenCV Programmer
Schedule
Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.
| Week# | Date | Task | Status | Completion Date | Description |
|---|---|---|---|---|---|
| 1 | 3/21/2016 | Get individual Raspberry Pi 2 for prototyping & research OpenCV on microcontroller | Completed | 3/20/2016 | |
| 2 | 3/27/2016 | Continue Research and learning OpenCV. Familiarize ourselves with API. Know the terminologies. | Complete | 4/2/2016 | |
| 3 | 4/2/2016 | Complete various tutorials to get a better feel for OpenCV. Discuss various techniques to be used. | Complete | 4/2/2016 | |
| 4 | 4/4/2016 | Research on lane detection algorithms. IE. Hough Lines, Canny Edge Detection, etc. Start writing small elements of each algorithm. | Complete | 4/8/2016 | |
| 5 | 4/14/2016 | Run sample codes on a still, non-moving picture. | Complete | 4/8/2016 | |
| 6 | 4/20/2016 | Write our own algorithm, and test it. Camera input, Proper Hough Line generation. | Incomplete | Included blurring, edge detection, and Hough transform.
Problem 1: A lot of noise being picked up by Hough transform. Status 1: Binarizing image seems to help decrease a lot of the noise. Gets rid of a lot of unnecessary objects Problem 2: Gaps in lanes do not complete Hough transform. Status 2: Currently working on Hough transform filters and Custom Region of Interest. Will possibly use birds-eye view. | |
| 7 | 4/22/2016 | Modify the code for our own project objective. Include a "lane collider" to see when we cross a lane. | Incomplete | ||
| 8 | 5/2/2016 | Implement the code with Raspberry Pi 2 | Incomplete | ||
| 9 | 5/8/2016 | Testing in Lab and attach feedback system (sound for warning) | Incomplete | ||
| 10 | 5/14/2016 | Testing on the road | Incomplete |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
Design & Implementation
The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.
Hardware Design
Discuss your hardware design here. Show detailed schematics, and the interface here.
Hardware Interface
In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.
Software Design
Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.
Implementation
This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.
Testing & Technical Challenges
Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.
Include sub-sections that list out a problem and solution, such as:
Issue 1: Noise
There are Large amounts of noise when generating Hough lines. This is because there are lines in each picture. Standard Hough lines do not work because you cannot set the minimum and maximum lengths of lines. Probabilistic Hough Lines are the best bet for this task. Even with Probabilistic Hough Lines, there is still quite a bit of noise.
Resolution still in the works. Possible fixes include increasing Gaussian blur to smooth out unnecessary edges, and applying a region of interest.
Conclusion
Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?
Project Video
Upload a video of your project and post the link here.
Project Source Code
References
Acknowledgement
Any acknowledgement that you may wish to provide can be included here.
References Used
List any references used in project.
Appendix
You can list the references you used.
