-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Behavior Tree] Robot cancels control when in goal x_y tolerance #4681
Comments
Thanks for reporting the issue, let me take a look at it. |
It's very strange that I cannot reproduce your issue. I just tried with @neobotix robots and as well both the turtlebots that we have here. Seems to work fine, even with the parameters you have given. I'm certainly sure you would have rebuilt the package, but just for completeness, may I ask did you actually do it? |
Hi @padhupradheep , |
It could actually be an edge case..
I did the same but wasn't able to reproduce it. I also made a video (sorry for the low quality) with the turtlebot having a different heading at the end: nav2bug.webmIs there any other scenario in depot world, where you can show us the issue? would be great if I get some more details. Thanks! |
Okay I have just removed all build artifact (by $rm -r /build /install /log) and rebuild all the nav2 again with latest commit 771eca4.
From above log, there is a gap before Goal succeeded and the gap is around 10s which is the Wait timeout duration that I set in the xml file. I also capture the rosbag, the last goal in the bag is where the issue happens ( it takes quite many trials to reproduced :) ) |
Any thoughts here @padhupradheep ? |
Unfortunately it is hard to reproduce the issue in our setup. It's good that the user has given a bag, I'd try to clear it soon. |
Hi @padhupradheep , |
Unfortunately not yet, I was also away for a conference. Please allow me some more time to get back to this. |
@chanhhoang99 like mentioned in #4729 could you please try it without composition and let me know if you can reproduce the issue? |
@padhupradheep , Okay I will check it |
Hi @padhupradheep ,
You can see that Below is my launch command: |
Analysing the issue, I see that BT is not inhibiting and causing the problem. @chanhhoang99 I see there seems to be a localization jump when the robot rotates near the goal location, which apparently causes the Maybe you might need to add some behavior to the BT, that could check if the robot is within a specific goal tolerance, after which the @SteveMacenski what do you think? Localization jumps are something that we didn't consider for atleast the example BT that we have. Maybe open sourcing the solution that I showed for #4003 atleast might help @chanhhoang99 get through this issue. |
Agreed! |
Hi @padhupradheep , Thanks for the finding. |
Not yet, I'd update here, when we open source it (let me try to get it ASAP).
Note it is a condition plugin, therefore you would require to tweak around the BT to get your use-case working. |
Ah I see there is already a PR, that adds a similar behavior: #4620 @chanhhoang99 Would it be fine if I close this issue now ? In essence, to solve the problem that you have posted, you need to tweak your BT such that, while reaching the goal proximity, the robot doesn't replan and trigger the |
Thanks @padhupradheep , I think you can close this issue. |
Hi @padhupradheep , would IsPathValid help in this case ?
|
Bug report
Required Info:
Steps to reproduce issue
Expected behavior
Robot end up at desire goal without any wait and canceling action.
Actual behavior
Additional information
From above actual behavior, I suspect this relates to PathLongerOnApproach.
I tried reverting commit de4fd78, issue still persists
Please see video. Screencast from 2024-09-18 11-33-48.webm
Below is my configuration:
The text was updated successfully, but these errors were encountered: