Skip to content
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

explores for a while, and then exploration is stopped, finding no frontiers #33

Open
altineller opened this issue Mar 20, 2023 · 3 comments

Comments

@altineller
Copy link

Hello,

What parameter must we change to avoid no frontiers found and exploration stopping abruptly? If I move the robot a bit with joystick and then 'ros2 topic pub -1 /explore/resume std_msgs/msg/Bool "{data: True}"' exploration resumes for a little while, and then stops.

I have tried to decrease the min_frontier_size but it did not solve the problem.

Best Regards,
Can

@charlielito
Copy link
Contributor

Could you share a rosbag with an example so we can reproduce it?

@altineller
Copy link
Author

Hello, I tried this almost a year ago, and I will retry in the simulator and get the rosbag data and post it, in a matter of few days.
Best regards.

@altineller
Copy link
Author

Hello,

I did get my test setup using willow garage and my robot, and I recorded a rosbag until it stops. However the rosbag file is 26+GB and compressed it is 8GB, so I did not upload it.

Here is screenshot when it says exploration stopped:

Screenshot from 2024-10-11 23-26-59

There are no blue markers, but there are red markers. I wonder if increasing the lidar max distance could help?

Best Regards,
Can

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants