
29-04-2015, 11:37
|
 |
Programmer - LabVIEW, C++, C#, Java
AKA: James Parks
 FRC #0900 (Zebracorns)
Team Role: Alumni
|
|
Join Date: Jan 2009
Rookie Year: 2008
Location: Seattle, WA
Posts: 72
|
|
|
Re: 900's 2015 Robot Code
Quote:
Originally Posted by faust1706
I think I talked to you Saturday about your system. Really cool work. You said something that was really odd to me: you were getting ~15-20 fps. It didn't seem right, and looking at your code I now know why (or have a very good guess).
You are using 2 namespaces that have identical functions, such as erode, dilate, and threshold, cv and cv::gpu.
I'll use the function generateThreshold as a running example. You are passing in Mats, not GpuMat. Meaning when you call cvtColor on ImageIn, it will use the cpu based cvtColor. Same goes for threshold, split, erode and dilate.
There isn't a gpu equivalent of findcontours that I am aware of. There are gpu edge detectors such as sobel and laplacian, however.
Once again, excellent work. This took me a little while to figure out. I'd love to see what the fps is with these changes. Also, if you want to stick to object recognition through training, look into cudNN.
|
Thanks for the feedback. I'll have the students work on this after our break and when they have caught-up on last weeks homework.
|