You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When Pathfinding to a path, during the PathfindingCommand, the robot will simply stop after a few seconds.
After some digging, it seems to be an issue relating to how the isFinished method for the command is calculated, mainly with the return statement on line 367 (for Python). Upon removing this line, the issue resolves itself, so I believe the implementation of stoppingDistance is incorrect here.
After looking at the same methods in Java and C++, it seems this issue may be present in all languages of PPLib.
To Reproduce
Steps to reproduce the behavior:
Run a AutoBuilder.pathfindThenFollowPath command.
Observe how it stops early.
Expected behavior
The robot is supposed to pathfind without any stopping to the start of the path, then seamlessly execute the path.
Versions: (please complete the following information):
OS: Windows 11
GUI Version: 2025.0.0-beta-5
PPLib Version: 2025.0.0b5
PPLib Language: Python
Additional context
The repository I have used for testing and encountering this bug can be found here.
The text was updated successfully, but these errors were encountered:
Describe the bug
When Pathfinding to a path, during the PathfindingCommand, the robot will simply stop after a few seconds.
After some digging, it seems to be an issue relating to how the isFinished method for the command is calculated, mainly with the return statement on line 367 (for Python). Upon removing this line, the issue resolves itself, so I believe the implementation of stoppingDistance is incorrect here.
After looking at the same methods in Java and C++, it seems this issue may be present in all languages of PPLib.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The robot is supposed to pathfind without any stopping to the start of the path, then seamlessly execute the path.
Versions: (please complete the following information):
Additional context
The repository I have used for testing and encountering this bug can be found here.
The text was updated successfully, but these errors were encountered: