Lars Glud

Could you try using a tool like this https://docs.microsoft.com/en-us/sysinternals/downloads/coreinfo And post the results. Then we could have a look if the SSE or AVX is supported? And lets keep it...

Thanks. That rules out the instruction set then. Could you try launch it in debug and post the stacktrace when it crash?

Is the intention to limit/simplify the cloudgenerator so you cannot have different distributions on each component (X/Y/Z) - what do we gain from this?

> Hello, Could i work on this one? Yes, please go ahead.

You can add in your CmakeLists something like: target_link_libraries(${PROJECT_NAME} ${PCL_LIBRARIES}) // original from @jasjuang example target_link_libraries(${PROJECT_NAME} pcl_io_ply) // added line that solves the linking error (given the path where the...

In the extract_clusters, they query the tree if it returns sorted or not, like this: ``` // Check if the tree is sorted -- if it is we don't need...

> @larshg Like I mentioned, it's possible, but I didn't know if the effort would be worth it. I've pushed a change in our_cvfh, so you can take a look...

It's not in all cases the tree is fully exposed to the user - sometimes they are private in PCL, ie. in our_cvfh. But I guess the most save approach...

> > ie. in our_cvfh. > > Not really. See https://github.com/PointCloudLibrary/pcl/blob/master/features/include/pcl/features/impl/our_cvfh.hpp#L612 (the false argument implies that the output results are unsorted) Yes, and in this case the user can't change...

> It's 2021 and I'm still getting these warnings when using PCL. Is there really no way of getting rid of these without manually fiddling with PCL's CMake config? Why...