niklas/ros2_tracing
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Rename 'Tools' section to 'Tools packages'

Browse source
This commit is contained in:
Christophe Bedard 2019-08-09 10:14:49 +02:00
parent fd203e83e3
commit a833e1c651
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/design_ros_2.md
View file

@ -31,7 +31,7 @@ Design document for ROS 2 tracing, instrumentation, and analysis effort.
1. [Timeline](#timeline) 1. [Timeline](#timeline)
2. [Notes on client libraries](#notes-on-client-libraries) 2. [Notes on client libraries](#notes-on-client-libraries)
3. [ROS 1/2 compatibility](#ros-12-compatibility) 3. [ROS 1/2 compatibility](#ros-12-compatibility)
6. [Tools](#tools) 6. [Tools packages](#tools-packages)
7. [Analysis architecture](#analysis-architecture) 7. [Analysis architecture](#analysis-architecture)
## Introduction ## Introduction
@ -549,7 +549,7 @@ This effort should first focus on `rcl` and `rclcpp` , but `rclpy` should eventu
We could look into making analyses work on both ROS 1 and ROS 2, through a common instrumentation interface (or other abstraction). We could look into making analyses work on both ROS 1 and ROS 2, through a common instrumentation interface (or other abstraction).
## Tools ## Tools packages
* `tracetools_trace` * `tracetools_trace`
* wraps the LTTng Python bindings to setup and start a tracing session * wraps the LTTng Python bindings to setup and start a tracing session