# vision_visp

**Repository Path**: huaaoyang/vision_visp

## Basic Information

- **Project Name**: vision_visp
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: GPL-2.0
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 1
- **Created**: 2021-11-21
- **Last Updated**: 2023-05-11

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

ViSP stack for ROS
==================

![GPL-2](https://www.gnu.org/graphics/gplv3-127x51.png)

`vision_visp` provides ViSP algorithms as ROS components. [ViSP]
[visp] is the Visual Servoing Platform and [ROS] [ros] a robotics
middleware.

These packages are released under the [GPL-2](COPYING) license.


Components documentation is hosted on the [ros.org wiki] [vision_visp-wiki].

Support is provided through [ROS Answers] [vision_visp-answers] .


Which branch should I use?
--------------------------

Branches come in two flavors:

 * development branch,
 * release branch

Package for each ROS release is maintained on separate
branches. I.e. `melodic-devel` is the Melodic Morenia development branch whereas
`melodic` is the Melodic Morenia release branch.

`master` means the next ROS release.

If you are a user you should use a release branch as they contain
stable and tested versions of the packages. If you are a developper
you must provide new patches against `master`. You may also provide
version-specific bug fix again older releases.


 - Never implement new features in old branches (i.e. not
   master). These Pull Requests will not be accepted. If you provide a
   bug fix then you may ask for it to be backported. ABI/API breakage
   prevent patches from being backported.
 - The *only* action allowed in release branches is merging the
   development branch in the current branch.


*Warning:* the Fuerte branches still rely on the legacy `rosbuild`
 build system. We recommend you to update to a newer ROS release. Only
 minimum maintained will be done for this release.


Additional development guidelines are provided in
[CONTRIBUTING.md](CONTRIBUTING.md).



Build Status
------------

This stack supports the following ROS releases:

 * Hydro
 * Groovy
 * Fuerte
 * Indigo
 * Jade
 * Kinetic
 * Lunar
 * Melodic
 * Noetic

The master branch holds the development that will be available in the
next ROS release.


| ROS Release   | Development Branch           | Release Branch |
| ------------- | ---------------------------- | -------------- |
| Master        | [![Build Status](https://travis-ci.org/lagadic/vision_visp.png?branch=master)](https://travis-ci.org/lagadic/vision_visp) | N/A |
| Melodic       | [![Build Status](https://travis-ci.org/lagadic/vision_visp.png?branch=melodic-devel)](https://travis-ci.org/lagadic/vision_visp) | [![Build Status](https://travis-ci.org/lagadic/vision_visp.png?branch=melodic)](https://travis-ci.org/lagadic/vision_visp) |
| Lunar         | [![Build Status](https://travis-ci.org/lagadic/vision_visp.png?branch=lunar-devel)](https://travis-ci.org/lagadic/vision_visp) | [![Build Status](https://travis-ci.org/lagadic/vision_visp.png?branch=lunar)](https://travis-ci.org/lagadic/vision_visp) |
| Kinetic       | [![Build Status](https://travis-ci.org/lagadic/vision_visp.png?branch=kinetic-devel)](https://travis-ci.org/lagadic/vision_visp) | [![Build Status](https://travis-ci.org/lagadic/vision_visp.png?branch=kinetic)](https://travis-ci.org/lagadic/vision_visp) |



[visp]: https://visp.inria.fr
[ros]: http://www.ros.org
[vision_visp-wiki]: http://wiki.ros.org/vision_visp
[vision_visp-answers]: http://answers.ros.org/questions/scope:all/sort:activity-desc/tags:vision_visp/page:1/