-
Notifications
You must be signed in to change notification settings - Fork 43
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
It seems that the dvs_tracking cannot work? #11
Comments
Could you show all terminal information logs:) |
Hello, I have the same problem. Have you solved it now? ================================================================================REQUIRED process [dvs_tracking-7] has died!
|
I had the same issue with opencv4.5, I downgraded to 4.2. Helped for me in this case, but the program still dies halfway during the rosbags (examples), see open Issue |
I think this program can not work at all. |
@lienharj @KwanWaiPang I downgraded opencv to 3.2.0 started roslaunch server http://172.18.20.20:37191/ SUMMARYCLEAR PARAMETERS
PARAMETERS
NODES auto-starting new master setting /run_id to c5d96ea4-3bb0-11ec-bce8-2cf05d6ca09d |
@zebrajiahao |
It looks like no data has been read. And if you have wechat, we can discuss it(same name as account). |
Yes, you can add my WeChat through: scxspingit,Thanks~ |
@xixixixiangxianguestc hello, i have the same issue. Have you solved it? |
I also have the same error. @xixixixiangxianguestc @youngOS1998 |
no matter which launch file, after running, it will appear error:
================================================================================REQUIRED process [dvs_tracking-7] has died!
process has died [pid 4972, exit code -11, cmd /home/kwanwaipang/catkin_ws_dvs/devel/lib/dvs_tracking/dvs_tracking_ros events:=/dvs/events remote_key:=/evo/remote_key pointcloud:=dvs_mapping/pointcloud __name:=dvs_tracking __log:=/home/kwanwaipang/.ros/log/b690b020-19d6-11ec-bb55-4074e020cd12/dvs_tracking-7.log].
log file: /home/kwanwaipang/.ros/log/b690b020-19d6-11ec-bb55-4074e020cd12/dvs_tracking-7*.log
Initiating shutdown!
The text was updated successfully, but these errors were encountered: