Removed 1 parameter: MPC_USE_HTE.
- Removed 1 parameter:
MPC_USE_HTE. - Most activity in
src/(+1/−12).
Full analysis → Summary: automatic analysis
MPC_USE_HTE.src/ (+1/−12).Full analysis → Summary: automatic analysis
None.
| Name | Last value | Note |
|---|---|---|
MPC_USE_HTE | 1 | removed from src/modules/mc_pos_control/multicopter_position_control_params.c |
No post: no meaningful change.
| Module | Added | Modified | Removed | Lines + | Lines − |
|---|---|---|---|---|---|
src | 0 | 1 | 0 | +1 | −12 |
| Path | Lines | Note | |
|---|---|---|---|
| M | src/modules/mc_pos_control/multicopter_position_control_params.c | +1/−12 |
Remove `MPC_USE_HTE` and always use hover thrust for altitude control (#24751) * Remove `MPC_USE_HTE` and always use hover thrust for altitude control Note the separate module can still be not run but I have not seen a case where the hover thrust estimate is not useful for altitude control hence I don't expect anyone to have the parameter disabled or planning on not running the module. This parameter was used to experimentally introduce the hover thrust estimator. First it was just logging its status and you could opt in to use it: f9794e99f897b842e74a370e5fa77c281aeddce5 but soon after it became the default and you had to opt out of using it: a8063ac94867c2990b0a80c6fdf0dccc835c3356 AFAIK we haven't seen problems requiring to disable it in the last 5 years and hence I suggest to remove the parameter to reduce the configuration space. * Update src/modules/land_detector/MulticopterLandDetector.cpp Co-authored-by: Mathieu Bresciani <brescianimathieu@gmail.com> * undo docs changes * change redundant update() calls to copy() --------- Co-authored-by: Jacob Dahl <37091262+dakejahl@users.noreply.github.com> Co-authored-by: Mathieu Bresciani <brescianimathieu@gmail.com> Co-authored-by: Jacob Dahl <dahl.jakejacob@gmail.com>