FLVIS: Attempt to initialize an empty graph Segmentation fault (core dumped)

First of all, thank you for sharing this work. I am evaluating different VSLAM for my research and I encounter the following error:

tracking: 48|50|113
tracking: 67|67|85
tracking: 61|63|82
tracking: 60|63|79
tracking: 58|60|79
tracking: 58|59|76
tracking: 65|86|95
tracking: 62|95|107
tracking: 66|66|66
tracking: 64|65|65
tracking: 62|63|63
tracking: 61|63|63
tracking: 62|63|63
tracking: 60|62|63
tracking: 53|62|67
tracking: 51|121|136
tracking: 42|139|151
virtual bool g2o::SparseOptimizer::initializeOptimization(g2o::HyperGraph::VertexSet&, int): Attempt to initialize an empty graph
/opt/ros/kinetic/lib/nodelet/nodelet: line 1:  7929 Segmentation fault      (core dumped) $0 $@
[flvis_nodelet_manager-3] process has died [pid 7927, exit code 139, cmd bash -c sleep 0; $0 $@ /opt/ros/kinetic/lib/nodelet/nodelet manager __name:=flvis_nodelet_manager __log:=/home/fabrice/.ros/log/bd569f54-0f88-11eb-9699-88b1116f3669/flvis_nodelet_manager-3.log].
log file: /home/fabrice/.ros/log/bd569f54-0f88-11eb-9699-88b1116f3669/flvis_nodelet_manager-3*.log
[ INFO] [1602836582.269961107]: Bond broken, exiting
[ INFO] [1602836582.366583719]: Bond broken, exiting
[ INFO] [1602836582.374452665]: Bond broken, exiting
[LoopClosingNodeletClass_loader-6] process has finished cleanly
log file: /home/fabrice/.ros/log/bd569f54-0f88-11eb-9699-88b1116f3669/Loo
pClosingNodeletClass_loader-6*.log
[TrackingNodeletClass_loader-4] process has finished cleanly

flvis

Do you have any idea why it happens? Or where do I have to dig to understand what is going on?

I am running FLVIS on ubuntu 16.04

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 29

Most upvoted comments

Oh great ! I will have a look, can you tell (if you remember) which parameters did you edit? Otherwise I will check on px webpages

From your experience, the Pixhawk IMU is more accurate than the D435i one?

You can follow this link->https://github.com/mavlink/mavros/issues/1346 Yes, I believe so. And another reason to use the FCU’s IMU is that you can directly feed the imu pose to the FCU(through /mavros/vision_pose/pose) You need to calibrate the extrinsic parameter using Kalibr

Ttoto on Nov 6, 2020