noetic process has died

[Panda12580]

Hello, may I ask why when I run single,launch file, call rqt to see the result will kill the process? I have checked the set parameters and there is no error. I ask for your help, thank you.

[saikishor]

Hello @Panda12580!

It is indeed weird that setting parameters through service works but not through the rqt reconfigure, at the end of the day, they are doing the same. We cannot see the screenshot you have attached. Could you reattach it?

Thank you

[Panda12580]

@saikishor Thank you for your reply. I have updated and uploaded the picture. Please check where my mistake is.

[Panda12580]

I set up the single.launch file and then start rs_camera.launch, but I want to see images via rqt and subscribed to aruco_ros/result ,
the background process will be killed as soon as I do this.

[saikishor]

@Panda12580 I don't see the relation between rqt image viewer and the point you said about setting parameters through the command line. They are completely different.

What I recommend is to try to subscribe to the topic in the command line and see what would happen. This part is something that is tested, so I expect it to work without issues.

Thank you,

Best Regards,
PAL Robotics Team

[Oscar-qi]

@saikishor Hello, I have been using the aruco-ros package recently on the Ubuntu 20.04 system. When I run the following command:

bash
rosrun image_view image_view image:=/aruco_single/result
the single.launch node dies.

[saikishor]

Can you let us know what happens if you subscribe through command line?

[Oscar-qi]

Can you let us know what happens if you subscribe through command line?

I opened three terminals and ran the driver node for the d435 camera, the single_realsense node for aruco_ros, and subscribed to aruco_single/result using the command line。

The terminal display for subscribing to aruco_single/result using the command line reads:
rosrun image_view image_viewer image:=/aruco_single/result
[INFO] 【1713951282.914114320]: Inttlaltzing nodelet wtth 4 worker threads.
[INFO][1713951283.689522413]: Using transport "raw"

When I subscribe to the aruco_single/result topic, it shows the following in the terminal of aruco_ros:

NODES
aruco_single (aruco_ros/stngle)
ROS_MASTER_URI=http://Localhost:11311
process[aruco_stngle-1]:started with pid[80918]
[ WARN] [1713951115.318433478]:Corner refinenent opttons have been removed in Aruco 3.0.0, corner_refinenent ROS paraneter ts deprecated
[ WARN] [1713951116.014256637]: normaltzeImagerllumtnatton is untnplemented!
[aruco single-1] process has dled [pid 80918, extt code -l1, cmd /home/rm/catkin _ws/devel/lib/aruco_ros/single /camera_info:=/camera/color/canera_info /image:=/camera/color/image_raw __name:=aruco_single __log:=/home/rm/.ros/log/451bc2ea-021d-11ef-8aea-48b02d15ce9b/aruco single-1.log].
log file：/home/rm/.ros/log/451bc2ea-021d-11ef-Baea-48bo2d15ce9b/aruco single-1*
.1og
all processes on machine have died, roslaunch will exit shuttting down processing monitor...
... shutting down processing monitor complete
done

[chenglei11]

hi I ran into the same problem with you, have you solved it? could you please tell me how to solve this one? you can reply me in Chinese as well

[Panda12580]

@chenglei11 I was able to implement it on another noetic version of the computer, but the code used was previous, that is, I'm not sure whether the author of the package changed the code to cause the conflict or the computer environment itself, so I guess if I can use the earlier version of the noetic package to try it?

[Panda12580]

@saikishor I'm sorry for not replying in time. I mean, when I select the topic result from the view-image option in the rqt visual interface, the program running single.launch will be killed, which means that we need to subscribe to the topic result when we recognize the QR code. No matter what the situation is, once we subscribe to the topic, The program will be killed.

[chenglei11]

@chenglei11 I was able to implement it on another noetic version of the computer, but the code used was previous, that is, I'm not sure whether the author of the package changed the code to cause the conflict or the computer environment itself, so I guess if I can use the earlier version of the noetic package to try it?

yeah i can also implement it on another computer, have you tried this method? did it work?

[BUAAPY]

@chenglei11 I was able to implement it on another noetic version of the computer, but the code used was previous, that is, I'm not sure whether the author of the package changed the code to cause the conflict or the computer environment itself, so I guess if I can use the earlier version of the noetic package to try it?

Hey, I've met the same problem. Have you solved the problem? which version have you tried?

[Panda12580]

@BUAAPY I'm using the noetic branch, and the code I'm using is from earlier, on my other computer. Unfortunately, my rough review of the new code is not very different from the current one. So I'm not sure what the problem is, the environment configuration problem is very likely.

[LuShuaiqi-Geo]

I encountered the same problem. My image acquisition operations were the same as the author's. I also used neotic. But the difference is that after I tried to get the image, it did not kill aruco_single, but got stuck. It could not get the image and did not kill the process. I feel very strange and hope there is a solution to this problem

[BUAAPY]

I've tried to print messages during the running process and the program has stucked before an opencv function (the resize function). However, the program runs smoothly in another noetic environment. The only difference is the version of opencv (4.5.4  in the stucked one, 4.2.0 the other one).  According to other blogs the ROS noetic uses its default opencv (4.2.0), especially its cv_bridge package. The aruco_ros uses my installed opencv (4.5.4) automatically during the cmake process, though the minimum version is set to 4.2.0 in the cmake file. I dont know if this is the issue and how to fix it. Maybe uninstalling the latest opencv and using the default one o noetic may help.

…

---Original--- From: "Lu ***@***.***> Date: Tue, Nov 12, 2024 17:01 PM To: ***@***.***>; Cc: ***@***.******@***.***>; Subject: Re: [pal-robotics/aruco_ros] noetic process has died (Issue #133) I encountered the same problem. My image acquisition operations were the same as the author's. I also used neotic. But the difference is that after I tried to get the image, it did not kill aruco_single, but got stuck. It could not get the image and did not kill the process. I feel very strange and hope there is a solution to this problem — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[saikishor]

Exactly, that should be the issue