Giter VIP home page Giter VIP logo

limo's Introduction

Limo


CALL FOR HACKATHON: Against all my expectations my work still invokes the interest of many. Since it aged quite a bit now, I would love to organize a Hackathon were people who love to code such as me take part to refurbish this repo. Possible things to do are:

  1. Make a standalone api that works without ros
  2. Make a python api (already started)
  3. Bring repo to C++20 as much as possible (basis is ros indepedant app)
  4. constexpr everything (as much as possible)
  5. ROS2
  6. Remake of the lidar point depth extraction module

But for this I need YOUR HELP! Your reward will be a lot of fun, working together on a project with experienced devs and of course a contribution record (that looks pretty neat in applications ;) ). If you are interested, please contact me per mail or write an issue. If there is more than 2 people plus me, I will organize a date :)


Lidar-Monocular Visual Odometry. This library is designed to be an open platform for visual odometry algortihm development. We focus explicitely on the simple integration of the following key methodologies:

  • Keyframe selection
  • Landmark selection
  • Prior estimation
  • Depth integration from different sensors.
  • Scale integration by groundplane constraint.

The core library keyframe_bundle_adjustment is a backend that should faciliate to swap these modules and easily develop those algorithms.

  • It is supposed to be an add-on module to do temporal inference of the optimization graph in order to smooth the result

  • In order to do that online a windowed approach is used

  • Keyframes are instances in time which are used for the bundle adjustment, one keyframe may have several cameras (and therefore images) associated with it

  • The selection of Keyframes tries to reduce the amount of redundant information while extending the time span covered by the optimization window to reduce drift

  • Methodologies for Keyframe selection:

    • Difference in time
    • Difference in motion
  • We use this library for combining Lidar with monocular vision.

  • Limo2 on KITTI is LIDAR with monocular Visual Odometry, supported with groundplane constraint

  • Video: https://youtu.be/wRemjJBjp64

  • Now we switched from kinetic to melodic

Details

This work was accepted on IROS 2018. See https://arxiv.org/pdf/1807.07524.pdf .

If you refer to this work please cite:

@inproceedings{graeter2018limo,
  title={LIMO: Lidar-Monocular Visual Odometry},
  author={Graeter, Johannes and Wilczynski, Alexander and Lauer, Martin},
  booktitle={2018 IEEE/RSJ International Conference on Intelligent Robots and Systems (IROS)},
  pages={7872--7879},
  year={2018},
  organization={IEEE}
}

Please note that Limo2 differs from the publication. We enhanced the speed a little and added additional groundplane reconstruction for pure monocular visual odometry and a combination of scale from LIDAR and the groundplane (best performing on KITTI). For information on Limo2, please see my dissertation https://books.google.de/books?hl=en&lr=&id=cZW8DwAAQBAJ&oi .

Installation

Docker

To facilitate the development I created a standalone dockerfile.

# This is where you put the rosbags this will be available at /limo_data in the container
mkdir $HOME/limo_data
cd limo/docker
docker-compose build limo
  • You can run the docker and go to the entrypoint with
docker-compose run limo bash

Go to step Run in this tutorial and use tmux for terminals.

  • You can invoke a jupyter notebook with a python interface for limo with
docker-compose up limo

and open the suggested link from the run output in a browser.

Semantic segmentation

The monocular variant expects semantic segmentation of the images. You can produce this for example with my fork from NVIDIA's semantic segmentation:

  1. Clone my fork
git clone https://github.com/johannes-graeter/semantic-segmentation
  1. Download best_kitti.pth as described in the README.md from NVIDIA and put it in the semantic-segmentation folder

  2. I installed via their docker, for which you must be logged in on (and register if necessary) https://ngc.nvidia.com/

  3. Build the container with

docker-compose build semantic-segmentation
  1. Run the segmentation with
docker-copmose run semantic-segmentation

Note that without a GPU this will take some time. With the Nvidia Quadro P2000 on my laptop i took around 6 seconds per image.

Requirements

In any case:

 sudo apt-get install libpng++-dev
  • install ros:
  • install catkin_tools:
sudo apt-get install python-catkin-tools
  • install opencv_apps:
sudo apt-get install ros-melodic-opencv-apps
  • install git:
sudo apt-get install git

Build

  • initiate a catkin workspace:

    cd ${your_catkin_workspace}
    catkin init
  • clone limo into src of workspace:

    mkdir ${your_catkin_workspace}/src
    cd ${your_catkin_workspace}/src
    git clone https://github.com/johannes-graeter/limo.git
  • clone dependencies and build repos

    cd ${your_catkin_workspace}/src/limo
    bash install_repos.sh
  • unittests:

    cd ${your_catkin_workspace}/src/limo
    catkin run_tests --profile limo_release

Run

  • get test data Sequence 04 or Sequence 01. This is a bag file generated from Kitti sequence 04 with added semantic labels.

  • in different terminals (for example with tmux)

    1. roscore
    2. rosbag play 04.bag -r 0.1 --pause --clock
    3. source ${your_catkin_workspace}/devel_limo_release/setup.sh
      roslaunch demo_keyframe_bundle_adjustment_meta kitti_standalone.launch
    4. unpause rosbag (hit space in terminal)
    5. rviz -d ${your_catkin_workspace}/src/demo_keyframe_bundle_adjustment_meta/res/default.rviz
  • watch limo trace the trajectory in rviz :)

  • Before submitting an issue, please have a look at the section Known issues.

Known issues

  • Unittest of LandmarkSelector.voxel fails with libpcl version 1.7.2 or smaller (just 4 landmarks are selected). Since this works with pcl 1.8.1 which is standard for ros melodic, this is ignored. This should lower the performance of the software only by a very small amount.

limo's People

Contributors

fabolhak avatar johannes-graeter avatar longruidong avatar phonght32 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

limo's Issues

Build with Ubuntu 16.04

Hello!
I'm very interested in limo, but I met some question when I tried to build limo. Can I still build limo with Ubuntu 16.04 now?I notice that you may be using ros-melodic now, and when I tried to build, I met so much error with ros-kinetic. Part of them is showing in the picture.
image
image
image
Or could you give me some suggestion to solve them?
Thank you very much!

Parametrs description

Thanks for sharing the code. Do you have a document describing in more detail the parameters used in the code.

roslaunch Error

When I do "roslaunch demo_keyframe_bundle_adjustment_meta kitti_stanalone.launch"
This error shows up. Any ideas?
[kitti_stanalone.launch] is neither a launch file in package [demo_keyframe_bundle_adjustment_meta] nor is [demo_keyframe_bundle_adjustment_meta] a launch file name
The traceback for the exception was written to the log file

A question about the dynamic objects。

Thanks for your excellent work! I want to test limo on my own data. SInce Identifying the dynamic objects by deep learning is a little hard. So I want to know how much influence does the dynamic object have on the accuracy of the track? Have you ever tested it without semantic labels? Great thanks!!

KITTI Ros bags

Hi,

Thank you for sharing your work.
Can you also share other KITTI rosbags that are appropriate for your code?

Thank you

build problems

@thanhphong98 What build problems do you refer to for creating build_limo_release and so on in the limo package? Catkin should build in its workspace which is 2 levels higher.
Anyways it should be able to create those.

/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(node_data.cpp.o)

hi, when i run bash install_repos.sh, teminator display the following error message, it is about yaml-cpp, but i dont know how to fix it
and my system is : ubuntu 16.04, ros-kinetic
ERROR MESSAGE:

