-
Notifications
You must be signed in to change notification settings - Fork 119
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
Layer rgb not found, adding it to the semantic map #86
Comments
Oh, this might be the input image issue. |
subscribers:
|
[ INFO] [1709173219.924276172]: Subscribed to Image topic: /camera/color/image_raw, Camera info topic: /camera/color/camera_info. Channel info topic: Not found. Using channels: rgb As above, terminal outputs all information. |
RUN image_topic: /zed2i/zed_node/left/image_rect_color --------------End of Parameters----------------------- |
Oh so it does happen with the turtlesim example? Have you tried with docker already? |
Thank you for your reply. The main reason is that there is no detailed error message and I don’t know how to fix it. I am currently trying to run it under docker. |
I only positioned the channel input in this function to only have rgb.
Furthermore, I'm not sure if my parameters are misconfigured: |
Thanks for sharing the details. If it is a color image, you can leave it, or add ["rgb"] as the channel name. |
[ INFO] [1709118694.042549165]: [ElevationMappingCupy] finish initialization
Layer rgb not found, adding it to the semantic map
[elevation_mapping-1] process has died [pid 237549, exit code -11, cmd
/emcu_ws/devel/lib/elevation_mapping_cupy/elevation_mapping_node __name:=elevation_mapping __log:=/.ros/log/96750bb0-d626-11ee-a708-5f7e327b3b63/elevation_mapping-1.log].log file: ~/.ros/log/96750bb0-d626-11ee-a708-5f7e327b3b63/elevation_mapping-1*.log
all processes on machine have died, roslaunch will exit
After print ‘Layer rgb not found, adding it to the semantic map’ , all processes on machine have died.
Can you help me to solve this question? thanks!
The text was updated successfully, but these errors were encountered: