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

RViz2: TF OLD DATA Error #5

Open
jkcolem opened this issue Feb 7, 2024 · 8 comments
Open

RViz2: TF OLD DATA Error #5

jkcolem opened this issue Feb 7, 2024 · 8 comments
Assignees
Labels
verify to close Waiting on confirm issue is resolved

Comments

@jkcolem
Copy link

jkcolem commented Feb 7, 2024

Hello @hemalshahNV and @jaiveersinghNV ,

I'm currently having a issue with running the freespace segmentation. Whenever I run this line of code:

featnet_engine_file_path:=/tmp/models/bi3d/bi3dnet_featnet.plan \
segnet_engine_file_path:=/tmp/models/bi3d/bi3dnet_segnet.plan \
max_disparity_values:=32 

I get the following error from RViz2:

Screenshot from 2024-02-07 16-35-50

When I was working on this a month ago, I was able to get the whole freespace segmentation pipeline to work.

@hemalshahNV
Copy link
Contributor

Could you show more of the log before this point? The process for the freespace container died right at the beginning of this output so curious what took that out. The rest of the log seems expected after the freespace node died.

@hemalshahNV hemalshahNV self-assigned this Feb 7, 2024
@hemalshahNV hemalshahNV added the needs info Needs more information label Feb 7, 2024
@jkcolem
Copy link
Author

jkcolem commented Feb 8, 2024

Hello @hemalshahNV ,

This is the entire log of the error:

Screenshot from 2024-02-08 14-15-53

@hemalshahNV
Copy link
Contributor

Thanks! The log indicates that isaac_ros_image_proc package (in the Isaac ROS Image Pipeline repository) and isaac_ros_bi3d package (in the Isaac ROS Depth Segmentation repository) do not seem to be built in your ROS workspace and sourced into your environment. Could you confirm that these are available? Freespace segmentation relies on both of them.

@hemalshahNV hemalshahNV added verify to close Waiting on confirm issue is resolved and removed needs info Needs more information labels Feb 8, 2024
@jkcolem
Copy link
Author

jkcolem commented Feb 9, 2024

Hello @hemalshahNV ,

So I try sudo apt-get install -y ros-humble-isaac-ros-bi3d-freespace in the docker container and a few new things were install in the container. Then I follow all the steps where I open the second terminal in the docker container and everything builds successfully. This shown by the following images:

Screenshot from 2024-02-09 08-37-13

Screenshot from 2024-02-09 08-42-37

Next I run the freespace segmentation of the code, then I ran into new errors which is shown in the following images:

Screenshot from 2024-02-09 13-03-46

Screenshot from 2024-02-09 12-54-03

Screenshot from 2024-02-09 12-54-14

Screenshot from 2024-02-09 12-54-27

Screenshot from 2024-02-09 12-54-36

Then I looked at the rqt_graph to see which ROS2 nodes where communicating with each other and this image is the following results of that:

rosgraph_error

For some reason the nitros node for the images couldn't load in

@jaiveersinghNV
Copy link
Contributor

Hi @jkcolem ,

If you are building your workspace from source, please make sure to source the workspace after building:

source install/setup.bash

This will ensure that the isaac_ros_image_proc package is indexed and discoverable during the ROS launch process.

@jkcolem
Copy link
Author

jkcolem commented Feb 14, 2024

Hello @jaiveersinghNV ,

I have done source install/setup.bash this shown in the first image.

Down below I have cropped the first image to show this:

Screenshot from 2024-02-09 08-37-13-crop

@swapnesh-wani-nvidia
Copy link

Could you try with a clean build? From the rqt image it looks like you are still missing nvidia::isaac_ros::bi3d::Bi3DNode.

@jkcolem
Copy link
Author

jkcolem commented Mar 1, 2024

Hello @swapnesh-wani-nvidia ,

I was able to get the freespace segmentation working again, but not by doing a clean build. I had to source /opt/ros/humble/setup.bash before launching the docker container. Also, I noticed that you must click play in Isaac Sim first before you launch the isaac_ros_bi3d node. I replicate my original error by stopping my simulation in Isaac Sim and letting Rviz2 continue running. . Then I click play to run the simulation, and Rviz2 will output TF old data error. If you launch the isaac_ros_bi3d node first, then you get a gxf error message. This is before you start the simulation in Isaac Sim.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
verify to close Waiting on confirm issue is resolved
Projects
None yet
Development

No branches or pull requests

4 participants