<html><head><title>MRPT.ORG RSS update</title></head><body><b>New entry:</b> Â I will have to subclass the<br>
<b>Original item:</b> <a href="http://www.mrpt.org/node/1520#comment-697">http://www.mrpt.org/node/1520#comment-697</a><br>
<b>NOTE:</b> Do NOT answer to this mail, generated automatically from this <a href="http://www.mrpt.org/crss">RSS feed</a>. To reply, please visit the <a href="http://www.mrpt.org/node/1520#comment-697">original source</a>.<br><hr><br><p>In reply to <a href="http://www.mrpt.org/node/1520">Chr-UM6 IMU
<blockquote><p> I will have to subclass the
CObservationIMU class for the UM6 since it's a 9DoF and provides an
attitude solution as well as filter accelerometer and gyro data.
All or some of which would be needed by users of this new driver.
As I contemplate doing this I may ask for more
<p>Anyway, consider the
possibility of extending the lenght of the possible measurement vectors
in CObservationIMU to hold any extra data fields instead of subclassing,
mostly thinking of transparently getting backward compatibility with all
programs that worked with CObservationIMU. I mean, adding new data
fields after the 15 currently existing: IMU_X_ACC, ...,
<p>If you feel confident to making commits, just <a
me</a> with a gmail address and will give you write permisions to