Errors on rayimport #13
-
|
Hi Thomas, $ rayimport pointcloud.ply ray 0,0,0 --max_intensity 0 --remove_start_pos Next, when I try to run rayextract it seems to run but nothing happens: When I tried repeating the above steps using just I did follow your instructions in an earlier question on the forum, on using ccmake to make DOUBLE_RAYS=ON But it didn't seem to make a difference. Hope you could suggest a solution. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
Hi sdhargay, sorry you are experiencing problems. The warnings for 'rayimport pointcloud.ply 0,0,0' are as expected. It has the sensor origin at 0,0,0 but the cloud many km away, so the rays are too long. I have just fixed the problem of it issuing the warning too much, thanks. The reason rayextract terrain does nothing is that WITH_QHULL is turned off, and rayextract terrain uses QHULL. You can see how to install QHULL in the readme.md. It should have output the error message: "Error: extracting terrain requires QHull, see README instructions for installation" FYI: rayextract terrain can get very slow on large clouds, as it is superlinear with respect to the number of points. If it takes too long then you can raydecimate and rayextract terrain on the smaller cloud. Functions like rayextract trees don't mind if the ground is based on a decimated cloud, you can still use the full cloud for tree extraction. p.s. I will add a warning if you use rayimport ray 0,0,0 (as some functions expect the rays to have a length). thanks |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot Thomas! I enabled WITH_QHULL and followed the instructions given under "Optional build dependencies: For raywrap". Although WITH_QHULL is ON, there are lots of DIRS_NOTFOUND lines as you can see above. I cloned the qhull repo to the same directory-level as my root raycloudtools directory, maybe I need to clone it to the "raycloudtools/build" directory? I also tried to install qhull using: $sudo apt install libqhull-dev, which didn't make a difference. Anyhow I ran $rayextract terrain pointcloud_raycloud.ply" again but there wasn't any output generated although it seemed to do something briefly: I tried rayextract terrain again with the "--gradient 1" option, but it was the same outcome. thanks, sonam |
Beta Was this translation helpful? Give feedback.
-
|
If you followed the instructions including the sudo make install, then the cmake .. should be able to find the library and include paths as long as the install has put it somewhere that is in the standard paths that cmake uses. If that doesn't work then let me know where libqhull.
8000
so.7.3.2 has been installed to, when you ran the sudo make install. |
Beta Was this translation helpful? Give feedback.
-
|
I am running Ubuntu on Windows Sub-system for Linux (WSL). As shown below the libqhull.so.7.3.2 file seems to be present at the expected location: \\wsl.localhost\Ubuntu\usr\local\lib Running echo $LD_LIBRARY_PATH didn't show anything, so I did the "export ..." step you suggested; followed by the "source..." |
Beta Was this translation helpful? Give feedback.
-
|
"Then I ran rayextract terrain again" The Qhull_DIR should be /usr/local/lib/cmake/Qhull if cmake has found it. If cmake can't find the package and it is pointed to in the LD_LIBRARY_PATH then I won't be any help in debugging it, I'm not an expert in cmake's FIND_PACKAGE systems. You may want to look at the last two run commands in raycloudtools/docker/dockerfile and check that is essentially what you did. Other that using docker, you could also try using a 3rd party 2D Delauney triangulation in place of the 'hull.growUpwards(0.01)' function in rayterrain.cpp. Then you wouldn't need Qhull at all. sorry I couldn't be more help. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your help. Yes I agree it seems to be due to cmake's inability to find the qhull shared library, and could be something specific to my system set-up. I will try to figure it out and post the solution here if I find one. In the meantime I have followed your suggestion and thankfully "rayextract terrain" and "rayextract trees" is working as expected in Docker! |
Beta Was this translation helpful? Give feedback.
Hi sdhargay, sorry you are experiencing problems.
The warnings for 'rayimport pointcloud.ply 0,0,0' are as expected. It has the sen 10000 sor origin at 0,0,0 but the cloud many km away, so the rays are too long. I have just fixed the problem of it issuing the warning too much, thanks.
The warnings for 'rayimport pointcloud.ply ray 0,0,0 --max_intensity 0 --remove_start_pos' are correct but not a problem in your case. Your cloud has no time value or colour value and, although the positions are far from the origin, you are removing the start point.
The reason rayextract terrain does nothing is that WITH_QHULL is turned off, and rayextract terrain uses QHULL. You can see how to install QHULL in the…