10
$\begingroup$

I am currently working on a project for school where I need to implement an extended Kalman Filter for a point robot with a laser scanner. The Robot can rotate with 0 degree turn radius and drive forward. All motions are piecewise linear (drive,rotate,drive).

The simulator we are using does not support acceleration, all motion is instantaneous.

We also have a known map (png image) that we need to localize in. We can ray trace in the image in order to simulate laser scans.

My partner and I are little confused as to the motion and sensor models we'll need to use.

So far we are modelling the state as a vector $(x,y,\theta)$.

We are using the update equations as follows

void kalman::predict(const nav_msgs::Odometry msg){
    this->X[0] += linear * dt * cos( X[2] ); //x
    this->X[1] += linear * dt * sin( X[2] ); //y
    this->X[2] += angular * dt; //theta

    this->F(0,2) = -linear * dt * sin( X[2] ); //t+1 ?
    this->F(1,2) =  linear * dt * cos( X[2] ); //t+1 ?

    P = F * P * F.t() + Q;

    this->linear = msg.twist.twist.linear.x;
    this->angular = msg.twist.twist.angular.z;
    return;
}

We thought we had everything working until we noticed that we forgot to initialize P and that it was zero, meaning that there was no correction happening. Apparently our propagation was very accurate as we haven't yet introduced noise into the system.

For the motion model we are using the following matrix for F:

$F = \begin{bmatrix}1 & 0 & -v*\Delta t*sin(\theta) \\ 0 & 1 & v*\Delta t*cos(\theta) \\ 0 & 0 & 1 \end{bmatrix}$

As its the Jacobian of our update formulas. Is this correct?

For the sensor model we are approximating the Jacobian (H) by taking finite differences of the robots $x$, $y$ and $\theta$ positions and ray tracing in the map. We talked to the TA who said that this would work but I'm still unsure it will. Our prof is away so we can't ask him unfortunately. We are using 3 laser measurements per correction step so H is a 3x3.

The other issue where having how to initialize P. We tried 1,10,100 and they all place the robot outside the map at (-90,-70) when the map is only 50x50.

The code for our project can be found here: https://github.com/en4bz/kalman/blob/master/src/kalman.cpp

Any advice is greatly appreciated.

EDIT:

At this point I've gotten the filter to stabilize with basic movement noise but no actual movement. As soon as the robot starts to move the filter diverges quite quickly and exits the map.

$\endgroup$

2 Answers 2

3
$\begingroup$
  • Using EKF for localisation based on laser scans and a known map is a bad idea and will not work because one of EKF's main assumptions is not valid: The measurement model is not differentiable.

I would suggest looking into Monte Carlo Localization (Particle Filters). This will not only solve the problem with your measurement model, but also allow global localization (initial pose within the map completely unknown).

Edit: I am sorry I forgot to mention another important point:

  • If you want to apply EKF, your measurement model as well as your motion model may only include Gaussian noise. This means you need be able to write down your measurement model as $z_t = h(x_t) + N(0, Q_t)$. This is is a severe limitation, since it does not allow a slightly more complex model like the beam_range_finder_model in Probabilistic Robotics, which also considers dynamic objects in front of the robot, invalid (max) measurements and completely random readings. You would be stuck with casting rays for the $h(x_t)$ part and adding Gaussian noise.
$\endgroup$
2
  • $\begingroup$ ^^"Using EKF for localisation based on laser scans and a known map is a bad idea" who said that? Please provide the references. EKF is the most successful estimator and many papers suggest using EKF for localization problem. Actually, I'm surprised about you are saying. The main assumptions of EKF are the motion and observation models are linear and the noise is Gaussian. I don't know what do you mean by "The measurement model is not differentiable." $\endgroup$
    – CroCo
    Jun 11, 2014 at 6:52
  • $\begingroup$ The original poster mentioned raytracing which means he intends to use a measurement model similar to the "beam model of range finders" in probabilistic robotics. This measurement model exhibits jumps (Imagine a laser beam barely hitting an obstacle and missing it: It only takes a tiny rotation for a jump which is not differentiable.) $\endgroup$
    – sebsch
    Jun 11, 2014 at 8:51
0
$\begingroup$

First of all, you mentioned nothing about which kind of localization you are using. Is it with known or unknown correspondences?

Now to acquire the Jacobian in Matlab you may do the following

>> syms x y a Vtran Vrotat t
>> f1 = x + Vtran*t*cos(a);
>> f2 = y + Vtran*t*sin(a);
>> f3 = a + Vrotat*t;
>> input  = [x y a];
>> output = [f1 f2 f3];
>> F = jacobian(output, input)

The result

F =
[ 1, 0, -Vtran*t*sin(a)]
[ 0, 1,  Vtran*t*cos(a)]
[ 0, 0,               1]

Extended Kalman Filter requires the system to be linear and the noise to be Gaussian. The system here means the motion and observation models must be linear. Laser sensors give the range and the angle toward a landmark from the robot's frame, so the measurement model is not linear. About P, if you assume it to be large then your EKF estimator will be poor at the beginning and it relies on the measurements because the previous state vector is not available. However, once your robot starts moving and sensing, EKF will be getting better because it uses the motion and measurement models to estimates the robot's pose. If your robot is not sensing any landmarks, the uncertainty increases drastically. Also, you need to be careful about the angle. In C++, cos and sin, the angle should be in radian. There is nothing in your code about this issue. If you are assuming the angle's noise in degree while your calculation in radian, then you might get weird results because one degree as a noise while the calculations in radian is considered huge.

$\endgroup$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.