You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+21-1Lines changed: 21 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,6 +63,7 @@ dependencies {
63
63
-[x] Implement some route visualizer for desktop application
64
64
-[x] Implement Kalman filter and test all settings
65
65
-[x] Implement noise generator for logged data
66
+
-[ ] Improve UI. Need to use some controls for coefficient/noise changes
66
67
67
68
### Filter
68
69
@@ -82,7 +83,26 @@ dependencies {
82
83
### Library
83
84
84
85
-[x] Separate test android application and library
85
-
-[ ] Add library to maven repository
86
+
-[x] Add library to some public repository
87
+
88
+
## Theory
89
+
90
+
Kalman filtering, also known as linear quadratic estimation (LQE), is an algorithm that uses a series of measurements observed over time, containing statistical noise and other inaccuracies, and produces estimates of unknown variables that tend to be more accurate than those based on a single measurement alone, by estimating a joint probability distribution over the variables for each timeframe.
91
+
92
+
You can get more details about the filter [here](https://en.wikipedia.org/wiki/Kalman_filter).
93
+
94
+
The filter is a de-facto standard solution in navigation systems. The project simply defines the given data and implements some math.
95
+
96
+
The project uses 2 data sources: GPS and accelerometer. GPS coordinates are not very accurate, but each of them doesn't depend on previous values. So, there is no accumulation error in this case. On the other hand, the accelerometer has very accurate GPS readings, but it accumulates error related to noise and integration error. Therefore, it is necessary to "fuse" these two sources. Kalman is the best solution here.
97
+
98
+
So first - we need to define matrices and do some math with them. And second - we need to get real acceleration (not in device orientation) . First one is described in current project's wiki. But second one is little bit more complex thing called "sensor fusion". There is a lot information about this in internet. For real acceleration we need to know 2 things : device orientation and "linear acceleration". Linear acceleration is acceleration along each device axis excluding force of gravity. It could be calculated by high pass filter or with more complex algorithms. Device orientation could be calculated in many ways :
99
+
100
+
- Using accelerometer + magnetometer
101
+
- Using accelerometer + magnetometer + gyroscope
102
+
- Using [Madgwick filter](http://x-io.co.uk/open-source-imu-and-ahrs-algorithms/)
103
+
- Using virtual "rotation vector" sensor.
104
+
105
+
Best results show madgwick and rotation vector sensor, but Madgwick filter should be used when we know sensor frequency. Android doesn't provide such information, so best solution here is to use virtual rotation vector sensor. You can get more details from current project's wiki.
0 commit comments