-
Notifications
You must be signed in to change notification settings - Fork 433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accelerometer aiding #86
Comments
@nplayle , Orientation + Accel: The only assumption we have in the framework is that the frame of reference of PTAM is roughly gravity aligned. (Usually this can be made sure by initializing ptam s.t. the control grid is horizontal). If the ptam frame of reference is not gravity aligned the estimator will estimate this rotation (world-to-vision transformation) and compensate for it. Of course this is only meaningful if the initial guess is not more than 10-20 degrees off. The first thing I would verify is the imu to camera transformation. We expect you to set this in the parameter file. Here you have to provide the position and orientation of the camera frame of reference w.r.t. the imu frame of reference expressed in the imu frame of ref. GNSS The global yaw is only observable if you translate in a direction orthogonal to the direction of gravity. The roll and pitch are observable. We usually set the yaw to a reasonable guess at the beginning which we take from a compass. pressure sensor The units are expressed as metric height above a reference point which is stored at the filter initialization time. Simon |
Assuming this is clarified. |
Hi,
I'm currently using MSF with ETHZ PTAM in a masters project and have a few questions.
Are the accelerometers used in the determination of pitch and roll?
I believe my inaccurate angle estimates from PTAM might be incorrectly estimating accelerometer and gyro biases causing me to read incorrect velocity estimates if I pitch / roll my setup.
What corrects the orientation estimate in the case of GNSS only?
What units is the pressure input?
Thanks!
Nick
The text was updated successfully, but these errors were encountered: