-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
condition distance traveled always returns failure #4842
Comments
Please do not cross post. Have you actually tried to use it and see that it doesn't work or just speculating looking at the software? We have a unit test that seems to point to it working [1] |
Yes, I did test it and the condition always returns IDLE.
I added a print out in the
It always prints IDLE. Maybe my behavior tree does not implement this condition correctly? |
Can you check the test and see an error? Unfortunately, we're a bit resource constrained right now, so I do need developers to do a bit of research to help suss out their issues (if they exist). I don't have the bandwidth right now to dig into each reported issue from scratch :-) I see that the main version of this node looks different from the link that you provided based on some hash. What branch is that from, how did you obtain that hash, and have you tested any changes as addressing the behavior (and/or looked at It could be that your hash is from a no longer supported branch / distribution -- or based on BT.CPPv3, and we're on BT.CPPv4 now that has different behavior and definitions for states |
That hash should be the latest commit from the Humble branch. |
Since when the behavior tree is first loaded, all nodes are in the IDLE state before they are ticked for the first time, doesn't this if statement always return IDLE and therefore the tick method always return FAILURE?
navigation2/nav2_behavior_tree/plugins/condition/distance_traveled_condition.cpp
Line 46 in 507b365
I also asked the question here but didn't get answers:
https://robotics.stackexchange.com/questions/114059/nav2-distance-traveled-condition
The text was updated successfully, but these errors were encountered: