Ask Your Question

Ammy's profile - activity

2020-01-14 04:02:15 -0500 received badge  Popular Question (source)
2019-06-22 20:52:19 -0500 received badge  Popular Question (source)
2016-07-19 13:27:01 -0500 received badge  Student (source)
2016-07-01 08:56:18 -0500 received badge  Scholar (source)
2016-07-01 08:56:14 -0500 received badge  Supporter (source)
2016-07-01 08:55:20 -0500 commented answer Converting GpuMat 32FC1 > 8UC1

I've now solved the problem. One has to use an additional matrix to copy the converted matrix into. so it works as follows:

cv::cuda::GpuMat gm_temp;
gm_mask.convertTo(gm_temp, CV_8UC1, 255.0/1.0, 0);
gm_mask = gm_temp;
2016-07-01 05:22:34 -0500 commented answer Converting GpuMat 32FC1 > 8UC1

as it is defined in

cuda::threshold(gm_depth, gm_mask, sts.d_treshold, 1.0, THRESH_BINARY)

i have got only "1" and "0" entrys in gm_mask, so that shouldn't be the problem i think.

2016-07-01 01:40:37 -0500 received badge  Editor (source)
2016-07-01 01:39:07 -0500 asked a question Converting GpuMat 32FC1 > 8UC1

Hello together,

i've got a problem with converting an GpuMat (the same problem i have, when i'm doing it with a cv::Mat). I want to delete some areas from a picture (gm_temp) where the threshold of the depth, stored in another matrix (gm_depth), is under a certain value (sts.d_treshold). Because cuda::treshold converts the gm_mask to 32FC1, i need to convert it back to 8UC1 to be able to multiply it with gm_temp. But after the conversion gm_mask only have zeros in its matrix, although it had the proper values before.

          cv::cuda::GpuMat gm_mask (gm_temp.rows, gm_temp.cols, CV_8UC1, 0.0);
          gm_depth.upload(m_depth);
          cuda::resize(gm_depth, gm_depth, Size(gm_temp.cols, gm_temp.rows));
          cuda::threshold(gm_depth, gm_mask, sts.d_treshold, 1.0, THRESH_BINARY); // Until here it's working fine.
          gm_mask.convertTo(gm_mask, CV_8UC1, 255.0/1.0, 0);
          cuda::multiply(gm_temp, gm_mask, gm_temp);
2016-06-17 03:25:52 -0500 commented question Compiling OpenCV 3.1doesn't put header files into include directory

recently CUDA 8 has been released with VS2015 support, so it should actually work now

2016-06-15 08:30:42 -0500 commented question Compiling OpenCV 3.1doesn't put header files into include directory

The most cuda libs have been compiled but not all....

Here's the cmake output: https://syncandshare.lrz.de/dl/fiFmXK...

2016-06-15 07:57:56 -0500 commented question Compiling OpenCV 3.1doesn't put header files into include directory

for sad, i can't post the cmake output here, because i registered just today :-/

2016-06-15 07:05:14 -0500 asked a question Compiling OpenCV 3.1doesn't put header files into include directory

Hello together,

I recently tried to compile OpenCV 3.1 with CUDA8, OpenNI2, Python2.7 on Windows 8.1 with Visual Studio 2015. I built the project "ALL_BUILD", but still e. g. the header files haven't been put into the include directory. Do i have to build another project within the opencv solution?

Moreover some cuda librarys (e.g. cuda_objdetect) haven't been built and i don't know why.

You can find the cmakelist.txt here: https://syncandshare.lrz.de/dl/fiTXbE... And the log of the compiler here: https://syncandshare.lrz.de/dl/fiRvTu...

Many Thanks Armin