clarification on Rust rewrite of position estimation
This commit is contained in:
parent
734197be1c
commit
c7adc7f67a
@ -589,7 +589,7 @@
|
||||
<p>Changes since the 2025032100 release:</p>
|
||||
|
||||
<ul>
|
||||
<li>Network Location: rewrite position estimation in Rust with a new algorithm based on Expectation-Maximization (EM) always using 3D (altitude) to provide much better accuracy, robustness and performance (this new 3D implementation performs better than the previous implementation in the 2D mode we were stuck using due to 3D being far too CPU intensive)</li>
|
||||
<li>Network Location: rewrite position estimation in Rust (from Kotlin) with a new algorithm based on Expectation-Maximization (EM) always using 3D (altitude) to provide much better accuracy, robustness and performance (this new 3D implementation performs better than the previous implementation in the 2D mode we were stuck using due to 3D being far too CPU intensive)</li>
|
||||
<li>Network Location: improve RSSI-based (signal strength) distance estimation including tuning it separately for 2.4GHz vs. 5GHz/6GHz and take distance variance into account for position estimation (Wi-Fi Round-Trip-Time support will be added in the future for Access Points supporting it)</li>
|
||||
<li>Network Location: add support for 6GHz Wi-Fi networks via Reduced Neighbor Report (RNR)</li>
|
||||
<li>Network Location: increase the number of closest APs we explicitly request data for from 5 to 15</li>
|
||||
|
Loading…
x
Reference in New Issue
Block a user