The Kalman Filter with Velocity

Hi all, here’s how to implement a position-and-velocity Kalman filter from scratch, in C++ish pseudocode, from the perspective of a developer who isn’t a professional mathematician and doesn’t understand the kind of symbology used in many Kalman articles. I wrote another article about a simpler Kalman filter as a primer on the subject, if you read it first it will hopefully help make this article easier to understand.

Firstly we need to implement some matrix maths stuff as a prerequisite. It might help to skim-read Wikipedia on the topic first.

// A 2-row column vector.
struct Vector {
    double a // aka Position or Price
    double b // aka Velocity
// A 2x2 matrix.
struct Matrix {
    double tl // Top Left, eg row 1 column 1
    double tr // Top right, r1c2
    double bl // Bottom left, r2c1
    double br // Bottom right, r2c2
// vectorA + vectorB.
+(Vector lhs, Vector rhs) -> Vector {
    return Vector {
        a: lhs.a + rhs.a,
        b: lhs.b + rhs.b
// vectorA - vectorB.
-(Vector lhs, Vector rhs) -> Vector {
    return Vector(
        a: lhs.a - rhs.a,
        b: lhs.b - rhs.b
// matrixA + matrixB.
+(Matrix lhs, Matrix rhs) -> Matrix {
    return Matrix(
        tl: +, tr: +,
        bl: +, br: +
// matrixA - matrixB.
-(Matrix l, Matrix r) -> Matrix {
    return Matrix(
        tl: -, tr: -,
        bl: -, br: -
// matrixA * matrixB.
*(Matrix l, Matrix r) -> Matrix {
    return Matrix(
        tl: * + *,
        tr: * + *,
        bl: * + *,
        br: * + *
// vectorOutput = matrixA * vectorB.
*(Matrix m, Vector v) -> Vector {
    return Vector(
        a: * v.a + * v.b,
        b: * v.a + * v.b
// Invert a matrix (the matrix version of 1 / m).
invert(Matrix m) -> Matrix {
    return Matrix(
        tl:, tr:,
        bl:, br:
// Transpose a matrix (mirror it diagonally).
transpose(Matrix m) -> Matrix {
    return Matrix(
        tl:, tr:,
        bl:, br:

Next, you’ll need the ‘external noise covariance matrix’. This is usually referred to as Q in Kalman literature:

const double Q_POSITION_VARIANCE = 0.1
const double Q_VELOCITY_VARIANCE = 0.1
const Matrix Q_EXTERNAL_NOISE = {

Next, you’ll need the ‘measurement noise covariance matrix’, aka R in Kalman articles:

const double R_POSITION_VARIANCE = 0.1
const double R_VELOCITY_VARIANCE = 0.1
const Matrix R_MEASUREMENT_NOISE = {

How do you select good Q and R values? I’m not an expert, but here’s my two tips:

  • If you’re filtering position and velocity sensors that have a normal / gaussian error, and they really are separate sensors as opposed to faking velocity by nowPosition-lastPosition, use the variance and covariance of the two sensors for R, and perhaps experiment with Q until it works the way you’d like. Variance = average[residual^2], covariance = average[positionResidual * velocityResidual], residual = measuredValue - realValue. If you don’t have real values, you could try substituting some kind of moving average.
  • If you’re filtering non-gaussian data (eg stock prices), or your velocity is faked, simply experiment with Q and R until you’re happy with the filter performance. I’d write a program to generate a million random Q+R pairs, then choose the pair that predicts ‘next’ data points best. That is a (whopping) exercise for the reader, sorry!

Next, we need our ‘state transition matrix’, aka F in Kalman articles. This is a constant matrix that, when multiplied by the current state vector (position + velocity), gives us our expected next state vector (old position + velocity, same velocity). Eg it looks like:

const Matrix F_STATE_TRANSITION = {
    tl: 1, tr: 1,
    bl: 0, br: 1,

Maybe the above needs more explaining. Say our old state is position 100m, velocity 10m/s. Multiplying this by F works out like so:

Normal matrix * vector formula:
a: * vec.a + * vec.b,
b: * vec.a + * vec.b


new position: * position + * velocity
new velocity: * position + * velocity


new position: 1 * position + 1 * velocity
new velocity: 0 * position + 1 * velocity


new position: position + velocity
new velocity: velocity


new position: 110m
new velocity: 10m/s

In other words, for a timestep of 1 second, F simply adds the velocity-per-second to the current position, and assumes no friction hence velocity stays constant.

Next, we need the ‘state error’, aka P in Kalman articles. I find it usually works fine to start filtering with this as 1. (Perhaps this should be scaled to match your typical values.)

Matrix pStateError = {
    tl: 1, tr: 1,
    bl: 1, br: 1,

Next, we need our ‘current state’, aka X in Kalman articles. If, like me, you’re faking the velocity, start the filter with this set using the first two measurements:

Vector xCurrentState = {
    a: data[1],
    b: data[1] - data[0], // Faux velocity.

Phew! Now for the interesting bit. For each new data point/measurement, we need to first predict what it’ll be, then blend that prediction with the measurement to produce an estimate. This estimate is the filter’s output. A ‘Kalman gain’ (known as K in Kalman articles) is calculated then is used to weight the prediction vs measurement when blending them to form the estimate:

// Make predictions.
Vector xPredicted = F_STATE_TRANSITION * xCurrentState

// Update it with the measurement.
Vector zMeasurement = Vector {
    a: data[current_index], // Position.
    b: data[current_index] - data[previous_index] // Faux velocity.
Matrix kKalmanGain = pPredicted * invert(pPredicted + R_MEASUREMENT_NOISE_VARIANCE)
Vector xEstimate = xPredicted + kKalmanGain * (zMeasurement - xPredicted)
Matrix pEstimate = pPredicted - kKalmanGain * pPredicted

// Store for the next iteration.
pStateError = pEstimate
xCurrentState = xEstimate // This is the output!

Thanks for reading, I hope this helped, God bless, and have a nice week :)

Thanks for reading! And if you want to get in touch, I'd love to hear from you: chris.hulbert at gmail.

Chris Hulbert

(Comp Sci, Hons - UTS)

iOS Developer (Freelancer / Contractor) in Australia.

I have worked at places such as Google, Cochlear, Assembly Payments, News Corp, Fox Sports, NineMSN, FetchTV, Coles, Woolworths, Trust Bank, and Westpac, among others. If you're looking for help developing an iOS app, drop me a line!

Get in touch:
[email protected]

 Subscribe via RSS