View Single Post
  #21   Spotlight this post!  
Unread 14-05-2015, 16:02
Sperkowsky's Avatar
Sperkowsky Sperkowsky is offline
Professional Multitasker
AKA: Samuel Perkowsky
FRC #2869 (Regal Eagles)
Team Role: Leadership
 
Join Date: Jan 2015
Rookie Year: 2014
Location: Bethpage, NY
Posts: 1,893
Sperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond repute
Quote:
Originally Posted by KJaget View Post
The code changes aren't that bad. It's only a few changes to switch between GPU and CPU detection code using OpenCV - you just switch from a CascadeClassifier object to a CascadeClassifier_GPU object and most everything else just works. There might be slight differences in the parameters passed to the call to actually do the detect - we just wrapped them in classes which hid those differences from the calling code. Our code builds and runs not only on a Jetson but on x86 Linux, Windows and Cygwin and autodetects whether to use CPU or GPU based on the hardware it finds.

The bigger problem is going to be speed. Based on what we saw running on the Jetson CPUs I'm not sure RPi performance is going to be usable. But I don't have any specific tests to prove it, but I'd be surprised.
I went to the jetson release at makerfaire and talked to the lead designer. The architecture is quite different but speed increase is quite nominal compared to the pi. Thats coming from an intel designer.
Reply With Quote