SVO-SLAM environment setup guide
Installation: Plain CMake (No ROS)
First, create a working directory such as: workspace, and then perform the following needs in this directory.
(tip: Be sure not to use Chinese names, even though your system has the default Chinese name. Otherwise, the following dependencies will be very difficult, and cmake cannot find the configuration file.)
mkdir workspace cd workspace
Boost - c Librairies (thread and system are needed)
sudo apt-<span style="color: #0000ff;">get</span> install libboost-all-dev
Eigen 3 - Linear algebra
apt-<span style="color: #0000ff;">get</span> install libeigen3-dev
OpenCV - Computer vision library for loading and displaying images (I downloaded OpenCV3.0)
<span style="color: #000000;">mkdir build cd build cmake .. make</span>
Sophus - Lie groups
<span style="color: #000000;">cd workspace git clone https:</span><span style="color: #008000;">//</span><span style="color: #008000;">github.com/strasdat/Sophus.git</span> <span style="color: #000000;">cd Sophus git checkout a621ff mkdir build cd build cmake .. make</span>
If you encounter the error "unit_complex_.imag() = 0." at this time, you need to change the code to: "unit_complex_.imag(0.)"
Fast - Corner Detector
<span style="color: #000000;">cd workspace git clone https:</span><span style="color: #008000;">//</span><span style="color: #008000;">github.com/uzh-rpg/fast.git</span> <span style="color: #000000;">cd fast mkdir build cd build cmake .. make</span>
g2o - General Graph Optimization OPTIONAL
Be patient and careful. The dependencies of each version of G2O are very complicated, so you need to be patient and look at the version number. Otherwise, there will be many mistakes and you will be confused. I read a lot of blogs on the Internet before, but they didn't really solve the problem of dependencies. Below I compile the process I did, complete and correct version.
First install g2o’s dependencies:
sudo apt-<span style="color: #0000ff;">get</span> install cmake libeigen4-dev libsuitesparse-dev, qt4-qmake libqglviewer-dev libsuitesparse-dev libcxsparse3.<span style="color: #800080;">1.2</span> libcholmod-dev
Then download, compile, etc.:
<span style="color: #000000;">cd workspace git clone https:</span><span style="color: #008000;">//</span><span style="color: #008000;">github.com/RainerKuemmerle/g2o.git</span> <span style="color: #000000;">cd g2o mkdir build cd build cmake .. make sudo make install</span>
vikit_common - Some useful tools that we need
vikit contains the camera model, some mathematics and interpolation functions required by SVO.
<span style="color: #000000;">cd workspace git clone https:</span><span style="color: #008000;">//</span><span style="color: #008000;">github.com/uzh-rpg/rpg_vikit.git</span>
Set USE_ROS to FALSE. in the pg_vikit/vikit_common/CMakeLists.txt
filecd rpg_vikit/<span style="color: #000000;">vikit_common mkdir build cd build cmake .. make</span>
SVO
<span style="color: #000000;">cd workspace git clone https:</span><span style="color: #008000;">//</span><span style="color: #008000;">github.com/uzh-rpg/rpg_svo.git</span> cd rpg_svo/svo
In the file svo/CMakeLists.txt, set USE_ROS to FALSE.
<span style="color: #000000;">mkdir build cd build cmake .. make</span>
Run SVO without ROS
First, create a folder to store your data:
mkdir Datasets
Then set an environment variable to store the path
export SVO_DATASET_DIR=${HOME}/Datasets
Execute the script .bashrc, and then go to the new folder to download the test data
source ~/<span style="color: #000000;">.bashrc cd ${SVO_DATASET_DIR} wget http:</span><span style="color: #008000;">//</span><span style="color: #008000;">rpg.ifi.uzh.ch/datasets/sin2_tex2_h1_v8_d.tar.gz -O - | tar -xz</span>
Then run SVO on the test data:
cd svo/<span style="color: #000000;">bin .</span>/test_pipeline
The above is the detailed content of SVO-SLAM environment setup guide. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

The key differences between CentOS and Ubuntu are: origin (CentOS originates from Red Hat, for enterprises; Ubuntu originates from Debian, for individuals), package management (CentOS uses yum, focusing on stability; Ubuntu uses apt, for high update frequency), support cycle (CentOS provides 10 years of support, Ubuntu provides 5 years of LTS support), community support (CentOS focuses on stability, Ubuntu provides a wide range of tutorials and documents), uses (CentOS is biased towards servers, Ubuntu is suitable for servers and desktops), other differences include installation simplicity (CentOS is thin)

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

Docker uses Linux kernel features to provide an efficient and isolated application running environment. Its working principle is as follows: 1. The mirror is used as a read-only template, which contains everything you need to run the application; 2. The Union File System (UnionFS) stacks multiple file systems, only storing the differences, saving space and speeding up; 3. The daemon manages the mirrors and containers, and the client uses them for interaction; 4. Namespaces and cgroups implement container isolation and resource limitations; 5. Multiple network modes support container interconnection. Only by understanding these core concepts can you better utilize Docker.

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)

VS Code To switch Chinese mode: Open the settings interface (Windows/Linux: Ctrl, macOS: Cmd,) Search for "Editor: Language" settings Select "Chinese" in the drop-down menu Save settings and restart VS Code

VS Code is the full name Visual Studio Code, which is a free and open source cross-platform code editor and development environment developed by Microsoft. It supports a wide range of programming languages and provides syntax highlighting, code automatic completion, code snippets and smart prompts to improve development efficiency. Through a rich extension ecosystem, users can add extensions to specific needs and languages, such as debuggers, code formatting tools, and Git integrations. VS Code also includes an intuitive debugger that helps quickly find and resolve bugs in your code.
