View Single Post
  #10   Spotlight this post!  
Unread 01-21-2016, 04:26 PM
Tom Bottiglieri Tom Bottiglieri is offline
Registered User
FRC #0254 (The Cheesy Poofs)
Team Role: Engineer
 
Join Date: Jan 2004
Rookie Year: 2003
Location: San Francisco, CA
Posts: 3,182
Tom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond repute
Re: GRIP on an NVIDIA Jetson TK1

Quote:
Originally Posted by marshall View Post
I'm not saying you are wrong but I'm not sure where you are getting that the GPU functions are "under the hood" with OpenCV4Tegra. It's not nearly as automatic as you are making it seem from our experience working with it and moving images from the CPU to GPU memory is a chore, though definitely doable.*

Check out this webcast/video about porting OpenCV code over to the Jetson: http://devblogs.nvidia.com/parallelf...etson-tk1-gpu/

As far as I know, OpenCV4Tegra is a pre-compiled and ARM/Tegra/CUDA optimized version of the OpenCV library because building it yourself is a pain though definitely doable.

Also, OpenCV4Tegra is being augmented/replaced with VisionWorks now on the TX1.

*Please note that I could be wrong because I haven't dug into Nvidia's code... just our code that is somewhat based on it/uses it.
I misread the docs, you are totally right. Still, it seems using the tegra version gets you a few cpu based optimizations. And you can use the GPU module out of the box, which seems nice.