|CI status||No Continuous Integration|
|Tags||No category tags.|
Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)
The planning framework (Tesseract) was designed to be light weight, limiting the number of dependencies, mainly only using standard libraries like, eigen, boost, orocos and to the packages below. The core packages are ROS agnostic and have full python support.
Tesseract Setup Wizard and Visualization Tools
Tesseract Core Packages
- tesseract – This is the main class that manages the major component Environment, Forward Kinematics, Inverse Kinematics and loading from various data.
- tesseract_command_language – This package contains a generic command language to support motion and process planning similar to industrial teach pendants
- tesseract_collision – This package contains a common interface for collision checking prividing several implementation of a Bullet collision library and FCL collision library. It includes both continuous and discrete collision checking for convex-convex, convex-concave and concave-concave shapes.
- tesseract_common – This package contains common functionality needed by the majority of the packages.
- tesseract_environment – This package contains the Tesseract Environment which provides functionality to add,remove,move and modify links and joint. It also manages adding object to the contact managers and provides the ability.
- tesseract_geometry – This package contains geometry types used by Tesseract including primitive shapes, mesh, convex hull mesh, octomap and signed distance field.
- tesseract_kinematics – This package contains a common interface for Forward and Inverse kinematics for Chains, Trees and Graphs including implementation using KDL and OPW Kinematics.
- tesseract_scene_graph – This package contains the scene graph which is the data structure used to manage the connectivity of objects in the environment. It inherits from boost graph and provides addition functionality for adding,removing and modifying Links and Joints along with search implementation.
- tesseract_support – This package contains support data used for unit tests and examples throughout Tesseract.
- tesseract_visualization – This package contains visualization utilities and libraries.
How to create:
- Create Video:
gource -1280x720 -seconds-per-day 0.2 --auto-skip-seconds 0.2 --disable-bloom -background d0d3d4 --hide filenames,mouse,progress -o - | ffmpeg -y -r 60 -f image2pipe -vcodec ppm -i - -vcodec libx264 -preset ultrafast -pix_fmt yuv420p -crf 1 -threads 0 -bf 0 gource.mp4
- Create Gif:
ffmpeg -i gource.mp4 -r 10 -vf "scale=800:-1,split[s0][s1];[s0]palettegen[p];[s1][p]paletteuse" tesseract_evolution.gif
Warning: These packages are under heavy development and are subject to change.
See issue #66
1) Clone repository into your workspace 2) Clone the repositories in the dependencies.rosinstall file using wstool or some other method (e.g. manually git cloning them) 3) Build the workspace using catkin tools, colcon, or a similar tool
NOTE: For noetic tesseract_ext is not required. Install the following dependencies: libbullet-dev, libbullet-extras-dev and ros-noetic-fcl. Taskflow can be install using the PPA below.
NOTE: To speed up clean build you may want to add tesseract_ext to an extended workspace.
NOTE: Install TaskFlow from ROS-Industrial PPA.
Building with Clang-Tidy Enabled
Must pass the -DTESSERACT_ENABLE_CLANG_TIDY=ON to cmake when building. This is automatically enabled if cmake argument -DTESSERACT_ENABLE_TESTING_ALL=ON is passed.
Building Tesseract Tests
Must pass the -DTESSERACT_ENABLE_TESTING=ON to cmake when wanting to build tests. This is automatically enabled if cmake argument -DTESSERACT_ENABLE_TESTING_ALL=ON is passed.
NOTE: If you are building using catkin tools, use
catkin build --force-cmake -DTESSERACT_ENABLE_TESTING=ON.
Running Tesseract Tests
Tesseract packages use ctest because it is ROS agnostic, so to run the test call
catkin test --no-deps tesseract_collision tesseract_common tesseract_environment tesseract_geometry tesseract_kinematics tesseract_scene_graph tesseract_urdf tesseract_command_language
Building Tesseract Code Coverage
Must pass the -DTESSERACT_ENABLE_CODE_COVERAGE=ON to cmake when wanting to build code coverage. The code coverage report is located in each individuals build directory inside a ccov/all-merged folder. Open the index.html file to see the packages code coverage report.
NOTE: Must be a clean build when generating a code coverage report. Also must build in debug.
Exclude Code From Code Coverage
- Lines containing this marker will be excluded.
- Marks the beginning of an excluded section. The current line is part of this section.
- Marks the end of an excluded section. The current line not part of this section.
.. NOTE: You can replace LCOV above with GCOV or GCOVR.
Create Debian Package (Linux) or NuGet Package (Windows)
The following process will generate a Debian or NuGet package leveraging cmake and cpack based on the OS.
The package should be located in the current directory.
cd <workspace directory> catkin build -DCMAKE_BUILD_TYPE=Release -DTESSERACT_PACKAGE=ON ./src/tesseract/.run-cpack
.. NOTE: You can add a prefix to the package name by setting -DTESSERACT_PACKAGE_PREFIX="ros-noetic-".
Quality Tools Leverage
Tesseract currently leverages Compiler Warnigs, Clang Tidy and Code Coverage. All warnings produced by Compiler and Clang Tidy are treated as errors during CI builds.
- Clang Tidy
Documentation and Tutorials
Documentation and tutorials for Tesseract are located at https://github.com/tesseract-robotics/tesseract_docs.git
Debugging Windows Build
- Search Directories CI
- dir /s /b c:\opt\ros\noetic*assimp*
- Location of ROS Windows Builds
Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.