From 9d9db1be1b83bec48a13640fcdbe5eee82b8403b Mon Sep 17 00:00:00 2001 From: Stephanie Eng Date: Thu, 4 Apr 2024 15:55:37 -0400 Subject: [PATCH] Fix merge conflict in nav2_mppi_controller README (humble) (#4239) Signed-off-by: Stephanie Eng --- nav2_mppi_controller/README.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/nav2_mppi_controller/README.md b/nav2_mppi_controller/README.md index 1e8c7c2eba..164f20fe4c 100644 --- a/nav2_mppi_controller/README.md +++ b/nav2_mppi_controller/README.md @@ -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 |