berndpfrommer / basalt_ros1

ROS1 wrapper for basalt VIO
30 stars 11 forks source link

image frame 1672371570248219967 dropped due to queue overflow #11

Closed ZhangLiang-Cencen closed 1 year ago

ZhangLiang-Cencen commented 1 year ago

hello, when I run "roslaunch realsense2_camera rs_t265.launch" and roslaunch basalt_ros1 vio_t265.launch, the screen printed "image frame 1672371570248219967 dropped due to queue overflow"

what can I do to solve this problem?

Thanks!

ZhangLiang-Cencen commented 1 year ago

ubuntu 18 dose not have this problem.

ZhangLiang-Cencen commented 1 year ago

The method<arg name="enable_sync" default="true"/> does not work in ubuntu 20

berndpfrommer commented 1 year ago

queue overflow is often due to slow CPU. Regarding the option "enable_sync": What launch file are you referring to?

ZhangLiang-Cencen commented 1 year ago

queue overflow is often due to slow CPU. Regarding the option "enable_sync": What launch file are you referring to?

rs_t265.launch

ZhangLiang-Cencen commented 1 year ago

Could you please tell me how to solve the problem of slow CPU?

berndpfrommer commented 1 year ago

I cannot find the "rs_t265.launch" file in the source tree. Could you please provide a link to it? About the slow CPU problem: first find out if it even is due to high CPU load. Run "top" while you are getting the error messages and see what processes are consuming the most CPU cycles.

ZhangLiang-Cencen commented 1 year ago

Thanks for your help! If you run the following code, you will find the "rs_t265.launch".

mkdir -p ~/realsense_ws/src

cd ~/realsense_ws/src/

git clone https://github.com/IntelRealSense/realsense-ros.git

cd realsense-ros/

git checkout `git tag | sort -V | grep -P "^2.\d+\.\d+" | tail -1` //检查分支是否为最新
ZhangLiang-Cencen commented 1 year ago

I also want to ask another question. When I run this algorithm outdoor, the position_z was inaccurate. Screenshot from 2023-01-06 12-55-52

berndpfrommer commented 1 year ago

Please understand that I cannot provide support for the realsense t265 as I don't own such a device. As for your last question about z-axis inaccuracy: you are giving me no context at all, which makes it impossible to provide any reasonable response.