You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting the following error when using roslaunch orb_slam3_ros_wrapper euroc_mono.launch
[ WARN] [1670076780.160426745]: TF_OLD_DATA ignoring data from the past (Possible reasons are listed at http://wiki.ros.org/tf/Errors%20explained) for frame camera at time 0.000000 according to authority unknown_publisher
Warning: TF_OLD_DATA ignoring data from the past (Possible reasons are listed at http://wiki.ros.org/tf/Errors%20explained) for frame camera at time 0.000000 according to authority unknown_publisher
at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.6/src/buffer_core.cpp
terminate called after throwing an instance of 'cv::Exception'
what(): OpenCV(4.6.0-dev) ../modules/highgui/src/window.cpp:376: error: (-215:Assertion failed) size.width>0 && size.height>0 in function 'imshow'
[orb_slam3_mono-1] process has died [pid 59511, exit code -6, cmd /home/ubuntu/catkin_ws/devel/lib/orb_slam3_ros_wrapper/orb_slam3_ros_wrapper_mono __name:=orb_slam3_mono __log:=/home/ubuntu/.ros/log/e093e46c-7305-11ed-8581-558ecd5b9b83/orb_slam3_mono-1.log].
log file: /home/ubuntu/.ros/log/e093e46c-7305-11ed-8581-558ecd5b9b83/orb_slam3_mono-1*.log
RVIZ shows up and I can see my video feed. I'm also able to see the SLAM working for just one frame before the ORB-SLAM crashes and RVIZ is left behind.
The log seems not be available...
The text was updated successfully, but these errors were encountered:
I also have the same issue. i checked out you link and looked for cv.VideoCapture(0) line in all files with grep, found nothing meaningful. Do you have any other ideas?
I'm getting the following error when using
roslaunch orb_slam3_ros_wrapper euroc_mono.launch
RVIZ shows up and I can see my video feed. I'm also able to see the SLAM working for just one frame before the ORB-SLAM crashes and RVIZ is left behind.
The log seems not be available...
The text was updated successfully, but these errors were encountered: