nobleo / path_tracking_pid

Path Tracking PID offers a tuneable PID control loop, decouling steering and forward velocity

nobleo/path_tracking_pid Issues

Controller never succeeds, and turns around at the end of the path
Updated a year ago3
publishing nan velocity due to infinite inverse radius assignment
Updated a year ago2
How to run with the branch "first-ros2-conversion"
Updated 2 years ago
how to use full_coverage_path_planner and path_tracking_pid?
Updated 2 years ago3
about how use this package
Updated 2 years ago1
Straight line into turn: starting turn too early
Updated 3 years ago
Step response of the lowpass filter has an overshoot
Closed 3 years ago4
Is the calculated stopping distance too conservative?
Updated 3 years ago5
Controller's end phase distance is calculated wrong for backwards motion
Closed 3 years ago1
Global plan is statically transformed to the global frame
Updated 3 years ago
Angle calculation of closestPointOnSegment() should be changed
Updated 3 years ago5
Tests broken
Closed 3 years ago3
`Controller::getControllerState()` should be refactored
Closed 3 years ago
`Controller::findPositionOnPlan()` should be refactored
Closed 3 years ago1
UB in `TrackingPidLocalPlanner::projectedCollisionCost()` - partially uninitialized object used
Updated 3 years ago
Does `Controller::findPositionOnPlan()` do what is intended?
Updated 3 years ago1
`Controller::distToSegmentSquared()` should be refactored
Closed 3 years ago2
Documentation of `Controller::distToSegmentSquared()` incorrect
Closed 3 years ago5
`path_tracking_pid::PidConfig config_` should be decoupled from dynamic reconfigure
Updated 3 years ago
`Controller::distToSegmentSquared()` ignores z-component half the time
Updated 3 years ago3
`Controller::mpc_based_max_vel()` and `Controller::update()` interaction should be refactored
Updated 3 years ago1
Controller is too conservative in its collision checking
Closed 3 years ago8
Build fails when CATKIN_ENABLE_TESTING=OFF
Updated 3 years ago
Controller state doesn't need to be reset on reconfigure
Updated 3 years ago5
Some variable names are unclear
Updated 3 years ago1
`computeVelocityCommand` has nested function with the same name.
Updated 3 years ago
Global plan is changed to the controller's liking
Closed 3 years ago
Controller inherits from `nav_core::BaseLocalPlanner`, but does not support it
Closed 3 years ago
Simplify the math being done to calculate direction to goal
Closed 3 years ago
Move more visualization away from implementation
Closed 3 years ago
Refactor geometry_msgs::* to tf2:: datatypes where possible in controller.hpp
Closed 3 years ago
Slow down based on expanded-footprint <=> lethal-obstacle distance
Updated 3 years ago
Use only filtered error in P I D calculations
Updated 3 years ago1
Controller rejects goals when its last setpoint does not agree with odom velocity (on `init_vel_method` `pid_odom`)
Updated 3 years ago
Controller does not support `nav_core::BaseLocalPlanner`
Closed 3 years ago1
Calling cancel blocks the controller
Updated 3 years ago
Controller reconfigures itself on cancel
Closed 3 years ago7
Don't append the global plan
Updated 3 years ago
Current logic to slow down vehicles too conservative for robots with very asymmetric footprint
Updated 3 years ago
Possible unsigned underflow
Closed 3 years ago2
Check if constants should be replaced by user-configurable parameters
Updated 3 years ago4
Tests don't fail while tracking error is ginormous.
Updated 3 years ago
Collision polygon is rather conservative
Updated 3 years ago4
Controller uses path poses differently than expected
Updated 3 years ago
Collision polygon does not include all predicted footprints entirely
Updated 3 years ago
Code review
Closed 3 years ago2
A cancel of the `exe_path` action sets `target_x_vel` parameter to zero
Updated 3 years ago3
Regarding the inability to trace the global path？
Updated 3 years ago8
About the use of path_tracking_pid function package
Closed 3 years ago