<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Wrong Coriolis Force]]></title><description><![CDATA[<p>Can someone explain line 410 of <a href="http://pathgen.py" rel="nofollow">pathgen.py</a> ? This is where the accelerometer output is generated, and it reads:</p>
<pre><code>acc = vel_dot_b + attitude.cross3(w_ie_b+gyro, vel_b) - c_nb.T.dot(gravity)
</code></pre>
<p>The second term here appears to be the coriolis force, except it's missing a pre-factor of 2 (see: <a href="https://en.wikipedia.org/wiki/Coriolis_force" rel="nofollow">Coriolis Force</a>). More importantly, why is the gyro angular rate (<code>gyro</code>) being added to the earth's rotation (<code>w_ie_b</code>)? The rotation of the IMU does not generate a coriolis force since the IMU is at the origin of the body frame and therefore locally at rest (by definition). Finally, there doesn't appear to be a <a href="https://en.wikipedia.org/wiki/Centrifugal_force" rel="nofollow">centrifugal force</a> term due to the Earth's rotation in this equation, but that could be incorporated into the vector <code>gravity</code>, it's not clear. I noticed these issues because I was getting correct position and angular rate data but incorrect accelerometer data for high-speed trajectories.</p>
]]></description><link>https://forum.aceinna.com//topic/364/wrong-coriolis-force</link><generator>RSS for Node</generator><lastBuildDate>Sun, 19 Apr 2026 21:04:16 GMT</lastBuildDate><atom:link href="https://forum.aceinna.com//topic/364.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 27 Oct 2022 20:16:25 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Wrong Coriolis Force on Thu, 27 Oct 2022 20:16:25 GMT]]></title><description><![CDATA[<p>Can someone explain line 410 of <a href="http://pathgen.py" rel="nofollow">pathgen.py</a> ? This is where the accelerometer output is generated, and it reads:</p>
<pre><code>acc = vel_dot_b + attitude.cross3(w_ie_b+gyro, vel_b) - c_nb.T.dot(gravity)
</code></pre>
<p>The second term here appears to be the coriolis force, except it's missing a pre-factor of 2 (see: <a href="https://en.wikipedia.org/wiki/Coriolis_force" rel="nofollow">Coriolis Force</a>). More importantly, why is the gyro angular rate (<code>gyro</code>) being added to the earth's rotation (<code>w_ie_b</code>)? The rotation of the IMU does not generate a coriolis force since the IMU is at the origin of the body frame and therefore locally at rest (by definition). Finally, there doesn't appear to be a <a href="https://en.wikipedia.org/wiki/Centrifugal_force" rel="nofollow">centrifugal force</a> term due to the Earth's rotation in this equation, but that could be incorporated into the vector <code>gravity</code>, it's not clear. I noticed these issues because I was getting correct position and angular rate data but incorrect accelerometer data for high-speed trajectories.</p>
]]></description><link>https://forum.aceinna.com//post/1470</link><guid isPermaLink="true">https://forum.aceinna.com//post/1470</guid><dc:creator><![CDATA[KRResCon]]></dc:creator><pubDate>Thu, 27 Oct 2022 20:16:25 GMT</pubDate></item></channel></rss>