Errors     << viso_feature_tracking_ros_tool:make /home/liuzhiyang/limo/logs_limo_release/viso_feature_tracking_ros_tool/build.make.001.log
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(node_data.cpp.o): requires dynamic R_X86_64_32 reloc which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(node_data.cpp.o): requires dynamic R_X86_64_32 reloc which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(node_data.cpp.o): requires dynamic R_X86_64_32 reloc which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(node_data.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_Znwm' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(node_data.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_Znwm' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(node_data.cpp.o): requires dynamic R_X86_64_32 reloc against '__dso_handle' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(node_data.cpp.o): requires dynamic R_X86_64_32 reloc against '__gxx_personality_v0' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(exceptions.cpp.o): requires unsupported dynamic reloc 11; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(memory.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_Znwm' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(memory.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_ZdlPv' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(memory.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_ZdlPv' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(memory.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_ZdlPv' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(memory.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_ZdlPv' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(memory.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_ZdlPv' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(memory.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_ZdlPv' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(memory.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_ZdlPv' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(memory.cpp.o): requires dynamic R_X86_64_32 reloc against '__pthread_key_create' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(memory.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_ZNSt8_Rb_treeIPN4YAML6detail4nodeES3_St9_IdentityIS3_ESt4lessIS3_ESaIS3_EE8_M_eraseEPSt13_Rb_tree_nodeIS3_E' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(memory.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_ZNSt8_Rb_treeIPN4YAML6detail4nodeES3_St9_IdentityIS3_ESt4lessIS3_ESaIS3_EE8_M_eraseEPSt13_Rb_tree_nodeIS3_E' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(memory.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_ZSt18_Rb_tree_decrementPSt18_Rb_tree_node_base' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(memory.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_ZSt18_Rb_tree_decrementPSt18_Rb_tree_node_base' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(memory.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_ZNSt8_Rb_treeISt10shared_ptrIN4YAML6detail4nodeEES4_St9_IdentityIS4_ESt4lessIS4_ESaIS4_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS4_ERKS4_' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(memory.cpp.o): requires dynamic R_X86_64_32 reloc which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(parse.cpp.o): requires dynamic R_X86_64_32 reloc which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(parse.cpp.o): requires dynamic R_X86_64_32 reloc which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(parse.cpp.o): requires dynamic R_X86_64_32 reloc against '__pthread_key_create' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(parse.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_Znwm' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(parse.cpp.o): requires dynamic R_X86_64_32 reloc which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(parser.cpp.o): requires dynamic R_X86_64_32 reloc which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(parser.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_ZN4YAML9Exception10build_whatERKNS_4MarkERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(parser.cpp.o): requires dynamic R_X86_64_PC32 reloc against 'memcmp' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(parser.cpp.o): requires dynamic R_X86_64_PC32 reloc against 'memcmp' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(parser.cpp.o): requires dynamic R_X86_64_PC32 reloc against '_Znwm' which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(parser.cpp.o): requires dynamic R_X86_64_32 reloc which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(parser.cpp.o): requires dynamic R_X86_64_32 reloc which may overflow at runtime; recompile with -fPIC
/usr/bin/ld.gold: error: /usr/local/lib/libyaml-cpp.a(scanner.cpp.o): requires dynamic R_X86_64_32 reloc which may overflow at runtime; recompile with -fPIC

timestamp problem

Hi:)
How to solve the timestamp problem between camera and lidar ?
What specific camera and lidar do you use in the real environment?
Thank you

get error of tracklet_depth_node-3

when start running, got error as below:

Got the camera info:
img_width: 1226
img_height: 370
focal_length_x: 707.091
principalPointX: 601.887
principalPointY: 183.11

Initialize DepthEstimator Post
DepthEstimator successful initialized
================================================================================REQUIRED process [tracklet_depth_node-3] has died!
process has died [pid 23803, exit code -11, cmd /home/carmark/SLAM/limo-slam/devel_limo_release/lib/tracklets_depth_ros_tool/tracklet_depth_node __name:=tracklet_depth_node __log:=/home/carmark/.ros/log/ee4ed292-c0d5-11e8-848d-9cb6d0f8f3e7/tracklet_depth_node-3.log].
log file: /home/carmark/.ros/log/ee4ed292-c0d5-11e8-848d-9cb6d0f8f3e7/tracklet_depth_node-3*.log
Initiating shutdown!

[mono_lidar-17] killing on exit
[semantic_labels-16] killing on exit
[label_dilation-15] killing on exit
[add_outlier_flag-14] killing on exit
[transform_local_cs_camera_gt-13] killing on exit
[transform_vehicle_camera_vehicle_gt-12] killing on exit
[transform_local_cs-11] killing on exit
[transform_local_estimate_prior-10] killing on exit
[transform_local_cs_left_camera_estimate_prior-9] killing on exit
[transform_vehicle_left_camera_estimate_prior-8] killing on exit
[ INFO] [1537888640.489776084, 0.528613523]: Duration feature matching and tracking: 71 ms
[transform_local_cs_vehcile_estimate-7] killing on exit
[transform_vehicle_left_camera_estimate-6] killing on exit
[viso_feature_tracking_node_left-2] killing on exit
[tf2_static_alias_vehicle_to_rig_left_estimate-4] killing on exit
[tf2_static_alias_vehicle_to_rig_right_estimate-5] killing on exit
[tracklet_depth_node-3] killing on exit
[gamma_correction_node_left-1] killing on exit
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injectorboost::lock_error >'
what(): boost: mutex lock failed in pthread_mutex_lock: Invalid argument

Dumped map to /tmp/mono_lidar_map_dump.yaml--------------------------------------

shutting down processing monitor...
... shutting down processing monitor complete
done

Build error in "bash install_repos.sh"

Hi, I am trying to run your code. But when I followed the instruction to build repos bash install_repos.sh I got errors:

`Errors << rosinterface_handler:make /media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/logs_limo_release/rosinterface_handler/build.make.000.log
Traceback (most recent call last):
File "/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/src/rosinterface_handler/test/cfg/DefaultsMissing.rosif", line 14, in
exit(gen.generate("rosinterface_handler", "rosinterface_handler_test", "DefaultsMissing"))
File "/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/src/rosinterface_handler/src/rosinterface_handler/interface_generator_catkin.py", line 562, in generate
return self._generateImpl()
File "/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/src/rosinterface_handler/src/rosinterface_handler/interface_generator_catkin.py", line 571, in _generateImpl
self._generatepy()
File "/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/src/rosinterface_handler/src/rosinterface_handler/interface_generator_catkin.py", line 947, in _generatepy
with open(init_file, 'wa') as f:

ValueError: must have exactly one of create/read/write/append mode

Traceback (most recent call last):
File "/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/src/rosinterface_handler/test/cfg/Defaults.rosif", line 41, in
exit(gen.generate("rosinterface_handler", "rosinterface_handler_test", "Defaults"))
File "/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/src/rosinterface_handler/src/rosinterface_handler/interface_generator_catkin.py", line 562, in generate
return self._generateImpl()
File "/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/src/rosinterface_handler/src/rosinterface_handler/interface_generator_catkin.py", line 571, in _generateImpl
self._generatepy()
File "/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/src/rosinterface_handler/src/rosinterface_handler/interface_generator_catkin.py", line 947, in _generatepy
with open(init_file, 'wa') as f:

ValueError: must have exactly one of create/read/write/append mode

make[2]: *** [/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/devel_limo_release/.private/rosinterface_handler/include/rosinterface_handler/DefaultsMissingInterface.h] Error 1
make[2]: *** Deleting file '/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/devel_limo_release/.private/rosinterface_handler/include/rosinterface_handler/DefaultsMissingInterface.h'
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/devel_limo_release/.private/rosinterface_handler/include/rosinterface_handler/DefaultsInterface.h] Error 1
make[2]: *** Deleting file '/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/devel_limo_release/.private/rosinterface_handler/include/rosinterface_handler/DefaultsInterface.h'
......
Failed << viso2:cmake [ Exited with code 1 ]
Failed <<< viso2 [ 2.8 seconds ]
[build] Summary: 2 of 20 packages succeeded.
[build] Ignored: 3 packages were skipped or are blacklisted.
[build] Warnings: None.
[build] Abandoned: 10 packages were abandoned.
[build] Failed: 8 packages failed.
[build] Runtime: 9.1 seconds total.
[build] Note: Workspace packages have changed, please re-source setup files to use them.`

According to the error ValueError: must have exactly one of create/read/write/append mode, I changed the source code in 'interface_generator_catkin.py' by replacing with open(init_file, 'wa') as f: with with open(init_file, 'w') as f:. Then I got other errors:

`Errors << rosinterface_handler:make /media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/logs_limo_release/rosinterface_handler/build.make.001.log
File "/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/devel_limo_release/.private/rosinterface_handler/share/rosinterface_handler/cfg/DefaultsAtLaunch.cfg", line 33
<filter object at 0x7fa5be3dda20>.add(name = 'verbosity_param_wo_default', paramtype = 'str', level = 0, description = 'Sets the verbosity for this node', edit_method=verbosity_param_wo_default, default="0")
^

SyntaxError: invalid syntax

make[2]: *** [/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/devel_limo_release/.private/rosinterface_handler/include/rosinterface_handler/DefaultsAtLaunchConfig.h] Error 1
make[2]: *** Waiting for unfinished jobs....
File "/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/devel_limo_release/.private/rosinterface_handler/share/rosinterface_handler/cfg/Defaults.cfg", line 26
<filter object at 0x7f9c9e343c50>.add(name = 'int_param_w_default', paramtype = 'int', level = 0, description = 'An Integer parameter', edit_method="", default=1)
^

SyntaxError: invalid syntax

make[2]: *** [/media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/devel_limo_release/.private/rosinterface_handler/include/rosinterface_handler/DefaultsConfig.h] Error 1
make[1]: *** [CMakeFiles/rosinterface_handler_gencfg.dir/all] Error 2
make: *** [all] Error 2
cd /media/rain/Win10_E/SLAM/Codes/LIMO/catkin_ws/build_limo_release/rosinterface_handler; catkin build --get-env rosinterface_handler | catkin env -si /usr/bin/make --jobserver-fds=6,7 -j; cd -
...........................................................................................................................................................................................................
Failed << rosinterface_handler:make [ Exited with code 2 ]
Failed <<< rosinterface_handler [ 0.5 seconds ]
Abandoned <<< matches_msg_conversions_ros [ Unrelated job failed ]
Abandoned <<< keyframe_bundle_adjustment [ Unrelated job failed ]
Abandoned <<< image_preproc_ros_tool [ Unrelated job failed ]
Abandoned <<< matches_conversion_ros_tool [ Unrelated job failed ]
Abandoned <<< util_nodes_tf2_ros_tool [ Unrelated job failed ]
Abandoned <<< feature_tracking_core [ Unrelated job failed ]
Abandoned <<< tracklets_depth_ros_tool [ Unrelated job failed ]
Abandoned <<< viso_feature_tracking_ros_tool [ Unrelated job failed ]
Abandoned <<< keyframe_bundle_adjustment_ros_tool [ Unrelated job failed ]
Abandoned <<< demo_keyframe_bundle_adjustment_meta [ Unrelated job failed ]
......
Failed << image_preproc:cmake [ Exited with code 1 ]
Failed <<< image_preproc [ 1.1 seconds ]
[build] Summary: 1 of 19 packages succeeded.
[build] Ignored: 3 packages were skipped or are blacklisted.
[build] Warnings: None.
[build] Abandoned: 10 packages were abandoned.
[build] Failed: 8 packages failed.
[build] Runtime: 2.3 seconds total. `

**My default python version is 3.6.6. Even after I changed it to version 2.7.12, I got the same error.

So, do you know how to fix it?**

Failed to implement the LIMO to my own dataset

I want to implement the LIMO to my own dataset. I have images and velodyne as well, refer to your template bag file, I record my bag file as following topic:
image
As you said the semantic label not compulsory in another issues, I disabled it as well.

Since I do not have gray scale image, so i use 'image_proc' convert my color image to the gray scale.

The problem is about the /tf and /tf_static, I am not really understand how you arrange you /tf and /tf_static topic, but i noticed you said It need to transform the velodyne to camera. My dataset is from a vehicle which contain the Lidar, camera and GPS. It has three frame id and child frame id combinations: 1. agv_ndt/odom and agv_ndt/base_link 2. agv_ndt/map and agv_ndt/odom 3. world and agv_ndt/map.

Since I am not sure how they make this dataset and what these frame id means. So i just convert the first combination to the '/sensor/velodyne and /sensor/camera' (you see it has 2916 mesage, but velodyne and images also around 600, is this affect?).

I also change the frame id name in topic '/sensor/camera/grayscale/left/image_rect' to '/sensor/camera' and '/sensor/velodyne/cloud_euclidean' to '/sensor/velodyne, so they are consistent with the /tf topic.

I did not change the frame id in for color image, because I noticed color image topic was not subscribe by the LIMO while it's running. I also did not change id name in /tf_static, because I define the '/sensor/velodyne' as header frame and '/sensor/camera' as child frame directly in /tf.

After all of these processing to my own bag file. It still impossible to implement it to LIMO. Terminal is looks like this:

image
image

For your template kitti bag, after got the tf transformation, it will find out the image, show image information, then start calculation. For my bag file, it can not find the images at all.

What you think the possible reason of this? I appreciate any advice worth to try.

catkin run_test error

@johannes-graeter Thank you for your great job!
When i run "catkin run_tests --profile limo_release" command, i got this errror :

test_results/keyframe_bundle_adjustment/gtest-keyframe_bundle_adjustment-keyframe_bundle_adjustment-test.xml: 16 tests, 0 errors, 1 failures, 0 skipped
Summary: 16 tests, 0 errors, 1 failures, 0 skipped
CMakeFiles/_run_tests_keyframe_bundle_adjustment.dir/build.make:57: recipe for target '_run_tests_keyframe_bundle_adjustment' failed
make[3]: Leaving directory '/home/liwenyi/limo_ws/build_limo_release/keyframe_bundle_adjustment'
CMakeFiles/Makefile2:270: recipe for target 'CMakeFiles/_run_tests_keyframe_bundle_adjustment.dir/all' failed
make[2]: Leaving directory '/home/liwenyi/limo_ws/build_limo_release/keyframe_bundle_adjustment'
make[3]: *** [_run_tests_keyframe_bundle_adjustment] Error 1
make[2]: *** [CMakeFiles/_run_tests_keyframe_bundle_adjustment.dir/all] Error 2
CMakeFiles/Makefile2:407: recipe for target 'CMakeFiles/run_tests.dir/rule' failed
make[1]: Leaving directory '/home/liwenyi/limo_ws/build_limo_release/keyframe_bundle_adjustment'
make[1]: *** [CMakeFiles/run_tests.dir/rule] Error 2
Makefile:303: recipe for target 'run_tests' failed
make: *** [run_tests] Error 2
cd /home/liwenyi/limo_ws/build_limo_release/keyframe_bundle_adjustment; catkin build --get-env keyframe_bundle_adjustment | catkin env -si /usr/bin/make run_tests --jobserver-fds=6,7 -j; cd -

I am a newer to lidar_camera_slam.How can I solve this problem? Thank you so much!

CMake error when building

Hello,
thank you for sharing this project. Unfortunately, I'm stuck trying to build it in the virtual machine.

I downloaded the provided VM image, pulled the newest version of the limo repo and installed the dependencies via bash install_repos.sh.

The build process fails with:

CMake Error at mrt_cmake_modules/cmake/Modules/FindAutoDeps.cmake:80 (message):
Package opencv_apps is specified for autodepend but cmake variables are not defined.

fail

Fail to run with own bag file

Hello,

I made a bag file with the package in eth repo https://github.com/ethz-asl/kitti_to_rosbag

I used, kitti processed data on raw data page not the odometry dataset!

I set topic name and frame ID as you did and then used static transform publisher in launch file to organize /sensor/camera/grayscale/image_rect, /sensor/camera, sensor/velodyne.

types: sensor_msgs/CameraInfo [c9a58c1b0b154e0e6da7578cb991d214] sensor_msgs/Image [060021388200f6f0f447d0fcd9c64743] sensor_msgs/PointCloud2 [1158d486dd51d683ce2f1be655c3c181] topics: /sensor/camera/color/left/camera_info 4544 msgs : sensor_msgs/CameraInfo /sensor/camera/color/left/image_rect 4544 msgs : sensor_msgs/Image /sensor/camera/grayscale/left/camera_info 4544 msgs : sensor_msgs/CameraInfo /sensor/camera/grayscale/left/image_rect 4544 msgs : sensor_msgs/Image /sensor/velodyne/cloud_euclidean 4544 msgs : sensor_msgs/PointCloud2

However, when I tried to run the code it fails with

Pusblisher name pointcloud camera cs: /monolidar_debug/cloud_camera_cs
Publisher name pointcloud interpolated: /monolidar_debug/cloud_interpolated
Publisher name image projection cloud: /monolidar_debug/image_cloud_projection
[ INFO] [1576692784.941486545]: Started '/tf2_static_alias_vehicle_to_rig_left_estimate' in namespace '/'.
Subscribed topics: 
/clock
/tf
/tf_static
Advertised topics: 
/rosout
/tf2_static_alias_vehicle_to_rig_left_estimate/parameter_descriptions
/tf2_static_alias_vehicle_to_rig_left_estimate/parameter_updates
/tf_static
/diagnostics

[ INFO] [1576692784.942262516]: Started '/tf2_static_alias_vehicle_to_rig_right_estimate' in namespace '/'.
Subscribed topics: 
/clock
/tf
/tf_static
Advertised topics: 
/rosout
/tf2_static_alias_vehicle_to_rig_right_estimate/parameter_descriptions
/tf2_static_alias_vehicle_to_rig_right_estimate/parameter_updates
/tf_static
/diagnostics

[ INFO] [1576692784.950787996]: Started '/add_outlier_flag_node' in namespace '/'.
Subscribed topics: 
/clock
/tracklets_depth/tracklets/left
/add_outlier_flag_node/in_topic
Advertised topics: 
/rosout
/add_outlier_flag_node/parameter_descriptions
/add_outlier_flag_node/parameter_updates
/tracklets_depth/tracklets/left/with_outlier_dummy

Publisher name calc depth stats: /monolidar_debug/depthcalc_stats
Publisher name tracklets depth with depth: /tracklets_depth/tracklets/left
[ INFO] [1576692784.980272889, 1317614148.426732672]: Waiting for the ROSBAG to start
[ERROR] [1576692784.980488773, 1317614148.426732672]: "sensor/camera" passed to lookupTransform argument target_frame does not exist. 
[ INFO] [1576692785.171751676, 1317614148.445853703]: waitForService: Service [/feature_matching_nodelet_manager/load_nodelet] is now available.
[ INFO] [1576692785.179935260, 1317614148.446859335]: Started '/feature_matching_nodelet_manager' in namespace '/'.
Subscribed topics: 
/clock
/sensor/camera/grayscale/left/image_rect
/feature_matching_nodelet_manager/bond
/sensor/camera/grayscale/left/image_rect_g
Advertised topics: 
/rosout
/gamma_correction_nodelet_left/parameter_descriptions
/gamma_correction_nodelet_left/parameter_updates
/sensor/camera/grayscale/left/image_rect_g
/feature_matching_nodelet_manager/bond
/matches/grayscale/left

[ INFO] [1576692785.589903439, 1317614148.488198204]: Started '/mono_lidar' in namespace '/'.
Subscribed topics: 
/clock
/tf
/tf_static
/tracklets_depth/tracklets/left/with_outlier_dummy
/sensor/camera/grayscale/left/camera_info
Advertised topics: 
/rosout
/mono_lidar/parameter_descriptions
/mono_lidar/parameter_updates
/tf
/diagnostics
/estimate/active_path
/estimate/complete_path
/estimate/landmarks
/mono_lidar/planes_topic

[ INFO] [1576692785.932972089, 1317614148.522593581]: /gamma_correction_nodelet_left Gamma correction Entered callback!
[ INFO] [1576692785.934925966, 1317614148.522593581]: /gamma_correction_nodelet_left gamma correction leaving callback!
[ INFO] [1576692786.006618082, 1317614148.529637008]: Duration feature matching and tracking: 71 ms
[ INFO] [1576692786.966240617, 1317614148.625935861]: /gamma_correction_nodelet_left Gamma correction Entered callback!
[ INFO] [1576692786.967394923, 1317614148.625935861]: /gamma_correction_nodelet_left gamma correction leaving callback!
[ INFO] [1576692787.158796571, 1317614148.645053746]: Duration feature matching and tracking: 191 ms
[ INFO] [1576692788.001864798, 1317614148.728774244]: /gamma_correction_nodelet_left Gamma correction Entered callback!
[ INFO] [1576692788.002903227, 1317614148.728774244]: /gamma_correction_nodelet_left gamma correction leaving callback!
[ INFO] [1576692788.186816896, 1317614148.747894257]: Duration feature matching and tracking: 183 ms
[ INFO] [1576692789.038945279, 1317614148.832029548]: /gamma_correction_nodelet_left Gamma correction Entered callback!
[ INFO] [1576692789.042283681, 1317614148.833220280]: /gamma_correction_nodelet_left gamma correction leaving callback!
[ INFO] [1576692789.232272671, 1317614148.852345104]: Duration feature matching and tracking: 189 ms
[ INFO] [1576692789.977019771, 1317614148.926949837]: Got the tf transformations: 
-0.00185775   -0.999966 -0.00803998 -0.00478403
-0.00648148  0.00805186   -0.999947  -0.0733743
   0.999977 -0.00180554 -0.00649622   -0.333997
          0           0           0           1
[ INFO] [1576692790.004324036, 1317614148.928963760]: Got the camera info:
Got the camera info:
img_width: 1241
img_height: 376
focal_length_x: 718.856
principalPointX: 607.193
principalPointY: 185.216

Initialize DepthEstimator Post
DepthEstimator successful initialized
[ INFO] [1576692790.074903636, 1317614148.936008810]: /gamma_correction_nodelet_left Gamma correction Entered callback!
[ INFO] [1576692790.075925730, 1317614148.936008810]: /gamma_correction_nodelet_left gamma correction leaving callback!
size before randomization 116979
size after randomization 6000
Publish image projection cloud
[ INFO] [1576692790.229899164, 1317614148.952137887]: Duration tracklet_depth_ros_tool=225 ms
[ INFO] [1576692790.266362575, 1317614148.955156956]: Duration feature matching and tracking: 190 ms
size before randomization 115326
size after randomization 6000
Publish image projection cloud
[ INFO] [1576692790.762193188, 1317614149.004744104]: Duration tracklet_depth_ros_tool=528 ms
terminate called after throwing an instance of 'std::runtime_error'
  what():  Time is out of dual 32-bit range
[ INFO] [1576692791.111181541, 1317614149.040300680]: /gamma_correction_nodelet_left Gamma correction Entered callback!
[ INFO] [1576692791.112115439, 1317614149.040300680]: /gamma_correction_nodelet_left gamma correction leaving callback!
================================================================================REQUIRED process [mono_lidar-19] has died!
process has died [pid 25457, exit code -6, cmd /home/hcyoo/catkin_ws6/devel/lib/keyframe_bundle_adjustment_ros_tool/mono_lidar __name:=mono_lidar __log:=/home/hcyoo/.ros/log/e135669e-217c-11ea-bd34-74d4358c6f8e/mono_lidar-19.log].
log file: /home/hcyoo/.ros/log/e135669e-217c-11ea-bd34-74d4358c6f8e/mono_lidar-19*.log
Initiating shutdown!
================================================================================
size before randomization 114734
size after randomization 6000
[add_outlier_flag_node-18] killing on exit
[transform_local_cs_camera_gt-17] killing on exit
[transform_local_estimate_prior-14] killing on exit
[mono_lidar-19] killing on exit
[transform_vehicle_left_camera_estimate_prior-12] killing on exit
[transform_local_cs-15] killing on exit
[transform_local_cs_left_camera_estimate_prior-13] killing on exit
[transform_vehicle_camera_vehicle_gt-16] killing on exit
[transform_vehicle_left_camera_estimate-10] killing on exit
[tf2_static_alias_vehicle_to_rig_right_estimate-9] killing on exit
[transform_local_cs_vehcile_estimate-11] killing on exit
[ INFO] [1576692791.335967701, 1317614149.062963705]: Duration feature matching and tracking: 223 ms
[tf2_static_alias_vehicle_to_rig_left_estimate-8] killing on exit
[tracklets_depth_node-7] killing on exit
[viso_feature_tracking_nodelet_left-6] killing on exit
[gamma_correction_nodelet_left-5] killing on exit
[ INFO] [1576692791.429957451, 1317614149.072016603]: Unloading nodelet /viso_feature_tracking_nodelet_left from manager feature_matching_nodelet_manager
Publish image projection cloud
[feature_matching_nodelet_manager-4] killing on exit
[link2_broadcaster-3] killing on exit
[link1_broadcaster-2] killing on exit
[link0_broadcaster-1] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done

Note that, time sync is slightly different ~0.00x sec (because this is not odometry dataset there has some time difference)

Does anyone have same experience?

Please give me some comments

Thank you!

Some qeustions for real data (VLP-16 and Mono)

Hello. I'm working on a real data experiment using LIMO. I use VLP-16 and mono camera. We have confirmed that LIMO is working with our sensor configuration. However, since LiDAR has 16 beams, it is necessary to modify parameters for good performance. What parameters should I change in this case? And can I disable the label image?
I would be very helpful if you let me know some tips.

Thank you.

odometry

where is the Odometry's code,I noticed that you did't use the libviso2.

build error in ROS melodic

Hi.
I have followed the wiki/readme and tried to install with your provided script. But i could not get it built. I have two systems with Ubuntu 18.04, ROS melodic, opencv3.4.4, libpcl-dev 1.8.1, ceres 1.14.0. Both of my systems show same error and start failing while building the util_nodes_tf2_ros_tool. I hope you have some time to help me to resolve it. Thank you.

Best regards
Kawser Jahan

edit:
However, I have used sudo apt-get install ros-melodic-opencv-apps, not the one for the ros kinect.

unittests_dump.txt
Screenshot from 2019-07-06 22-59-46

A question about how can point clout project into camera frame

Hi,I want to ask a question about your paper,"First the LIDAR point cloud is transformed into the camera frame and projected onto the image plane. "in BLOCK S: SCALE ESTIMATION , Approach. I want to know which park of your code can work out it? Thank you

build error

Hi,
Thanks for your project!
when I followed the instruction to build repos bash install_repos.sh I got errors:
Errors << robust_optimization:make /home/dh/catkin_ws_limo/logs/robust_optimization/build.make.000.log
In file included from /home/dh/catkin_ws_limo/src/limo/robust_optimization/include/robust_optimization/internal/apply_trimmer.hpp:16:0,
from /home/dh/catkin_ws_limo/src/limo/robust_optimization/src/robust_solving.cpp:10:
/home/dh/catkin_ws_limo/src/limo/robust_optimization/include/robust_optimization/internal/trimmer_quantile.hpp: In member function ‘std::vector robust_optimization::TrimmerQuantile::getOutliers(const std::map<Id, double>&)’:
/home/dh/catkin_ws_limo/src/limo/robust_optimization/include/robust_optimization/internal/trimmer_quantile.hpp:45:91: error: use of ‘auto’ in lambda parameter declaration only available with -std=c++14 or -std=gnu++14
residuals_input.cbegin(), residuals_input.cend(), input_vec.begin(), [](const auto& a) { return a; });

I have changed to gcc 7,but it still doesn't work,can you give me some advice?Thank you!

About the principle

Hi,
This is a great work. Do you have some paper or materials to introduce the principle of the code? How to fuse the lidar and visual data in SLAM?
Thanks very much.

no `matches_msg_types`

Hi @johannes-graeter , Thanks for your project.
I'd like to have a try, but when compiling, it seems I don't have matches_msg_types, is this an internal project?
could you help me?
Thanks again!

Code for epipolar error

Hi All:

In the paper for equation (3) where the epipolar error is computed to add constraints between two features without depth. But I cannot find where the code is that for the epipolar error computation. Maybe I just missed it, or can anyone shows me where the code is ?

Thanks !

Running demo, using 04.bag, I see nothing.

When I launch the limo node, I see the following flash by quickly
[ERROR] [1537984722.112431485]: Skipped loading plugin with error: XML Document '/home/xzcjml/catkin_limo/src/mono_lidar_depth/tracklets_depth_ros_tool/nodelet_plugins.xml' has no Root Element. This likely means the XML is malformed or missing..

and also
[ERROR] [1537984722.275178784]: "sensor/camera" passed to lookupTransform argument target_frame does not exist.

But generally, the console is emitting messages. Here's ros starup before I unpause rosbag player

SUMMARY
========

PARAMETERS
 * /add_outlier_flag_node/has_depth: True
 * /add_outlier_flag_node/publisher_topic: /tracklets_depth/...
 * /add_outlier_flag_node/subscriber_depth_topic: /tracklets_depth/...
 * /add_outlier_flag_node/verbosity: info
 * /gamma_correction_nodelet_left/auto_gamma: True
 * /gamma_correction_nodelet_left/gamma: 1.2
 * /label_dilation_nodelet/half_kernel_size: 8
 * /label_dilation_nodelet/publisher_topic: /semantic_labels/...
 * /label_dilation_nodelet/subscriber_topic: /sensor/camera/co...
 * /label_dilation_nodelet/verbosity: info
 * /mono_lidar/active_path_publisher_topic: /estimate/active_...
 * /mono_lidar/calib_source_frame_id: estimate/vehicle
 * /mono_lidar/calib_target_frame_id: estimate/sensor/c...
 * /mono_lidar/camera_info_subscriber_topic: /sensor/camera/gr...
 * /mono_lidar/critical_rotation_difference: 0.03
 * /mono_lidar/dump_path: /tmp/poses_dump.txt
 * /mono_lidar/height_over_ground: 0.31
 * /mono_lidar/landmarks_publisher_topic: /estimate/landmarks
 * /mono_lidar/max_number_landmarks_far_bin: 400
 * /mono_lidar/max_number_landmarks_middle_bin: 400
 * /mono_lidar/max_number_landmarks_near_bin: 400
 * /mono_lidar/max_size_optimization_window: 12
 * /mono_lidar/max_solver_time: 0.4
 * /mono_lidar/min_median_flow: 5.0
 * /mono_lidar/min_number_connecting_landmarks: 18
 * /mono_lidar/outlier_labels_yaml: /home/xzcjml/catk...
 * /mono_lidar/outlier_rejection_num_iterations: 1
 * /mono_lidar/outlier_rejection_quantile: 0.95
 * /mono_lidar/path_publisher_topic: /estimate/complet...
 * /mono_lidar/prior_global_frame: estimate_prior/lo...
 * /mono_lidar/prior_speed: 5.0
 * /mono_lidar/prior_vehicle_frame: 
 * /mono_lidar/robust_loss_depth_thres: 0.16
 * /mono_lidar/robust_loss_reprojection_thres: 1.6
 * /mono_lidar/show_debug_image: False
 * /mono_lidar/shrubbery_weight: 0.9
 * /mono_lidar/tf_child_frame_id: estimate/vehicle
 * /mono_lidar/tf_parent_frame_id: estimate/local_cs...
 * /mono_lidar/tf_waiting_time: 0.1
 * /mono_lidar/time_between_keyframes_sec: 0.3
 * /mono_lidar/tracklets_subscriber_topic: /tracklets_depth/...
 * /mono_lidar/trajectory_publisher_topic: /estimate/trajectory
 * /mono_lidar/verbosity: debug
 * /rosdistro: kinetic
 * /rosversion: 1.12.14
 * /semantic_labels_nodelet/matches_publisher_topic: /tracklets_depth/...
 * /semantic_labels_nodelet/roi_height: 3
 * /semantic_labels_nodelet/roi_width: 3
 * /semantic_labels_nodelet/subscriber_labels_topic: /semantic_labels/...
 * /semantic_labels_nodelet/subscriber_matches_topic: /tracklets_depth/...
 * /semantic_labels_nodelet/verbosity: debug
 * /tf2_static_alias_vehicle_to_rig_left_estimate/from_source_frame_id: sensor/camera/gra...
 * /tf2_static_alias_vehicle_to_rig_left_estimate/from_target_frame_id: sensor/camera
 * /tf2_static_alias_vehicle_to_rig_left_estimate/to_source_frame_id: estimate/sensor/c...
 * /tf2_static_alias_vehicle_to_rig_left_estimate/to_target_frame_id: estimate/sensor/c...
 * /tf2_static_alias_vehicle_to_rig_right_estimate/from_source_frame_id: sensor/camera/gra...
 * /tf2_static_alias_vehicle_to_rig_right_estimate/from_target_frame_id: sensor/camera
 * /tf2_static_alias_vehicle_to_rig_right_estimate/to_source_frame_id: estimate/sensor/c...
 * /tf2_static_alias_vehicle_to_rig_right_estimate/to_target_frame_id: estimate/sensor/c...
 * /tracklets_depth_node/config_depth_estimator: /home/xzcjml/catk...
 * /tracklets_depth_node/config_tracklet_depth: /home/xzcjml/catk...
 * /tracklets_depth_node/verbosity: info
 * /use_sim_time: True
 * /viso_feature_tracking_nodelet_left/config: /home/xzcjml/catk...
 * /viso_feature_tracking_nodelet_left/verbosity: info

NODES
  /
    add_outlier_flag_node (matches_conversion_ros_tool/add_outlier_flag)
    feature_matching_nodelet_manager (nodelet/nodelet)
    gamma_correction_nodelet_left (nodelet/nodelet)
    label_dilation_nodelet (nodelet/nodelet)
    mono_lidar (keyframe_bundle_adjustment_ros_tool/mono_lidar)
    semantic_labels_nodelet (nodelet/nodelet)
    semantic_labels_nodelet_manager (nodelet/nodelet)
    tf2_static_alias_vehicle_to_rig_left_estimate (util_nodes_tf2_ros_tool/static_transform_alias)
    tf2_static_alias_vehicle_to_rig_right_estimate (util_nodes_tf2_ros_tool/static_transform_alias)
    tracklets_depth_node (tracklets_depth_ros_tool/tracklet_depth_node)
    transform_local_cs (tf2_ros/static_transform_publisher)
    transform_local_cs_camera_gt (tf2_ros/static_transform_publisher)
    transform_local_cs_left_camera_estimate_prior (tf2_ros/static_transform_publisher)
    transform_local_cs_vehcile_estimate (tf2_ros/static_transform_publisher)
    transform_local_estimate_prior (tf2_ros/static_transform_publisher)
    transform_vehicle_camera_vehicle_gt (tf2_ros/static_transform_publisher)
    transform_vehicle_left_camera_estimate (tf2_ros/static_transform_publisher)
    transform_vehicle_left_camera_estimate_prior (tf2_ros/static_transform_publisher)
    viso_feature_tracking_nodelet_left (nodelet/nodelet)

ROS_MASTER_URI=http://localhost:11311

process[feature_matching_nodelet_manager-1]: started with pid [18972]
process[gamma_correction_nodelet_left-2]: started with pid [18973]
process[viso_feature_tracking_nodelet_left-3]: started with pid [18974]
process[tracklets_depth_node-4]: started with pid [18983]
process[tf2_static_alias_vehicle_to_rig_left_estimate-5]: started with pid [19000]
[ INFO] [1537985361.460632902]: Loading nodelet /viso_feature_tracking_nodelet_left of type viso_feature_tracking_ros_tool/VisoFeatureTrackingNodelet to manager feature_matching_nodelet_manager with the following remappings:
[ INFO] [1537985361.460684455]: /src/image -> /sensor/camera/grayscale/left/image_rect_g
[ INFO] [1537985361.460697607]: /tgt/matches -> /matches/grayscale/left
[ERROR] [1537985361.462564799]: Skipped loading plugin with error: XML Document '/home/xzcjml/catkin_limo/src/mono_lidar_depth/tracklets_depth_ros_tool/nodelet_plugins.xml' has no Root Element. This likely means the XML is malformed or missing..
[ INFO] [1537985361.462697064]: waitForService: Service [/feature_matching_nodelet_manager/load_nodelet] has not been advertised, waiting...
process[tf2_static_alias_vehicle_to_rig_right_estimate-6]: started with pid [19013]
process[transform_vehicle_left_camera_estimate-7]: started with pid [19027]
[ INFO] [1537985361.478147242]: Initializing nodelet with 8 worker threads.
process[transform_local_cs_vehcile_estimate-8]: started with pid [19040]
process[transform_vehicle_left_camera_estimate_prior-9]: started with pid [19068]
process[transform_local_cs_left_camera_estimate_prior-10]: started with pid [19086]
process[transform_local_estimate_prior-11]: started with pid [19094]
process[transform_local_cs-12]: started with pid [19107]
process[transform_vehicle_camera_vehicle_gt-13]: started with pid [19135]
Starting node: TrackletDepth Estimator 
process[transform_local_cs_camera_gt-14]: started with pid [19152]
process[add_outlier_flag_node-15]: started with pid [19162]
process[semantic_labels_nodelet_manager-16]: started with pid [19176]
process[label_dilation_nodelet-17]: started with pid [19187]
process[semantic_labels_nodelet-18]: started with pid [19198]
process[mono_lidar-19]: started with pid [19211]
[ERROR] [1537985361.613059464]: Skipped loading plugin with error: XML Document '/home/xzcjml/catkin_limo/src/mono_lidar_depth/tracklets_depth_ros_tool/nodelet_plugins.xml' has no Root Element. This likely means the XML is malformed or missing..
[ INFO] [1537985361.687958870]: Loading nodelet /label_dilation_nodelet of type image_preproc_ros_tool/LabelDilationNodelet to manager semantic_labels_nodelet_manager with the following remappings:
[ INFO] [1537985361.690018349]: Loading nodelet /semantic_labels_nodelet of type matches_conversion_ros_tool/SemanticLabelsNodelet to manager semantic_labels_nodelet_manager with the following remappings:
Initalize parameters
[ INFO] [1537985361.703956360]: waitForService: Service [/semantic_labels_nodelet_manager/load_nodelet] has not been advertised, waiting...
config_tracklets_depth: /home/xzcjml/catkin_limo/src/limo/demo_keyframe_bundle_adjustment_meta/res/config_tracklets_depth_ros_tool.yaml
[ INFO] [1537985361.705460324]: waitForService: Service [/semantic_labels_nodelet_manager/load_nodelet] has not been advertised, waiting...
[ INFO] [1537985361.706346711]: Initializing nodelet with 8 worker threads.
config_tracklets_depth: /home/xzcjml/catkin_limo/src/limo/demo_keyframe_bundle_adjustment_meta/res/mono_lidar_fusion_parameters.yaml
Load settings from: /home/xzcjml/catkin_limo/src/limo/demo_keyframe_bundle_adjustment_meta/res/config_tracklets_depth_ros_tool.yaml

Load settings from: /home/xzcjml/catkin_limo/src/limo/demo_keyframe_bundle_adjustment_meta/res/mono_lidar_fusion_parameters.yaml

Initialize DepthEstimator Pre
Config file DepthEstimator: /home/xzcjml/catkin_limo/src/limo/demo_keyframe_bundle_adjustment_meta/res/mono_lidar_fusion_parameters.yaml
Load settings from: /home/xzcjml/catkin_limo/src/limo/demo_keyframe_bundle_adjustment_meta/res/mono_lidar_fusion_parameters.yaml

DepthEstimator parameters: 

_____ pixel area _____ 
neighbor_search_mode: 0
pixelarea_search_witdh: 6
pixelarea_search_height: 9
pixelarea_search_offset_x: 0
pixelarea_search_offset_y: 0

_____ Nearest Neighbors search _____
do_use_nearestNeighborSearch: 0
nnSearch_count10

_____ Radius search _____

do_use_radiusSearch: 1
radiusSearch_radius: 10
radiusSearch_count_min: 3

_____ Histogram Segmentation _____

do_use_histogram_segmentation: 1
histogram_segmentation_bin_witdh: 0.3
histogram_segmentation_min_pointcount: 1

_____ Depth segmentation _____

do_use_depth_segmentation: 0
depth_segmentation_max_treshold_gradient: 10
depth_segmentation_max_neighbor_distance: 0.2
depth_segmentation_max_neighbor_distance_gradient: 0.02
depth_segmentation_max_neighbor_to_seepoint_distance: 0.5
depth_segmentation_max_neighbor_to_seepoint_distance_gradient: 0.05
depth_segmentation_max_seedpoint_to_seepoint_distance: 0.05
depth_segmentation_max_seedpoint_to_seepoint_distance_gradient: 0.5
depth_segmentation_max_pointcount: 4

____ depth tresholds _____
treshold_depth_enabled: 1
treshold_depth_mode: 0
treshold_depth_max: 100
treshold_depth_min: 0

_____ depth local reshold _____
treshold_depth_local_enabled: 1
treshold_depth_local_mode: 0
treshold_depth_local_valuetype: 1
treshold_depth_local_value: 0.5

_____ PCA _____ 
do_use_PCA: 0
pca_debug: 1
pca_treshold_3_abs_min: 0.005
pca_treshold_3_2_rel_max: 15
pca_treshold_2_1_rel_min: 1.5

_____ ransac plane estimation _____ 
do_use_ransac_plane: 1
ransac_plane_distance_treshold: 0.2
ransac_plane_max_iterations: 600
ransac_plane_probability: 0.99
ransac_plane_use_refinement: 1
ransac_plane_refinement_treshold: 10.2
ransac_plane_use_camx_treshold: 0
ransac_plane_treshold_camx: 0.2
ransac_plane_point_distance_treshold: 0.2
ransac_plane_debug_visualize: 0

_____ Plane Depth Estimation ____ 
plane_estimator_use_triangle_maximation: 0
plane_estimator_z_x_min_relation: 0
plane_estimator_use_leastsquares: 0
plane_estimator_use_mestimator: 1
_____ misc _____ 
do_use_cut_behind_camera: 1
do_use_triangle_size_maximation: 1
do_check_triangleplanar_condition: 1
triangleplanar_crossnorm_treshold: 0.1
viewray_plane_orthoganality_treshold: 0.1
set_all_depths_to_zero: 0

do_debug_singleFeatures: 0
do_publish_points: 0
do_depth_calc_statistics: 0

Pusblisher name pointcloud camera cs: /monolidar_debug/cloud_camera_cs
Publisher name pointcloud interpolated: /monolidar_debug/cloud_interpolated
Publisher name image projection cloud: /monolidar_debug/image_cloud_projection
Publisher name calc depth stats: /monolidar_debug/depthcalc_stats
Publisher name tracklets depth with depth: /tracklets_depth/tracklets/left
[ INFO] [1537985361.808389733, 0.000000001]: Waiting for the ROSBAG to start
[ERROR] [1537985361.808679949, 0.000000001]: "sensor/camera" passed to lookupTransform argument target_frame does not exist. 
[ INFO] [1537985361.812748781, 0.000000001]: Started '/tf2_static_alias_vehicle_to_rig_left_estimate' in namespace '/'.
Subscribed topics: 
/clock
/tf
/tf_static
Advertised topics: 
/rosout
/tf2_static_alias_vehicle_to_rig_left_estimate/parameter_descriptions
/tf2_static_alias_vehicle_to_rig_left_estimate/parameter_updates
/tf_static
/diagnostics

[ INFO] [1537985361.823090849, 0.000000001]: Started '/tf2_static_alias_vehicle_to_rig_right_estimate' in namespace '/'.
Subscribed topics: 
/clock
/tf
/tf_static
Advertised topics: 
/rosout
/tf2_static_alias_vehicle_to_rig_right_estimate/parameter_descriptions
/tf2_static_alias_vehicle_to_rig_right_estimate/parameter_updates
/tf_static
/diagnostics

[ INFO] [1537985361.835780134]: Started '/add_outlier_flag_node' in namespace '/'.
Subscribed topics: 
/clock
/tracklets_depth/tracklets/left
/add_outlier_flag_node/in_topic
Advertised topics: 
/rosout
/add_outlier_flag_node/parameter_descriptions
/add_outlier_flag_node/parameter_updates
/tracklets_depth/tracklets/left/with_outlier_dummy

[DEBUG] [1537985361.889962880]: Verbosity set to debug
[DEBUG] [1537985361.948585216]: [mono_lidar]
Node mono_lidar has the following parameters:
	/mono_lidar/verbosity:debug
	/mono_lidar/verbosity_debug:debug
	/mono_lidar/verbosity_info:info
	/mono_lidar/verbosity_warning:warning
	/mono_lidar/verbosity_error:error
	/mono_lidar/verbosity_fatal:fatal
	/mono_lidar/diag_pub_topic:out_topic_diagnosed
	/mono_lidar/diagnostic_updater_name:MonoLidarUpdater
	/mono_lidar/diagnostic_updater_hardware_id:MonoLidar
	/mono_lidar/diagnostic_updater_rate:1
	/mono_lidar/diagnostic_updater_rate_tolerance:1
	/mono_lidar/prior_vehicle_frame:
	/mono_lidar/prior_global_frame:estimate_prior/local_cs_vehicle
	/mono_lidar/tf_waiting_time:0.1
	/mono_lidar/calib_target_frame_id:estimate/sensor/camera/grayscale/left
	/mono_lidar/calib_source_frame_id:estimate/vehicle
	/mono_lidar/tf_parent_frame_id:estimate/local_cs_vehicle
	/mono_lidar/tf_child_frame_id:estimate/vehicle
	/mono_lidar/max_number_landmarks_near_bin:400
	/mono_lidar/max_number_landmarks_middle_bin:400
	/mono_lidar/max_number_landmarks_far_bin:400
	/mono_lidar/time_between_keyframes_sec:0.3
	/mono_lidar/min_median_flow:5
	/mono_lidar/critical_rotation_difference:0.03
	/mono_lidar/robust_loss_depth_thres:0.16
	/mono_lidar/robust_loss_reprojection_thres:1.6
	/mono_lidar/min_number_connecting_landmarks:18
	/mono_lidar/max_size_optimization_window:12
	/mono_lidar/shrubbery_weight:0.9
	/mono_lidar/outlier_rejection_quantile:0.95
	/mono_lidar/outlier_rejection_num_iterations:1
	/mono_lidar/height_over_ground:0.31
	/mono_lidar/prior_speed:5
	/mono_lidar/show_debug_image:0
	/mono_lidar/max_solver_time:0.4
	/mono_lidar/dump_path:/tmp/poses_dump.txt
	/mono_lidar/outlier_labels_yaml:/home/xzcjml/catkin_limo/src/limo/keyframe_bundle_adjustment_ros_tool/res/outlier_labels.yaml
	/mono_lidar/tracklets_subscriber_topic:/tracklets_depth/tracklets/left/with_outlier_label
	/mono_lidar/tracklets_subscriber_queue_size:5
	/mono_lidar/camera_info_subscriber_topic:/sensor/camera/grayscale/left/camera_info
	/mono_lidar/camera_info_subscriber_queue_size:5
	/mono_lidar/active_path_publisher_topic:/estimate/active_path
	/mono_lidar/active_path_publisher_queue_size:5
	/mono_lidar/path_publisher_topic:/estimate/complete_path
	/mono_lidar/path_publisher_queue_size:5
	/mono_lidar/landmarks_publisher_topic:/estimate/landmarks
	/mono_lidar/landmarks_publisher_queue_size:5
	/mono_lidar/planes_publisher_topic:planes_topic
	/mono_lidar/planes_publisher_queue_size:5

[DEBUG] [1537985361.949780054]: Depth thres=0.16
[DEBUG] [1537985361.949820374]: Repr thres=1.6
[DEBUG] [1537985361.949852170]: Quantile=0.95
[DEBUG] [1537985361.949876629]: Number iterations=1
[DEBUG] [1537985361.951116869]: MonoLidar: outlier labels 
 -1 0 1 2 3 5 24 25 26 27 28 29 30 31 32 33

[DEBUG] [1537985361.951884009]: MonoLidar: shrubbery weight: 0.9 labels: 
 21 22 23

[DEBUG] [1537985361.978310628]: MonoLidar: Getting transform from vehicle to camera frame

Adding output topics to visualize from rviz didn't help either. However, I was able to visualize the input images, left and right and the velodyne point cloud. So the bag player is working.

how to do the reconstruction from limo

It is a great work about lidar-camera slam,that I want to know how to do the reconstruction,I watch the video in the youtube where there is a picture about reconstruction.Thank you

Build error

Hello,thank u for sharing your project !!!
But when i followed your instruction, i got some problems.
after "bash install_repos.sh" , i got this
build
after "catkin run_tests --profile limo_release" , i got this
test

Here are the details:
Errors << keyframe_bundle_adjustment:make /home/cqu123/workspace/logs_limo_release/keyframe_bundle_adjustment/build.make.002.log
Failed << keyframe_bundle_adjustment:make [ Exited with code 2 ]
Failed <<< keyframe_bundle_adjustment [ 1.1 seconds ]
Abandoned <<< image_preproc_ros_tool [ Unrelated job failed ]
Abandoned <<< matches_conversion_ros_tool [ Unrelated job failed ]
Abandoned <<< util_nodes_tf2_ros_tool [ Unrelated job failed ]
Abandoned <<< tracklets_depth_ros_tool [ Unrelated job failed ]
Abandoned <<< viso_feature_tracking_ros_tool [ Unrelated job failed ]
Abandoned <<< keyframe_bundle_adjustment_ros_tool [ Unrelated job failed ]
Abandoned <<< demo_keyframe_bundle_adjustment_meta [ Unrelated job failed ]

i have installed all the requirements include ceres before build
i'll appreciate if you can reply !

deactivating semantic label

Thank you for great work!

I looked through previous Issues regarding this like #16, #30

However, I don't understand the approach clearly and I tried different way.

It looks fine, but I want to check if it is correct and share this.

  1. kitti_standalone.launch
    Line 52
    <include file="$(find demo_keyframe_bundle_adjustment_meta)/launch/semantic_labels.launch"/>

to

<!-- include file="$(find demo_keyframe_bundle_adjustment_meta)/launch/semantic_labels.launch"/ -->

  1. keyframe_ba_monolid.launch
    Line 4
    <arg name="tracklets_subscriber_topic" default="/tracklets_depth/tracklets/left/with_outlier_label"/>

to

<arg name="tracklets_subscriber_topic" default="/tracklets_depth/tracklets/left/with_outlier_dummy"/>

For number2, I didn't get any issue when I ran the code, but as I said above

I want to get a check from others

Thank you

Odometry Evaluation Results

Hi, sorry to bother you again.

As you suggested to me, I did slow down the rosbag speeds and I obtained same number of poses for each frame. However the results are not good. Can you please comment about, why I obtained such that results???
In the attachments, you can see the results for KITTI_01 and KITTI_04.

Thanks in advanced.

err_mapped_onto_trajectory
error_mapped_onto_trajectory

CMake Error : Package mrt_ceres

Hi,

I followed your instruction to build the project, I get the following error after catkin build command in install_repos.sh file:

Errors     << monolidar_fusion:cmake /home/farid/catkin_ws/logs/monolidar_fusion/build.cmake.004.log                                    
CMake Warning at /home/farid/catkin_ws/devel/share/mrt_cmake_modules/cmake/mrt_cmake_modules-extras.cmake:10 (message):
  Current CMakeLists.txt version is less than the recommended version 2.1.
  If you are the maintainer, please update it with

  'mrt maintenance update_cmakelists monolidar_fusion'.
Call Stack (most recent call first):
  /home/farid/catkin_ws/devel/share/mrt_cmake_modules/cmake/mrt_cmake_modulesConfig.cmake:197 (include)
  CMakeLists.txt:9 (find_package)


CMake Error at /home/farid/catkin_ws/src/mrt_cmake_modules/cmake/Modules/FindAutoDeps.cmake:93 (message):
  Package mrt_ceres: Specified include dir variable CERES_INCLUDE_DIRS not
  set.
Call Stack (most recent call first):
  CMakeLists.txt:16 (find_package)


cd /home/farid/catkin_ws/build/monolidar_fusion; catkin build --get-env monolidar_fusion | catkin env -si  /usr/bin/cmake /home/farid/catkin_ws/src/mono_lidar_depth/monolidar_fusion --no-warn-unused-cli -DCATKIN_DEVEL_PREFIX=/home/farid/catkin_ws/devel/.private/monolidar_fusion -DCMAKE_INSTALL_PREFIX=/home/farid/catkin_ws/install; cd -
........................................................................................................................................

I have also installed ceres from the link provided.

Do you have any idea what I am really missing in here?

Cheers mate;
Farid

Image source when runtime.

Hello,
Recently, I try to build your package with my robot but I have many problems when simulation.
I don't know what mean of "src/image", "tgt/image", "tgt/matches", "src/image" in demo_keyframe_bundle_adjustment_meta/launch/feature_matching.launch
Screenshot from 2020-03-25 20-05-49
I try to pass data of grayscale camera to topic sensor/camera/grayscale/left/image_rect and rgb camera to topic sensor/camera/color/left/image_rect_g. After push information to terminal, I only get above information. It not similar when run your rosbag. I think there are no feature matching.
Screenshot from 2020-03-25 20-12-32
Can you help me to solve this problem.

How to deactive semantic lables

Hi, I am really impressed with the LIMO. I see the #16 but I still don't know how to deactivate the semantic labels, could you update the repo to support non-semantic dataset? Thank you!

Build Error about pcl_ros

Hi,
thank u for sharing your excellent code !!!
But after "bash install_repos.sh" , i got this Error

Errors     << image_preproc_ros_tool:cmake /home/dlr/catkin_ws/logs_limo_release/image_preproc_ros_tool/build.cmake.000.log
CMake Error at /home/dlr/catkin_ws/src/mrt_cmake_modules/cmake/Modules/FindAutoDeps.cmake:80 (message):
  Package pcl_ros is specified for autodepend but cmake variables are not
  defined.  Did you resolve dependencies?
Call Stack (most recent call first):
  CMakeLists.txt:16 (find_package)

Can you help me solve this error?
Thanks in advance!!

build error

While running step 11/17 : RUN /bin/bash -c 'source /opt/ros/melodic/setup.bash && catkin build'
I met such a problem
Screenshot from 2020-06-25 02-53-56
and I have already installed the Eigen
2

How can I solve this bug?

poses out and rviz problem

Thanks for your great work!
But when I run the rviz node,there is no image presented,as listed:
2019-12-12 21-46-09屏幕截图
2019-12-12 21-47-50屏幕截图

and I want to know which published topic is the most accurated poses result, is the topic "/semantic_labels_nodelet_manager/bond"?

eigen error in mono_lidar

Hi, johannes,

Thanks for your work. I met such error when running roslaunch demo_keyframe_bundle_adjustment_meta kitti_standalone.launch with 04.bag.

...
Initialize DepthEstimator Post
DepthEstimator successful initialized
[ INFO] [1591597391.300192954, 0.520561176]: /gamma_correction_nodelet_left Gamma correction Entered callback!
[ INFO] [1591597391.301096608, 0.520561176]: /gamma_correction_nodelet_left gamma correction leaving callback!
[ INFO] [1591597391.460237276, 0.536702683]: Duration feature matching and tracking: 158 ms
size before randomization 124232
size after randomization 6000
Publish image projection cloud
[ INFO] [1591597391.503006156, 0.540724514]: Duration assign semantic labels=0 ms
[ INFO] [1591597391.511459588, 0.541729991]: Duration tracklet_depth_ros_tool=376 ms
size before randomization 124088
size after randomization 6000
Publish image projection cloud
[ INFO] [1591597392.208998584, 0.611303525]: Duration assign semantic labels=2 ms
[ INFO] [1591597392.210731384, 0.611303525]: Duration tracklet_depth_ros_tool=696 ms
mono_lidar: /usr/include/eigen3/Eigen/src/Core/DenseStorage.h:128: Eigen::internal::plain_array<T, Size, MatrixOrArrayOptions, 32>::plain_array() [with T = double; int Size = 16; int MatrixOrArrayOptions = 0]: Assertion `(internal::UIntPtr(eigen_unaligned_array_assert_workaround_gcc47(array)) & (31)) == 0 && "this assertion is explained here: " "http://eigen.tuxfamily.org/dox-devel/group__TopicUnalignedArrayAssert.html" " **** READ THIS WEB PAGE !!! ****"' failed.
================================================================================REQUIRED process [mono_lidar-20] has died!
process has died [pid 15517, exit code -6, cmd /home/magic/ros_wspace/limo_ws/devel/lib/keyframe_bundle_adjustment_ros_tool/mono_lidar __name:=mono_lidar __log:=/home/magic/.ros/log/8131c29a-a950-11ea-bc34-8c04ba998175/mono_lidar-20.log].
log file: /home/magic/.ros/log/8131c29a-a950-11ea-bc34-8c04ba998175/mono_lidar-20*.log
Initiating shutdown!
================================================================================
[ INFO] [1591597392.342114657, 0.624392962]: /gamma_correction_nodelet_left Gamma correction Entered callback!
[ INFO] [1591597392.343137421, 0.625400988]: /gamma_correction_nodelet_left gamma correction leaving callback!

Minimum Topics to get LIMO to run and what launch file to use?

LIMO seems to be quite large and I'd like to get it to work with my LIDAR and Camera as soon as possible. So what I did was playback 04.bag to see what topics are to be published and mimic that.

  1. I created 2 images, one black and white (image 1) and the other color (image 2). 04 bag seems to be stereo so what I did was publish left and right color with the same image (image 2), and left and right that's lack and white with the same image (image 1). topics: /sensor/camera/(color|grayscale)/(left|right)/image_rect, frame_ids:/sensor/camera/(color|grayscale)/(left|right)
  2. I published 4 camera infos. topics: /sensor/camera/(color|grayscale)/(left/right)/camera_info, frame_ids:/sensor/camera/(color|grayscale)/(left|right)
  3. I published 1 point cloud: topics: /sensor/velodyne/cloud_euclidean, frame_id = /sensor/velodyne

Is there anything else that I should do? Do I need a robot state publisher and a URDF too? If so, what would the xml look like?

At the moment, I'm using kitti_standalone.launch

Thanks

roslaunch error

roslaunch demo_keyframe_bundle_adjustment_meta kitti_standalone.launch

the error is: [ERROR] [1570804070.495489865]: "sensor/camera" passed to lookupTransform argument target_frame does not exist.

how to solve it?

Build Error..

Hi,
me again ~
after solved my last issue, i got this new Error

[build] Found '23' packages in 0.0 seconds.                                                                       
[build] Updating package table.                                                                                   
Warning: generated devel space setup files have been deleted.
Starting  >>> catkin_tools_prebuild                                                                               
__________________________________________________________________________________________________________________
Errors     << catkin_tools_prebuild:cmake /home/dlr/catkin_ws/logs_limo_release/catkin_tools_prebuild/build.cmake.000.log
CMake Error: The source directory "/home/dlr/catkin_ws/build_limo_release/catkin_tools_prebuild/-Werror=volatile-register-var" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
cd /home/dlr/catkin_ws/build_limo_release/catkin_tools_prebuild; catkin build --get-env catkin_tools_prebuild | catkin env -si  /home/dlr/anaconda3/envs/py27/bin/cmake /home/dlr/catkin_ws/build_limo_release/catkin_tools_prebuild --no-warn-unused-cli -DCATKIN_DEVEL_PREFIX=/home/dlr/catkin_ws/devel_limo_release/.private/catkin_tools_prebuild -DCMAKE_INSTALL_PREFIX=/home/dlr/catkin_ws/install_limo_release -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_CXX_FLAGS=-Wall -Wextra -Wno-unused-parameter -Werror=address -Werror=array-bounds=1 -Werror=bool-compare -Werror=comment -Werror=enum-compare -Werror=format -Werror=init-self -Werror=logical-not-parentheses -Werror=maybe-uninitialized -Werror=memset-transposed-args -Werror=nonnull -Werror=nonnull-compare -Werror=openmp-simd -Werror=parentheses -Werror=return-type -Werror=sequence-point -Werror=sizeof-pointer-memaccess -Werror=switch -Werror=tautological-compare -Werror=trigraphs -Werror=uninitialized -Werror=volatile-register-var; cd -
..................................................................................................................
Failed     << catkin_tools_prebuild:cmake                         [ Exited with code 1 ]                          
Failed    <<< catkin_tools_prebuild                               [ 0.3 seconds ]                                 
Abandoned <<< aloam_velodyne                                      [ Unrelated job failed ]                        
Abandoned <<< mrt_cmake_modules                                   [ Unrelated job failed ]                        
Abandoned <<< image_preproc                                       [ Unrelated job failed ]                        
Abandoned <<< matches_msg_depth_ros                               [ Unrelated job failed ]                        
Abandoned <<< matches_msg_ros                                     [ Unrelated job failed ]                        
Abandoned <<< matches_msg_types                                   [ Unrelated job failed ]                        
Abandoned <<< matches_msg_conversions_ros                         [ Unrelated job failed ]                        
Abandoned <<< monolidar_fusion                                    [ Unrelated job failed ]                        
Abandoned <<< robust_optimization                                 [ Unrelated job failed ]                        
Abandoned <<< keyframe_bundle_adjustment                          [ Unrelated job failed ]                        
Abandoned <<< rosinterface_handler                                [ Unrelated job failed ]                        
Abandoned <<< image_preproc_ros_tool                              [ Unrelated job failed ]                        
Abandoned <<< matches_conversion_ros_tool                         [ Unrelated job failed ]                        
Abandoned <<< util_nodes_tf2_ros_tool                             [ Unrelated job failed ]                        
Abandoned <<< viso2                                               [ Unrelated job failed ]                        
Abandoned <<< feature_tracking_core                               [ Unrelated job failed ]                        
Abandoned <<< tracklets_depth_ros_tool                            [ Unrelated job failed ]                        
Abandoned <<< viso_feature_tracking_ros_tool                      [ Unrelated job failed ]                        
Abandoned <<< keyframe_bundle_adjustment_ros_tool                 [ Unrelated job failed ]                        
Abandoned <<< demo_keyframe_bundle_adjustment_meta                [ Unrelated job failed ]                        
[build] Summary: 0 of 21 packages succeeded.                                                                      
[build]   Ignored:   3 packages were skipped or are blacklisted.                                                  
[build]   Warnings:  None.                                                                                        
[build]   Abandoned: 20 packages were abandoned.                                                                  
[build]   Failed:    1 packages failed.

my environment:

ubuntu 16.04  ROS kinetic
python 2.7

Can you help me solve this error?
Thanks in advance!!

How to estimate the result

Thank you for your great work!

I wonder how to estimate the result after run this code.

As far as I know, estimated pose result is saved in forms of "test.txt" so that it can be run with kitti devkit_odometry

However, I cannot find anything after the sequence is done.

I guess, there should be something I miss.

Please share your experience!

Thank you

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.