Skip to content
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

Azure Kinect DK NotEnoughSpatialData #29

Open
JaVo93 opened this issue Jul 18, 2022 · 3 comments
Open

Azure Kinect DK NotEnoughSpatialData #29

JaVo93 opened this issue Jul 18, 2022 · 3 comments

Comments

@JaVo93
Copy link

JaVo93 commented Jul 18, 2022

hi,

I have a question: Someone got ASA and ROS running with the Azure Kinect DK?

I run Azure Kinect DK on Ubuntu 20.04 and ROS noetic. I'm using the SLAM RTA b map to get the position of the camera: https://github.com/microsoft/Azure_Kinect_ROS_Driver/blob/melodic/launch/slam_rtabmap.launch

Further I use image proc http://wiki.ros.org/image_proc to get the undistorted grayscale images.

When I run ASA ROS I got the error "NotEnoughSpatialData" based on the live Azure Kinect DK rostopics. I receive frames that is also confirmed by the statement "Add frames". The demo with the rosbags works well.

Did I miss something? Any advice would be great.

@159chenJie159
Copy link

159chenJie159 commented Sep 22, 2022

Did you fix the error, I also encountered this error using Realense's D435 camera, D435 has no imu.And I also used image proc to get the undistorted grayscale images. I don't know exactly how this problem came about, whether it was my setting up wrong "world_frame_id" or "camera_frame_id".

@EricVoll
Copy link
Contributor

Hi @JaVo93
Not enough spatial data is an error that usually is returned when the device hasn't uploaded enough data yet: link

So the solution should be relatively easy - just collect more view points before attempting to create an anchor. Does that solve the problem?

@soeroesg
Copy link

one reason can be that the ASA library cannot look up the poses of the images in the TF because the timestamps of the images and poses are different. check that the timestamps of the images and the corresponding poses are the same (or very close to each other) and try to increase tf_lookup_timeout in the launchfile

Also check the same with the camera_info, and try passing use_approx_sync_policy:=true

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants