Skip to content

FusionLocalizer: do not read past an unusable control_config - #172

Merged
fmrico merged 1 commit into
rollingfrom
fusion_control_config
Nov 1, 2026
Merged

fmrico merged 1 commit into
rollingfrom
fusion_control_config

Conversation

@fmrico

@fmrico fmrico commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Closes #171.

When the control term ends up disabled, control_update_vector is now reset to six false values, so the IMU acceleration checks always read a valid vector.

Test: a local filter with an IMU that measures accelerations, use_control: true and each of these control_config values:

  • missing;
  • empty;
  • too short;
  • too long;
  • all false;
  • valid.

It must start and stay finite with every one of them. Before the fix, the empty case segfaulted.

Signed-off-by: Francisco Martín Rico <fmrico@gmail.com>
@fmrico
fmrico merged commit 8b0421d into rolling Nov 1, 2026
1 check passed
@fmrico
fmrico deleted the fusion_control_config branch November 1, 2026 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FusionLocalizer crashes at startup with use_control and an unusable control_config plus an IMU

1 participant