Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

ekf2: add kconfig option to enable/disable optical flow fusion #21338

Merged
merged 2 commits into from
Mar 21, 2023

Conversation

dagar
Copy link
Member

@dagar dagar commented Mar 20, 2023

No description provided.

@dagar dagar requested a review from bresch March 20, 2023 15:46
@dagar dagar force-pushed the pr-ekf2_kconfig branch from fac82e2 to 52d6df5 Compare March 20, 2023 15:47
@dagar dagar force-pushed the pr-ekf2_kconfig branch from 482ddaf to 7a21b26 Compare March 20, 2023 16:57
Comment on lines +134 to +136
_param_ekf2_terr_mask(_params->terrain_fusion_mode),
_param_ekf2_terr_noise(_params->terrain_p_noise),
_param_ekf2_terr_grad(_params->terrain_gradient),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if we still want the terrain estimate using optical flow? I think those parameters should only be removed if rng and flow are disabled

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was going to do terrain estimator separately, but at the moment EKF2_OPTICAL_FLOW depends on EKF2_RANGE_FINDER and I was thinking we should just extract the terrain estimator into a separate class anyway.

@dagar dagar merged commit 32a5bd3 into main Mar 21, 2023
@dagar dagar deleted the pr-ekf2_kconfig branch March 21, 2023 15:25
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants