VINS-Mono | Versatile Monocular Visual-Inertial State Estimator | Robotics library

by HKUST-Aerial-Robotics C++ Version: Current License: GPL-3.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | VINS-Mono Summary

VINS-Mono is a C++ library typically used in Automation, Robotics applications. VINS-Mono has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has medium support. You can download it from GitHub.

A Robust and Versatile Monocular Visual-Inertial State Estimator

Support

Quality

Security

License

Reuse

Support

VINS-Mono has a medium active ecosystem.

It has 4227 star(s) with 1969 fork(s). There are 221 watchers for this library.

It had no major release in the last 6 months.

There are 259 open issues and 154 have been closed. On average issues are closed in 213 days. There are 6 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of VINS-Mono is current.

Quality

VINS-Mono has no bugs reported.

Security

VINS-Mono has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

VINS-Mono is licensed under the GPL-3.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

VINS-Mono releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of VINS-Mono

Get all kandi verified functions for this library.

VINS-Mono Key Features

No Key Features are available at this moment for VINS-Mono.

VINS-Mono Examples and Code Snippets

No Code Snippets are available at this moment for VINS-Mono.

Community Discussions

Trending Discussions on VINS-Mono

OpenCV "not a member of 'cv'" errors while trying to compile some code

QUESTION

OpenCV "not a member of 'cv'" errors while trying to compile some code

Asked 2020-Dec-14 at 18:56

I was trying to compile the following visual odometry library: https://github.com/HKUST-Aerial-Robotics/VINS-Mono but in attempting to do so with OpenCV 4.0, I'm getting several "error: 'x' is not a member of 'cv' errors. There were several of these involving things like RGB2GRAY that I was able to Google and figure out how to update, but there's a couple errors remaining that I haven't been able to figure out how to update. These are as follows:

error: 'SHAPE_CROSS' is not a member of 'cv'
error: 'SHAPE_RECT' is not a member of 'cv'
error: 'TERMCRIT_EPS' is not a member of 'cv'
error: 'TERMCRIT_ITER' is not a member of 'cv'

Would anyone know what the fixes for these would be for OpenCV 4.0? Thanks in advance.

...

ANSWER

Answered 2020-Dec-14 at 18:56

Found my solution after some more Googling:

CV_SHAPE_CROSS --> cv::MORPH_CROSS

CV_SHAPE_RECT --> cv::MORPH_RECT

CV_TERMCRIT_EPS --> cv::TermCriteria::EPS

CV_TERMCRIT_ITER --> cv::TermCriteria::MAX_ITER

Source https://stackoverflow.com/questions/65289739

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install VINS-Mono

Clone the repository and catkin_make:.

Support

To further facilitate the building process, we add docker in our code. Docker environment is like a sandbox, thus makes our code environment-independent. To run with docker, first make sure ros and docker are installed on your machine. Then add your account to docker group by sudo usermod -aG docker $YOUR_USER_NAME. Relaunch the terminal or logout and re-login if you get Permission denied error, type:. Note that the docker building process may take a while depends on your network and machine. After VINS-Mono successfully started, open another terminal and play your bag file, then you should be able to see the result. If you need modify the code, simply run ./run.sh LAUNCH_FILE_NAME after your changes.

Find more information at: