Giter VIP home page Giter VIP logo

benchmarks-attitude-smartphones's Introduction

This work is a part of On Attitude Estimation with Smartphones project
http://tyrex.inria.fr/mobile/benchmarks-attitude/

Abstract

We investigate the precision of attitude estimation algorithms in the particular context of pedestrian navigation with commodity smartphones and their inertial/magnetic sensors. We report on an extensive comparison and experimental analysis of existing algorithms. We focus on typical motions of smartphones when carried by pedestrians. We use a precise ground truth obtained from a motion capture system. We test state-of-the-art attitude estimation techniques with several smartphones, in the presence of magnetic perturbations typically found in buildings. We discuss the obtained results, analyze advantages and limits of current technologies for attitude estimation in this context. Furthermore, we propose a new technique for limiting the impact of magnetic perturbations with any attitude estimation algorithm used in this context. We show how our technique compares and improves over previous works.

How it works ?

To start, open a matlab console. Go to src folder. Add this folder and subfolders to the matlab path:

cd YOUR_PATH/benchmarks-attitude-smartphones/src/
loadProject;

Create a new benchmark instance. Load sensors noises, calibrations and datasets. Then start the benchmark process:

benchmark = AttitudeBenchmarks;
benchmark.load;
benchmark.process;

The benchmark process takes a while and memory if you compute all datasets with all algorithms, all sampling, all calibrations... (e.g. 26 hours on a macbook pro and 25 Go). In order to avoid to restart the full process each time, you can save/open the benchmark:

save(AttitudeBenchmarks.path, 'benchmark', '-v7.3'); % current state is saved in ./datasets/saved/ (default path)
load(AttitudeBenchmarks.path);

Results are stored in AttitudeBenchmarkResults class and aggregated data on means can be computed using compare function

results = benchmark.results;
results.compare('calibration');
results.compare('motions');
results.compare('motionsmag');
results.compare('mag');
results.compare('devices');
results.compare('sampling');
results.compare('processingTime');

Some stats on datasets can be computed:

benchmark.stats;

License

This project is under the CeCILL license.

Authors

Thibaud Michel
[email protected]

Hassen Fourati
Pierre Genevès
Nabil Layaïda

Tyrex Team, LIG, Inria (France), 2016
NEcS Team, Gipsa-Lab, Inria (France), 2016

benchmarks-attitude-smartphones's People

Contributors

thibaudm 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

Watchers

 avatar  avatar  avatar  avatar  avatar

benchmarks-attitude-smartphones's Issues

Calibration setup and procedure used to calibrate accelerometer

Hello,

I have been using the accelerometer calibration algorithm findAccelerometerCalibrationByKumar from this project to try and calibrate the accelerometer in the IMU I'm using. I'm doing the minimum required 9 positions with the use of a dodecahedron. See the attached image. The IMU will reside in the shape and by placing the dodecahedron on different sides and keeping it as motionless as possible, one of the required positions is acquired. Rince and repeat at least 9 times.

The problem I am encountering is that the results of the calibration are always bad. I have analysed the calibration files used in this project and copied the pattern I could see in the 9x3 calibration matrix. To no results unfortunately. I have verified that my data is correct and I have verified that the algorithm is working by feeding it calibration data from this project. Obviously I am doing something wrong, but I am having a hard time figuring out what I am doing wrong.

My question is what kind of calibration setup was used for the smartphones in the project to be able to obtain the calibration results? Frosio's paper mentions that random positions can be used, but from my experience as well as from the research I'v done on others using Frosio's algorithm, I have gathered that not all positions result in a solution. Did the calibration of the accelerometer in the smartphones have some kind of procedure utilizing the calibration setup resulting in consistent solutions across all the smartphone's IMUs during every calibration?

An example of my data. The 10x3 matrix I fed to the findAccelerometerCalibrationByKumar function. All of the data is in m/s^2.

  -0.2451259  -6.9371696  -6.6317955
  -0.2857638   6.9482451   7.086829 
  -7.0783234   0.1476433   6.8704422
  -0.026195    0.1517821  -9.4815092
  -0.1702154   0.2877862   9.6325266
  -0.325696   -6.5539241   7.1842451
  -0.2655272   6.576859   -6.7413335
  -0.4239417   9.9058435  -0.2867784
  -0.349081   -9.0924694   0.2780034
  -6.7616994   6.656745   -0.0232414

The results. As you can see the bias is far too large and the scale matrix is far from 1.

  B =
       -4.8261817   8.0330201   11.977169

  M =
        0.2487351   0.0207804   0.0242135
        0.0207804   0.056975   -0.005968 
        0.0242135  -0.005968    0.046166 

IMG_20211102_141150059
.

MichelEkfF and MichelObsF calculation results are inconsistent with the paper

Dear Tyrex,

Recently,I download the source code from here, after running the code, what confuses me is some MichelEkfF and MichelObsF calculation results are inconsistent with the paper.

For instance , in "On Attitude Estimation with Smartphones" VII.A Importance of Calibration
MichelEkfF( paper) 82.0° 20.1° 20.1° 6.9° 7.0° 18.2°
MichelEkfF( mine) 82.0° 51.8° 51.7° 20.1° 20.1° 42.6°

MichelObsF( paper) 82.1° 13.6° 13.5° 5.9° 5.9° 15.1°
MichelObsF( mine ) 82.1° 52.3° 52.2° 19.5° 19.3° 42.2°

I run the code by reading the README.md and didn't change anything.

I would be very grateful for your answer.

The function "quatrotate" may should be modified

Dear Tyrex:
Thanks for your excellent job, and I benefited much from your work.
I find you use the function "quatrotate" to calculate the vector in a new coordinate with a quaternion.
I think you should normalize the quaternion , or you shouldn't use 1 to stand for the "qw^2+qx^2+qy^2+qz^2".
image

I feel confused about the Implementation of dcm2quat.

Dear Tyrex:
Thanks for your excellent job, and I benefited much from your work.
But I felt confused about the Implementation of the dcm2quat function.
It seems like that you calculate the respective quaternion of the transpose of the inputting DCM.
I compared your code with the link of reference.
In your code, you calculate the quaternion like this:
image
In your reference, the quaternion is calculated like this:

image
The sequences of the elements in the calculation are different.
Would you please give me some advice?
Thank you.

C# implementation in cross platform Xamarin app

Hello!

I am looking to use these set of filters and algorithms to improve the overall accuracy of my navigation app - after having read Attitude Estimation for Indoor Navigation and Augmented Reality with Smartphones. The app currently takes os calibrated acc, gyro and mag readings into madgwick and uses the attitude quaternion that is returned.

Here is a screen recording of the app in i'ts current state.

There is some inaccuracies when indoors, certain areas outside and near house walls - which I believe is caused by magnet perturbations. I have measured the µT and found these to rise or fall in this places. However given from the small discussion at xioTechnologies/Fusion#8 - I learned that all perturbations are not reflected in the µT.

I was hoping I could try the magnetometer calibration with Barz and one of the MichelObs sensor fusion algorithms


My problem right now is I have no knowledge of matlab and also have very little math knowledge - so it is very hard to translate. It also seems difficult to use Matlab code in another languages (C# in this case) - It requires MATLAB Coder

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.