Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

libviso2 works perfectly fine when used with correct parameters. The problem you're seeing is probably caused by your initial transformation being different from the initial camera pose in the KIT dataset. As far as I remember the KIT camera is slightly facing downwards, hence the camera is recording a constant upward motion (relative to the camera) so when your initial camera position is facing forward instead of slightly downward like the KIT camera your odometry will end up going upwards. The calculated odometry is still correct but just rotated by the initial offset between your camera and the dataset's camera.

You can look up the sensor calibration on KIT's dataset website.