无法使用 ADF 原点改进点云的姿态 [英] Fail to improve pose of point cloud with ADF origin

查看:51
本文介绍了无法使用 ADF 原点改进点云的姿态的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我将场景的点云及其四元数保存在 pcl 文件中.

首先,我只使用姿势 w.r.t 来启动设备(参见第二张图片)来获取四元数.我发现了一个漂移问题,我在

解决方案

您应该设置姿势回调,以便仅返回与 ADF 基础相关的姿势 - 不应返回与服务开始相关的姿势 - 漂移将不会消失,但它会变得最小并会自动更正 - ADF 需要经过良好的训练以保持姿势返回率.

I save the point clouds of a scene and its quaternion in a pcl file.

First, I've only used pose w.r.t to device start (see second image) to get the quaternion. I've discovered a drifting problem which I mentioned here.

  1. Therefore, I learned the scene with area learning (see first image) by walking around the table.
  2. After that, I'm loading the area description file (ADF) to overcome the drifting. I wait for the first loop closure/localization in the onPoseAvailable callback.
  3. Then in the onXyzIjAvailable callback I use its timestamp to get a valid pose w.r.t to the ADF origin (baseFrame = COORDINATE_FRAME_AREA_DESCRIPTION and targetFrame = COORDINATE_FRAME_DEVICE).
  4. And I save the poseAtTime(xyzIj.timestamp) and the xyzIj in a *.PCD file.

But, the drifting seems to get even worse (see third image). It's better oriented to the origin, but the point clouds aren't that close as in the image without adf.

Do I something wrong?

Is there any way to improve this?

解决方案

You should set up the pose callback such that only poses with respect to ADF base are returned - poses with respect to start of service should not be returned - drift will not go away, but it will become minimal and will autocorrect - the ADF needs to be well trained to keep up the pose return rate.

这篇关于无法使用 ADF 原点改进点云的姿态的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