| Platform | CI Status |
|---|---|
| Linux (Focal) |  |
| Linux (Unstable) |  |
| Windows |  |
| Lint (Clang-Format) |  |
| Lint (CMake-Format) |  |
| Lint (Clang-Tidy) |  |
| Lint (CodeCov) | |
This include packages related to both motion and process planning for the Tesseract Motion Planning Environment.
- tesseract_motion_planners – This package contains a common interface for Planners and includes implementation for OMPL, TrajOpt, TrajOpt IFOPT and Descartes.
- tesseract_process_managers – This package contains a common interface for Process Planning and includes implementation for a wide variaty of process found industrial automation like painting, griding, welding, pick and place and more.
- tesseract_time_parameterization – This package contains a time parameterization algorithms and includes iteritive spline.
The planning server is built leveraging the library taskflow which enables you to quickly write parallel and heterogeneous tasks programs which aligns well with process motion planning. These types of libraries leverage thread pools to quickly spin up different tasks as needed. One interesting thing found, if a task consumes a lot of memory, then the malloc library can make a performance decision to allow the thread to hold onto the memory it has for subsequent tasks opposed to giving the memory back to your system. This may be fine if this was the only set of tasks being run but typically in our use case there are other computationally intensive processes which could use this memory.
The recommended approach to address memory management is to leverage the tcmalloc library which is part of Google Performance Tools (gperftools). Experimentation has shown tcmalloc to provide more stable memory management when leveraging the planning server.
This capability can be leveraged by linking the exectuable that contains the planning server against tcmalloc using the following commands:
find_package(tesseract_common REQUIRED)
find_package(tcmalloc REQUIRED)
add_executable(my_executable src/my_executable.cpp)
target_link_libraries(my_executable PUBLIC tcmalloc::tcmalloc)This library provides a set of run-time tunables, leveraging a set of environment variables.
The one parameter that has been used to configure tcmalloc to give memory back to the OS is TCMALLOC_RELEASE_RATE:
TCMALLOC_RELEASE_RATE default: 1.0 Rate at which we release unused memory to the system, via madvise(MADV_DONTNEED), on systems that support it. Zero means we never release memory back to the system. Increase this flag to return memory faster; decrease it to return memory slower. Reasonable rates are in the range [0,10].
Note: This is typically set in the roslaunch file for the planning server node leveraging the <env name="TCMALLOC_RELEASE_RATE" value="10"> tag.
The great thing is, the default malloc library ptmalloc provides run-time tunables through a set of environment variables.
The one parameter that has been used to configure libc so it always gives back the memory to the system is setting following memory tunnable:
Tunable: glibc.malloc.mmap_threshold
export GLIBC_TUNABLES=glibc.malloc.mmap_threshold=1000000
This tunable supersedes the MALLOC_MMAP_THRESHOLD_ environment variable and is identical in features.
When this tunable is set, all chunks larger than this value in bytes are allocated outside the normal heap, using the mmap system call. This way it is guaranteed that the memory for these chunks can be returned to the system on free. Note that requests smaller than this threshold might still be allocated via mmap.
If this tunable is not set, the default value is set to ‘131072’ bytes and the threshold is adjusted dynamically to suit the allocation patterns of the program. If the tunable is set, the dynamic adjustment is disabled and the value is set as static.
Note: This is typically set in the roslaunch file for the planning server node leveraging the <env name="GLIBC_TUNABLES" value="glibc.malloc.mmap_threshold=1000000"> tag.
TBD
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
- Clone repository into your workspace
- Clone the repositories in the dependencies.repos file using vcstool or some other method (e.g. manually git cloning them)
- Build the workspace using catkin tools, colcon, or a similar tool
NOTE: To speed up clean build you may want to add tesseract_ext to an extended workspace.
NOTE: Melodic install TaskFlow from ROS-Industrial PPA.
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.
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.
Tesseract packages use ctest because it is ROS agnostic, so to run the test call catkin test --no-deps tesseract_motion_planners tesseract_process_managers tesseract_time_parameterization
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.
- LCOV_EXCL_LINE
- Lines containing this marker will be excluded.
- LCOV_EXCL_START
- Marks the beginning of an excluded section. The current line is part of this section.
- LCOV_EXCL_STOP
- 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.
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.
cd gh_pages
sphinx-build . output
Now open gh_pages/output/index.rst and remove output directory before commiting changes.
- Search Directories CI
- dir /s /b c:\opt\ros\noetic*assimp*
- Location of ROS Windows Builds