move_basic
move_basic copied to clipboard
UbiquityRobotics
A minimal navigation node
The move_smooth version of move_basic should get separated and moved back here as a branch (as a start) and then merged to become the main version later down the line...
As discussed we'll try to implement two types of path planning: - A* paths to do collision avoidance (Janez) - a system that doesn't use occupancy grids (Jan) We can...
As discussed, we should make an attempt to make the collision checker into a standalone node, which can publish info to other nodes as well.
After #103 is done and we've got move_smooth to work on, we should do a general rewrite of the node to clean up the code and sort out or at...
I suppose this is something that we all know about, but nobody ever brought it up as an actual issue. Here's a worst case scenario example: https://user-images.githubusercontent.com/9977799/138290844-c99feae5-af33-458e-a6a2-a8d1d6eed770.mp4 Like how many...
Once move_smooth is added to this repo as a branch (issue #103 is prerequisite), we'll need to implement zero radius turning to mimic original move_basic behaviour. I've assigned Janez here...
Another thing seen by a client, it seems that in some cases the robot follows goals with a constant offset of sorts. It's likely this is related to lidar position...
So there seems to be a lot of info that move_basic is aware of during goal movement, but cannot be communicated back to the action client. There is technically a...
Something odd reported by a client, they seem to be getting a "MoveBasic: Done linear" in cases where the robot hits the goal, but more often than not the case...