S16: Number 1 - Revision history

Proj user17: /* Grading Criteria */

2016-05-24T03:09:54Z

‎Grading Criteria

Proj user17: /* Hardware Interface */

2016-05-23T16:40:22Z

‎Hardware Interface

Proj user17: /* Issue 3: Low Power CPU Image Processing Speed */

2016-05-23T16:15:10Z

‎Issue 3: Low Power CPU Image Processing Speed

Proj user17: /* Issue 3: Low Power CPU Image Processing Speed */

2016-05-23T16:10:17Z

‎Issue 3: Low Power CPU Image Processing Speed

Proj user17: /* Issue 3: Microcontroller Image Processing Speed */

2016-05-23T16:08:16Z

‎Issue 3: Microcontroller Image Processing Speed

Proj user17: /* Project Video */

2016-05-23T07:02:02Z

‎Project Video

Proj user17: /* Hardware Design */

2016-05-23T04:45:35Z

‎Hardware Design

Proj user17: /* Testing in a Dynamic Environment */

2016-05-23T04:45:11Z

‎Testing in a Dynamic Environment

Proj user17: /* Project Title */

2016-05-23T04:25:25Z

‎Project Title

Proj user17: /* Testing in a Dynamic Environment */

2016-05-23T04:24:13Z

‎Testing in a Dynamic Environment

← Older revision		Revision as of 03:09, 24 May 2016
Line 1:		Line 1:
−	~~=== Grading Criteria ===~~
−	~~<font color="green">~~
−	* 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.
−	~~</font>~~
−
	== Number 1 - Open CV Lane Departure ==		== Number 1 - Open CV Lane Departure ==

@@ Line 145: / Line 145: @@
 === Hardware Interface ===
-The Raspberry Pi 2 was chosen over the SJone Board because the SJone is incapable of doing image processing. The Raspberry Pi 2 runs an image of Linux called Raspbian Jessie. The Raspberry Pi 2 uses the BCM2836 (quad core ARMv7) chip.
+The Raspberry Pi 2 was chosen over the SJone Board because the SJone is incapable of doing image processing. The Raspberry Pi 2 runs an image of Linux called Raspbian Jessie. The Raspberry Pi 2 uses the BCM2836 (quad core ARMv7) chip running at 900 MHz.
 A USB camera is used to provide video/image feed to the Raspberry Pi 2. The camera gives the Raspberry Pi 2 a peripheral of the real world surrounding and allow the Raspberry Pi 2 to do image processing of the input frames.

@@ Line 287: / Line 287: @@
 A fix to this is to have an elapsed time where the lanes disappear. Because it takes time to change lanes, and the lines only disappear for a split second due to the speed of driving, we took made it so if the lines disappear for less than .3 seconds to continue on with the program. Only when the elapsed time is greater than .3 seconds do we deal with changing lanes.
-=== Issue 3: Low Power CPU Image Processing Speed ===
+=== Issue 3: Low Power CPU Image Processing Capability ===
-Most of our development and testing was done on our own personal laptop, which is able to handle a lot of the image processing at a higher Frames/Second. We were worried about how much of a decrease in processing when porting our project over to the Raspberry Pi 2. When testing our code on the Raspberry Pi 2, there was a noticeable decrease in the Frames/Second.
+Most of our development and testing was done on our own personal laptops, which can able to handle a lot of the image processing at a higher Frames/Second. We were worried about how much of a decrease in processing when porting our project over to the Raspberry Pi 2. When testing our code on the Raspberry Pi 2, there was a noticeable decrease in the Frames/Second.
 Although there was a noticeable decrease in Frames/Second, it was still able to provide the same result as testing on our laptop and in a real and dynamic environment. We would recommend others to invest in a better SBC (Single Board Computer) with a GPU for image processing related projects.

@@ Line 291: / Line 291: @@
 Most of our development and testing was done on our own personal laptop, which is able to handle a lot of the image processing at a higher Frames/Second. We were worried about how much of a decrease in processing when porting our project over to the Raspberry Pi 2. When testing our code on the Raspberry Pi 2, there was a noticeable decrease in the Frames/Second.
-Although there was a noticeable decrease in Frames/Second, it was still able to provide the same result as testing on our laptop and in a real and dynamic environment. We would suggest others to invest in a better microcontroller for image processing related projects.
+Although there was a noticeable decrease in Frames/Second, it was still able to provide the same result as testing on our laptop and in a real and dynamic environment. We would recommend others to invest in a better SBC (Single Board Computer) with a GPU for image processing related projects.
 == Conclusion ==

@@ Line 287: / Line 287: @@
 A fix to this is to have an elapsed time where the lanes disappear. Because it takes time to change lanes, and the lines only disappear for a split second due to the speed of driving, we took made it so if the lines disappear for less than .3 seconds to continue on with the program. Only when the elapsed time is greater than .3 seconds do we deal with changing lanes.
-=== Issue 3: Microcontroller Image Processing Speed ===
+=== Issue 3: Low Power CPU Image Processing Speed ===
 Most of our development and testing was done on our own personal laptop, which is able to handle a lot of the image processing at a higher Frames/Second. We were worried about how much of a decrease in processing when porting our project over to the Raspberry Pi 2. When testing our code on the Raspberry Pi 2, there was a noticeable decrease in the Frames/Second.

@@ Line 298: / Line 298: @@
 === Project Video ===
 [https://www.youtube.com/watch?v=6HfkxKG1YLE/ No Lane Change, Straight Line]
 === Project Source Code ===

← Older revision		Revision as of 04:45, 23 May 2016
Line 141:		Line 141:

	=== Hardware Design ===		=== Hardware Design ===
−	~~Discuss your hardware design here. Show detailed schematics, and the interface here.~~
−
	[[File:cmpe244_S16_Number1_hardwareInterfce.jpeg\|700px\|hardwareInterface]]		[[File:cmpe244_S16_Number1_hardwareInterfce.jpeg\|700px\|hardwareInterface]]

@@ Line 264: / Line 264: @@
 === Testing in a Dynamic Environment ===
 The testing was done on a highway. Many adjustments to the HSV had to be done to get it right. There are many factors that could affect the test such as cars passing by and their shadows are over the lanes, making it hard to detect. Much of the test was done on sample videos before we took it out on the road. Every video had to have its HSV adjusted. Since OpenCV processes images frame-by-frame, testing on the road is no different than testing it on sample videos. It just takes a little more work to get the HSV values right because the colors could change at any moment.
 === Issue 1: Noise ===

@@ Line 11: / Line 11: @@
 </font>
-== Project Title ==
+== Number 1 - Open CV Lane Departure ==
 == Abstract ==

← Older revision		Revision as of 04:24, 23 May 2016
Line 264:		Line 264:

	=== Testing in a Dynamic Environment ===		=== Testing in a Dynamic Environment ===
		+
		+	The testing was done on a highway. Many adjustments to the HSV had to be done to get it right. There are many factors that could affect the test such as cars passing by and their shadows are over the lanes, making it hard to detect. Much of the test was done on sample videos before we took it out on the road. Every video had to have its HSV adjusted. Since OpenCV processes images frame-by-frame, testing on the road is no different than testing it on sample videos. It just takes a little more work to get the HSV values right because the colors could change at any moment.

	=== Issue 1: Noise ===		=== Issue 1: Noise ===