clattenb's profile - activity

Excellent! Thank you for posting a reply!

Before I run into issues way down the road I want to ask my question on here.

When storing descriptors by using the GPU enabled functions surf() or orb() are the descriptors stored per row of a GpuMat? I have seen the documentation state that the CPU based versions of the functions store descriptors per row of a Mat datatype and I want to be sure that the GPU version does the same. I'm not sure because of the use of the "rowrange" function to set a range of rows to pass to the kernels to calculate the descriptors. It makes me think that maybe the descriptors are across several rows but I can't yet tell by just looking at the code. I figured I may get a quicker answer on here.

I just want to store each descriptor individually from the GPU feature detectors to put into a float array in my own data structures.

Any Feedback is appreciated.

Fixed the issue, here's a post for those that run into this in the future.

Use OpenCV static libraries. Also don't forget to use the compiled Opencv liblibtiff, liblibpng, etc. in the "install" directory in your build location.

Hello,

I quickly asked this question in a comment but I think it is better served as a topic.

I have a simple application that opens up an opengl window, nothing else, and it works fine on the CARMA board with opengl libraries and cuda libraries used when compiled. The moment I add opencv libraries to the project and try to run it on the CARMA board I get a std::bad_alloc error at runtime (doesn't even get to main()).It's the same opengl window code that has worked before. I think one or a couple libraries are allocating too much space for storage for the CARMA devboard? Not my area of expertise so it's just speculation at this point. Does any one have any suggestions on how to fix this? It may just be an compile flag that's missing or that is wrong when I compile Opencv.

Thanks in advance for the help.

EDIT: After more trial and error tonight I believe that it's a lack of physical memory on CARMA. Does anyone know what the physical memory requirement is for OpenCV?

Thanks Vladislav. I found the scripts in the platform folder and got it to compile nicely but I have another problem. I have a simple application that opens up an opengl window and it works fine on the CARMA board. The moment I add opencv libraries to the project and try to run it I get a std::bad_alloc error at runtime. I didn't add any code or even any OpenCV headers yet. I think one or a couple libraries are allocating too much space for storage for the CARMA devboard? Not my area of expertise so it's just speculation at this point. Any suggestions on a fix? Any help would be appreciated.

Hello,

So I have built OpenCV for the CARMA toolkit using the instructions from :

http://code.opencv.org/projects/opencv/wiki/CARMA_platform_compilation_and_testing

I went and rebuilt and changed up some items that weren't OpenCV related in my development and now 2.4.4 is out. Now that there isn't a CARMA toolchain like before what are the steps for compiling OpenCV for the CARMA devkit?

Thanks