Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Add 'No filter' and 'Optimized KF' setups #108

Merged
merged 10 commits into from
May 20, 2022
Merged

Conversation

aguscas
Copy link
Collaborator

@aguscas aguscas commented Apr 26, 2022

No description provided.

@aguscas aguscas force-pushed the optimized-kalman-filter branch 2 times, most recently from 6f832c0 to 3b4174c Compare April 27, 2022 12:22
Copy link
Contributor

@joaqo joaqo left a comment

Choose a reason for hiding this comment

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

This is great! I am thinking we should probably change the filter setup classes' names to 'filter factory', as it more accurately represents what they do, and why they need to have separate classes. Also we should probably rename the old FilterSetup to something like FilterPyKalmanFilterFactory. We can discuss this whenever you have time.

joaqo added 2 commits May 20, 2022 18:40
It seems the new optimized filter is a tiny bit less accurate, so we are
regressing this until we find out why. They should be identically
accurate in theory.
@joaqo joaqo merged commit 80a2a36 into master May 20, 2022
@joaqo joaqo deleted the optimized-kalman-filter branch May 20, 2022 18:48
javiber pushed a commit that referenced this pull request Sep 13, 2022
Add 'No filter' and 'Optimized KF' setups
javiber pushed a commit that referenced this pull request Sep 13, 2022
Add 'No filter' and 'Optimized KF' setups
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.

2 participants