Skip to content

Commit

Permalink
Fix merge conflict in nav2_mppi_controller README (humble) (ros-navig…
Browse files Browse the repository at this point in the history
…ation#4239)

Signed-off-by: Stephanie Eng <[email protected]>
  • Loading branch information
stephanie-eng authored and RBT22 committed Apr 9, 2024
1 parent d59d445 commit 83a7a4a
Showing 1 changed file with 0 additions and 3 deletions.
3 changes: 0 additions & 3 deletions nav2_mppi_controller/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,11 +53,8 @@ This process is then repeated a number of times and returns a converged solution
| gamma | double | Default: 0.015. A trade-off between smoothness (high) and low energy (low). This is a complex parameter that likely won't need to be changed from the default of `0.1` which works well for a broad range of cases. See Section 3D-2 in "Information Theoretic Model Predictive Control: Theory and Applications to Autonomous Driving" for detailed information. |
| visualize | bool | Default: false. Publish visualization of trajectories, which can slow down the controller significantly. Use only for debugging. |
| retry_attempt_limit | int | Default 1. Number of attempts to find feasible trajectory on failure for soft-resets before reporting failure. |
<<<<<<< HEAD
| reset_period | double | Default 1.0. required time of inactivity to reset optimizer (only in Humble due to backport ABI policies) |
=======
| regenerate_noises | bool | Default false. Whether to regenerate noises each iteration or use single noise distribution computed on initialization and reset. Practically, this is found to work fine since the trajectories are being sampled stochastically from a normal distribution and reduces compute jittering at run-time due to thread wake-ups to resample normal distribution. |
>>>>>>> 924f1673 ([MPPI Optimization] adding regenerate noise param + adding docs (#3868))

#### Trajectory Visualizer
| Parameter | Type | Definition |
Expand Down

0 comments on commit 83a7a4a

Please sign in to comment.