-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gbplanner_node crash, planner service failed. #31
Comments
Hi @antoan-flox , Did you experience this issue persistently or was this happening only occasionally? Best, |
Hi, @MihirDharmadhikari , I also meet same problem,it occor persistently, How to fix the issue? gbplanner_node: /usr/include/eigen3/Eigen/src/Core/DenseCoeffsBase.h:364: Eigen::DenseCoeffsBase<Derived, 1>::Scalar& Eigen::DenseCoeffsBase<Derived, 1>::operator()(Eigen::Index, Eigen::Index) [with Derived = Eigen::Matrix<double, -1, -1>; Eigen::DenseCoeffsBase<Derived, 1>::Scalar = double; Eigen::Index = long int]: Assertion `row >= 0 && row < rows() && col >= 0 && col < cols()' failed. |
Hi @yhy130531, Thanks for letting us know. I am investigating this issue and will get back to you on this. |
Thank you very much @MihirDharmadhikari. One thing that needs to be explained is that our emulator does not use Gazebo, but only uses Rviz display. The drone control, odometer, and point cloud generation are all ours. I only tested the exploration algorithm. When I start the algorithm , the above error occurred.
|
The planner can work with a custom setup as long as the appropriate topics for the point cloud and odometry are set and a position controller for tracking the output path is available. So I think your setup should be fine. |
The error only occur our simulation,the planner can be work well in your simulation. |
The LiDAR need not have 64 beams. The planner can take any point cloud as input as long as it is in the sensor frame so any other LiDAR simulator should be fine. |
@MihirDharmadhikari I see the same issue when I run your sim example Here is another screenshot when I clicked the "Start Planner" at 1701214505.143857999 and it looks the node crashed afterward. |
I encountered the same issue during simulation. Ultimately, I found that using Perhaps others facing this issue can consider checking the building command. |
Hello,
I built the package on ROS Noetic and experienced a crash, here is the output:
The text was updated successfully, but these errors were encountered: