Giter Club home page Giter Club logo

kalman's Introduction

Kalman Filter

The Kalman filter is a Bayesian filter that uses multivariate Gaussians, a recursive state estimator, a linear quadratic estimator (LQE), and an Infinite Impulse Response (IIR) filter. It is a control theory tool applicable to signal estimation, sensor fusion, or data assimilation problems. The filter is applicable for unimodal and uncorrelated uncertainties. The filter assumes white noise, propagation and measurement functions are differentiable, and that the uncertainty stays centered on the state estimate. The filter is the optimal linear filter under assumptions. The filter updates estimates by multiplying Gaussians rather than integrating differential equations. The filter predicts estimates by adding Gaussians. The filter maintains an estimate of the state and its uncertainty over the sequential estimation process. The filter is named after Rudolf E. Kálmán, who was one of the primary developers of its theory in 1960.

Designing a filter is as much art as science, with the following recipe. Model the real world in state-space notation. Then, compute and select the fundamental matrices, select the states X, P, the processes F, Q, the measurements Z, R, the measurement function H, and if the system has control inputs U, G. Evaluate the performance and iterate.

This library supports various simple and extended filters. The implementation is independent from linear algebra backends. Arbitrary parameters can be added to the prediction and update stages to participate in gain-scheduling or linear parameter varying (LPV) systems. The default filter type is a generalized, customizable, and extended filter. The default type parameters implement a one-state, one-output, and double-precision floating-point type filter. The default update equation uses the Joseph form. Examples illustrate various usages and implementation tradeoffs. A standard formatter specialization is included for representation of the filter states. Filters with state x output x input dimensions as 1x1x1 and 1x1x0 (no input) are supported through vanilla C++. Higher dimension filters require a linear algebra backend. Customization points and type injections allow for implementation tradeoffs.

Examples

1x1 Constant System Dynamic Model Filter

Example from the building height estimation sample. One estimated state and one observed output filter.

kalman filter;

filter.x(60.);
filter.p(225.);
filter.r(25.);

filter.update(48.54);

full sample code

6x2 Constant Acceleration Dynamic Model Filter

Example from the 2-dimension vehicle location, velocity, and acceleration vehicle estimation sample. Six estimated states and two observed outputs filter.

using kalman = kalman<vector<double, 6>, vector<double, 2>>;

kalman filter;

filter.x(0., 0., 0., 0., 0., 0.);
filter.p(kalman::estimate_uncertainty{ { 500, 0, 0, 0, 0, 0 },
                                       { 0, 500, 0, 0, 0, 0 },
                                       { 0, 0, 500, 0, 0, 0 },
                                       { 0, 0, 0, 500, 0, 0 },
                                       { 0, 0, 0, 0, 500, 0 },
                                       { 0, 0, 0, 0, 0, 500 } });
filter.q(0.2 * 0.2 * kalman::process_uncertainty{ { 0.25, 0.5, 0.5, 0, 0, 0 },
                                                  { 0.5, 1, 1, 0, 0, 0 },
                                                  { 0.5, 1, 1, 0, 0, 0 },
                                                  { 0, 0, 0, 0.25, 0.5, 0.5 },
                                                  { 0, 0, 0, 0.5, 1, 1 },
                                                  { 0, 0, 0, 0.5, 1, 1 } });
filter.f(kalman::state_transition{ { 1, 1, 0.5, 0, 0, 0 },
                                   { 0, 1, 1, 0, 0, 0 },
                                   { 0, 0, 1, 0, 0, 0 },
                                   { 0, 0, 0, 1, 1, 0.5 },
                                   { 0, 0, 0, 0, 1, 1 },
                                   { 0, 0, 0, 0, 0, 1 } });
filter.h(kalman::output_model{ { 1, 0, 0, 0, 0, 0 },
                               { 0, 0, 0, 1, 0, 0 } });
filter.r(kalman::output_uncertainty{ { 9, 0 }, { 0, 9 } });

filter.predict();
filter.update(-375.93, 301.78);

full sample code

4x1 Nonlinear Dynamic Model Extended Filter

Example from the thermal, current of warm air, strength, radius, and location estimation sample. Four estimated states and one observed output extended filter with two additional prediction arguments and two additional update arguments.

using kalman = kalman<vector<float, 4>, float, void, std::tuple<float, float>,
                             std::tuple<float, float>>;

kalman filter;

filter.x(1 / 4.06, 80, 0, 0);
filter.p(kalman::estimate_uncertainty{ { 0.0049, 0, 0, 0 },
                                       { 0, 400, 0, 0 },
                                       { 0, 0, 400, 0 },
                                       { 0, 0, 0, 400 } });
filter.transition([](const kalman::state &x, const float &drift_x,
                     const float &drift_y) -> kalman::state {
  return x + kalman::state{ 0, 0, -drift_x, -drift_y };
});
filter.q(kalman::process_uncertainty{ { 0.000001, 0, 0, 0 },
                                      { 0, 0.0009, 0, 0 },
                                      { 0, 0, 0.0009, 0 },
                                      { 0, 0, 0, 0.0009 } });
filter.r(0.2025);
filter.observation([](const kalman::state &x, const float &position_x,
                      const float &position_y) -> kalman::output {
  return kalman::output{ x(0) *
    std::exp(-((x(2) - position_x)*(x(2) - position_x) +
    (x(3) - position_y) * (x(3) - position_y)) / x(1) * x(1)) };
filter.h([](const kalman::state &x, const float &position_x,
            const float &position_y) -> kalman::output_model {
  const auto exp{ std::exp(-((x(2) - position_x) * (x(2) - position_x) +
    (x(3) - position_y) * (x(3) - position_y)) / (x(1) * x(1))) };
  const kalman::output_model h{
    exp,
    2 * x(0) * (((x(2) - position_x) * (x(2) - position_x) +
    (x(3) - position_y) * (x(3) - position_y)) / (x(1) * x(1))) * exp,
    -2 * (x(0) * (x(2) - position_x) / (x(1) * x(1))) * exp,
    -2 * (x(0) * (x(3) - position_y) / (x(1) * x(1))) * exp
  };
  return h;
});

filter.predict(drift_x, drift_y);
filter.update(position_x, position_y, variometer);

full sample code

Other Examples

Installation

git clone --depth 1 "https://github.com/FrancoisCarouge/kalman"
cmake -S "kalman" -B "build"
cmake --build "build" --parallel
sudo cmake --install "build"
find_package(kalman)
target_link_libraries(your_target PRIVATE kalman::kalman)

For more, see installation instructions.

Reference

Class kalman

Also documented in the fcarouge/kalman.hpp header.

Declaration

template <
  typename State,
  typename Output,
  typename Input,
  typename UpdateTypes,
  typename PredictionTypes>
class kalman

Template Parameters

Template Parameter Definition
State The type template parameter of the state column vector X. State variables can be observed (measured), or hidden variables (inferred). This is the the mean of the multivariate Gaussian. Defaults to double.
Output The type template parameter of the measurement column vector Z. Defaults to double.
Input The type template parameter of the control U. A void input type can be used for systems with no input control to disable all of the input control features, the control transition matrix G support, and the other related computations from the filter. Defaults to void.
UpdateTypes The additional update function parameter types passed in through a tuple-like parameter type, composing zero or more types. Parameters such as delta times, variances, or linearized values. The parameters are propagated to the function objects used to compute the state observation H and the observation noise R matrices. The parameters are also propagated to the state observation function object H. Defaults to no parameter types, the empty pack.
PredictionTypes The additional prediction function parameter types passed in through a tuple-like parameter type, composing zero or more types. Parameters such as delta times, variances, or linearized values. The parameters are propagated to the function objects used to compute the process noise Q, the state transition F, and the control transition G matrices. The parameters are also propagated to the state transition function object F. Defaults to no parameter types, the empty pack.

Member Types

Member Type Dimensions Definition Also Known As
estimate_uncertainty x by x Type of the estimated, hidden covariance matrix p. P, Σ
gain x by z Type of the gain matrix k. K, L
innovation_uncertainty z by z Type of the innovation uncertainty matrix s. S
innovation z by 1 Type of the innovation column vector y. Y
input_control x by u Type of the control transition matrix g. This member type is defined only if the filter supports input control. G, B
input u by 1 Type of the control column vector u. This member type is defined only if the filter supports input. U
output_model z by x Type of the observation transition matrix h. This member type is defined only if the filter supports output model. H, C
output_uncertainty z by z Type of the observation, measurement noise covariance matrix r. R
output z by 1 Type of the observation column vector z. Z, Y, O
process_uncertainty x by x Type of the process noise covariance matrix q. Q
state_transition x by x Type of the state transition matrix f. F, Φ, A
state x by 1 Type of the state estimate, hidden column vector x. X

Member Functions

Member Function Definition
(constructor) Constructs the filter.
(destructor) Destructs the filter.
operator= Assigns values to the filter.

Characteristics

Characteristic Definition
f Manages the state transition matrix F. Gets the value. Initializes and sets the value. Configures the callable object of expression state_transition(const state &, const input &, const PredictionTypes &...) to compute the value. The default value is the identity matrix.
g Manages the control transition matrix G. Gets the value. Initializes and sets the value. Configures the callable object of expression input_control(const PredictionTypes &...) to compute the value. The default value is the identity matrix. This member function is defined only if the filter supports input control.
h Manages the observation transition matrix H. Gets the value. Initializes and sets the value. Configures the callable object of expression output_model(const state &, const UpdateTypes &...) to compute the value. The default value is the identity matrix. This member function is defined only if the filter supports output model.
k Manages the gain matrix K. Gets the value last computed during the update. The default value is the identity matrix.
p Manages the estimated covariance matrix P. Gets the value. Initializes and sets the value. The default value is the identity matrix.
q Manages the process noise covariance matrix Q from the process noise w expected value E[wwᵀ] and its variance σ² found by measuring, tuning, educated guesses of the noise. Gets the value. Initializes and sets the value. Configures the callable object of expression process_uncertainty(const state &, const PredictionTypes &...) to compute the value. The default value is the null matrix.
r Manages the observation, measurement noise covariance matrix R from the measurement noise v expected value E[vvᵀ] and its variance σ² found by measuring, tuning, educated guesses of the noise. Gets the value. Initializes and sets the value. Configures the callable object of expression output_uncertainty(const state &, const output &, const UpdateTypes &...) to compute the value. The default value is the null matrix.
s Manages the innovation uncertainty matrix S. Gets the value last computed during the update. The default value is the identity matrix.
u Manages the control column vector U. Gets the value last used in prediction. This member function is defined only if the filter supports input.
x Manages the state estimate column vector X. Gets the value. Initializes and sets the value. The default value is the null column vector.
y Manages the innovation column vector Y. Gets the value last computed during the update. The default value is the null column vector.
z Manages the observation column vector Z. Gets the value last used during the update. The default value is the null column vector.
transition Manages the state transition function object f. Configures the callable object of expression state(const state &, const input &, const PredictionTypes &...) to compute the transition state value. The default value is the equivalent to f(x) = F * X. The default function is suitable for linear systems. For extended filters transition is a linearization of the state transition while F is the Jacobian of the transition function: F = ∂f/∂X = ∂fj/∂xi that is each row i contains the derivatives of the state transition function for every element j in the state column vector X.
observation Manages the state observation function object h. Configures the callable object of expression output(const state &, const UpdateTypes &...arguments) to compute the observation state value. The default value is the equivalent to h(x) = H * X. The default function is suitable for linear systems. For extended filters observation is a linearization of the state observation while H is the Jacobian of the observation function: H = ∂h/∂X = ∂hj/∂xi that is each row i contains the derivatives of the state observation function for every element j in the state vector X.

Modifiers

Modifier Definition
predict Produces estimates of the state variables and uncertainties.
update Updates the estimates with the outcome of a measurement.

Format

A specialization of the standard formatter is provided for the filter. Use std::format to store a formatted representation of all of the characteristics of the filter in a new string. Standard format parameters to be supported.

kalman filter;

std::print("{}", filter);
// {"f": 1, "h": 1, "k": 1, "p": 1, "q": 0, "r": 0, "s": 1, "x": 0, "y": 0, "z": 0}

Considerations

Motivations

Kalman filters can be difficult to learn, use, and implement. Users often need fair algebra, domain, and software knowledge. Inadequacy leads to incorrectness, underperformance, and a big ball of mud.

This package explores what could be a Kalman filter implementation a la standard library. The following concerns are considered:

  • Separation of the application domain and integration needs.
  • Separation of the mathematical concepts and linear algebra implementation.
  • Generalization and specialization of modern language and library support.

Selected Tradeoffs

In theory there is no difference between theory and practice, while in practice there is. The following engineering tradeoffs have been selected for this library implementation:

  • Update and prediction additional arguments are stored in the filter at the costs of memory and performance for the benefits of consistent data access and records.
  • The default floating point data type for the filter is double with about 16 significant digits to reduce loss of information compared to float.
  • The ergonomics and precision of the default filter takes precedence over performance.

Lessons Learned

Design, development, and testing uncovered unexpected facets of the projects:

  • The filter's state, output, and input column vectors should be type template parameters to allow the filter to participate in full compile-time verification of unit- and index-type safeties for input parameters and characteristics.
  • There exist Kalman filters with hundreds of state variables.
  • The float data type has about seven significant digits. Floating point error is a loss of information to account for in design.

Performance

The benchmarks share some performance information. Custom specializations and implementations can outperform this library. Custom optimizations may include: using a different covariance estimation update formula; removing symmetry support; using a different matrix inversion formula; removing unused or identity model dynamics supports; implementing a generated, unrolled filter algebra expressions; or running on accelerator hardware.

Eigen Update Float

Resources

Definitions

Term Definition
EKF The Extended Kalman Filter is the nonlinear version of the Kalman filter. Useful for nonlinear dynamics systems. This filter linearizes the model about an estimate working point of the current mean and covariance.
ESKF The Error State Kalman Filter is the error estimation version of the Kalman filter. Useful for linear error state dynamics systems. This filter estimates the errors rather than the states.
UKF The Unscented Kalman Filter is the sampled version of the Extended Kalman Filter. Useful for highly nonlinear dynamics systems. This filter samples sigma points about an estimate working point of the current mean using an Unscented Transformation technique.

Further terms should be defined and demonstrated for completeness: CKF, EKF-IMM, EnKF, Euler-KF, Fading-Memory, Finite/Fixed-Memory, Forward-Backward, FKF, IEKF, Joseph, KF, Linearized, MEKF, MRP-EKF, MRP-UKF, MSCKF, SKF, Smoother, UKF-GSF, UKF-IMM, USQUE, UDU, and UT.

Articles

Resources to learn about Kalman filters:

Projects

The library is used in projects:

  • GstKalman: A GStreamer Kalman filter video plugin.

Your project link here!

Third Party Acknowledgement

The library is designed, developed, and tested with the help of third-party tools and services acknowledged and thanked here:

Sponsors

Become a sponsor today! Support this project with coffee and infrastructure!

Sponsor

Corporations & Institutions

Your group logo and link here!

Individuals

Your name and link here!

Thanks everyone!

Continuous Integration & Deployment Actions

Code Repository

Pipeline

Sanitizer
Format
ClangTidy
Coverage Status
CppCheck
Doxygen
Valgrind

Public Domain
License Scan

Deploy Doxygen
Deploy Code Coverage

Sponsor

License

Kalman Filter is public domain:

This is free and unencumbered software released into the public domain.

Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.

In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain. We make this dedication for the benefit of the public at large and to the detriment of our heirs and successors. We intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

For more information, please refer to https://unlicense.org

kalman's People

Contributors

dependabot[bot] avatar francoiscarouge avatar step-security-bot avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar

kalman's Issues

Case Study

Is your feature request related to a problem? Please describe.
A case study with a non-trivial filter comparing and benchmarking different implementation, backends would expose or clarify suspected insights.

Describe the solution you'd like
For example, a 20+ states inertial navigation system extended filter, with a data set, and a symbolic pre-implementation optimized solution compared to the different linear algebra backends could show the benefits/tradeoffs of the solutions with more realistic benchmark data.

Add a benchmark

Is your feature request related to a problem? Please describe.
Benchmarks are critical to demonstrate, compare, test, regress the performance of the library. There is room to add more benchmarks. The library plots its performance. The goal of this story is to add, improve the coverage of the benchmark.

Describe the solution you'd like
One more benchmark source file, plot support in the benchmark directory. Either an absolute benchmark of the library or a comparison against another implementation. The code should be lean, well documented. Give credit and sources where appropriate.

Add another useful continuous integration and deployment pipeline stage

Is your feature request related to a problem? Please describe.
The CI/CD pipeline helps in the development and regression of the library by ensuring portability, code quality, performance regression, standardization, security, style, and many other useful supports. There is always room to add yet another type of pipeline stage against other architecture, another quality tool, security tool, performance support, or other standards. The goal of this story is to add, update, or improve the CI/CD pipeline support,

Describe the solution you'd like
A CI/CD pipeline definition in the .github/workflows folder.

Research and resolve one of the todo items

Is your feature request related to a problem? Please describe.
A number of to be done, to be resolved, or to be confirmed questions, features, or activities are marked in the codebase with the @todo documentation tags. Some of them are reported in the todo documentation list. There are all sorts of topics treated: C++, linear algebra, control theory. The goal of this story is to resolve one of them.

Describe the solution you'd like
No solution is prescribed as the to be done item is a pure open question to be researched, tested, benchmarked, weighted against solutions, or rationalized.

Add a sample

Is your feature request related to a problem? Please describe.
Examples, samples, are critical to help users of the library understand what the library can do and how to use it. While a number of samples are provided, there is room to add more. Kalman filters are used for all sorts of applications, domains, usages in typical or uncommon sizes, types, or domains. The goal of this story is to add one more sample.

Describe the solution you'd like
One more sample source file in the sample directory. The code should be lean, well documented, and tested against a simulated truth. Be conscious of copyright or licensing matters. Give credit and sources where appropriate.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.