#include <armarx/navigation/core/NavigationStackGeneralConfig.h>
◆ ~GeneralConfig()
◆ FromAron()
◆ toAron()
◆ boundaryVelocity
| float boundaryVelocity = 150 |
Speed the profile is floored at [mm/s].
Needed at the start: a GlobalTrajectory assigns a velocity to a position, so v(s = 0) = 0 is a fixed point – the controller looks up zero at the pose it is standing in, commands zero, and the robot never leaves the start.
◆ cornerLimit
◆ cornerVelocity
| float cornerVelocity = 200 |
◆ enableRampingCorners
| bool enableRampingCorners = true |
◆ enableRampingEnd
| bool enableRampingEnd = true |
◆ enableRampingStart
| bool enableRampingStart = true |
◆ goalVelocity
Speed the profile is allowed to fall to at the goal [mm/s].
The start's argument does not apply here: nothing has to get the robot moving again once it is at the goal, and a floor of boundaryVelocity there is precisely what it overshoots on. The feed-forward tracks the profile up to the last waypoint, so the robot arrives at the goal still commanded at that speed; the controller's final-segment law then steps the demand down in a single cycle and the command slew needs v^2 / (2 a) of run-out to absorb it – measured at 45-59 mm on ARMAR-7 with the historical 150 mm/s.
Kept above zero rather than at it, so the fixed-point argument cannot bite here either if the robot is nudged back onto the tail of the profile.
◆ inCollisionDistanceThresholdForRecovery
| float inCollisionDistanceThresholdForRecovery {100.0F} |
Maximum distance [mm] to search for a valid recovery position when robot starts in collision.
◆ maxVel
◆ minVel
◆ navigateCloseAsPossible
| bool navigateCloseAsPossible {false} |
If true and the goal is not reachable, navigate to the closest reachable position instead of failing.
◆ parametrization
How the planned velocity profile is (re-)assigned before execution.
◆ rampLength
The documentation for this struct was generated from the following files: