Open nvhungv2k opened 4 months ago
what do the clouds look like for you when you save them as .pcd
? I never hit that specific error... try writing some prints to check that the model tensor input dimensions match those of the cloud vector. as long as the stable_bdarknet.onnx
and the zamboni.bag
or whatever are still the same as in the OG branch, then you should be fine.
I converted pointcloud to *pcd and then viewed it using pcl_ros and pcl_viewer (a component of pcl-tools) respectively. The result is as follow: As I described above, why the program Segmentation::run(..) function, at line 374, in inference.cpp file run decreasingly
use: https://www.cloudcompare.org/ for many reasons ;)
hard to tell from only top-down-view but IMO your screenshot does NOT look like the VLP-16 used in run_sim
inputs:
I can confirm the current 404 status on the .onnx
and .bag
GDrive links. I don't think those files are mine to share, and I trust that the authors will handle it. I used a labeling tool and rangenet++ to make my own model, which you SHOULD do, for whatever LiDAR you will use in field applications, because:
if anyone else reading/trying has already figured out how to make the inference.cpp
&/ trellis.cpp
more sensor-agnostic, let us know! :)
run_sim
input can be any kind of LiDAR sensor (not necessarily is VLP-16), doesn't it? I do not see any snippet in SLOAM indicated that it fixed the kind of LiDAR, if any, please show me
Hello everyone, I built SLOAM with debug option to debug it with GDB:
catkin build -DCMAKE_BUILD_TYPE=Debug
And then, I was running SLOAM on: ubuntu 20.04; ros noetic:roslaunch sloam run_sim.launch
But when LiDAR information came up, it emitted the fatal error: free(): invalid pointer I debugged it with GDB by add launch-prefix="xterm -fa 'Monospace' -fs 14 -e gdb --args" to sloam node in sloam.launch as following: `...