Skip to content

Commit d7ee6a4

Browse files
committed
fixed broken cross-references in Table Of contents - Hint: must use small letters
Signed-off-by: Staschulat Jan (CR/AEX3) <jan.staschulat@de.bosch.com>
1 parent 3d813c8 commit d7ee6a4

1 file changed

Lines changed: 12 additions & 10 deletions

File tree

  • _docs/concepts/client_library/real-time_executor

‎_docs/concepts/client_library/real-time_executor/index.md‎

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -4,19 +4,19 @@ redirect_from: /real-time_executor/
44
permalink: /docs/concepts/client_library/real-time_executor/
55
---
66

7-
7+
88
## Table of contents
99

10-
* [Introduction](#Introduction)
10+
* [Introduction](#introduction)
1111
* [ROS 2 Executor Concept](#ros-2-executor-concept)
1212
* [RCL Executor](#rcl-executor)
13-
* [ROS 2 Layers](#ROS-2-Layers)
13+
* [API Layers](#api-layers)
1414
* [Concept](#concept)
15-
* [API](#API)
16-
* [Tutorial and Download](#Tutorial-and-Download)
17-
* [Background](#Background)
18-
* [ROS 2 rclcpp Executor](#ROS-2-rclcpp-Executor)
19-
* [Complex semantic of the ROS 2 Executor](#Complex-semantic-of-the-ROS-2-Executor)
15+
* [API](#api)
16+
* [Tutorial and Download](#tutorial-and-download)
17+
* [Background](#background)
18+
* [ROS 2 rclcpp Executor](#ros-2-rclcpp-executor)
19+
* [Complex semantics of the ROS 2 Executor](#complex-semantics-of-the-ros-2-executor)
2020
* [Callback-group-level Executor](#callback-group-level-executor)
2121
* [Related Work](#related-work)
2222
* [Roadmap](#roadmap)
@@ -63,7 +63,7 @@ This section describes a let-executor. It is a first step towards deterministic
6363

6464
In the future, we plan to provide other executors with different deterministic semantics.
6565

66-
### ROS 2 Layers<a name="ROS-2-Layers"></a>
66+
### API Layers
6767
As mentioned in the section [Introduction to Client Library](../), we plan to provide micro-ROS support for the C++ API and for the C API. The Real-Time Executor enriches the C API based on the ROS Client Library (rcl).
6868

6969
### Concept
@@ -113,6 +113,8 @@ The let-executor can be downloaded from the micro-ROS GitHub [rcl_executor repos
113113

114114
## Background
115115

116+
In section we provide a detailed description of the ROS 2 rclcpp Executor, point-out its complex semantics and present the Callback-group-level executor.
117+
116118
### ROS 2 rclcpp Executor
117119

118120
Here we provide some more detail about the ROS 2 rclcpp Executor.
@@ -130,7 +132,7 @@ Also, the Executor does not maintain an explicit callback queue, but relies on t
130132
The Executor concept, however, does not provide means for prioritization or categorization of the incoming callback calls. Moreover, it does not leverage the real-time characteristics of the underlying operating-system scheduler to have finer control on the order of executions. The overall implication of this behavior is that time-critical callbacks could suffer possible deadline misses and a degraded performance since they are serviced later than non-critical callbacks. Additionally, due to the FIFO mechanism, it is difficult to determine usable bounds on the worst-case latency that each callback execution may incur.
131133

132134

133-
### Complex semantic of the ROS 2 Executor
135+
### Complex semantics of the ROS 2 Executor
134136

135137
In a recent paper [CB2019](#CB2019), the Executor of ROS 2 has been analyzed in detail and a response time analysis of cause-effect chains has been proposed under reservation-based scheduling. As described in the sub-section [ROS 2 rclcpp Executor](#ROS-2-rclcpp-Executor), the executor distinguishes four categories of callbacks: _timers_, which are triggered by sysetm-level timers, _subscribers_, which are triggered by new messages on a subscribed topic, _services_, which are triggered by service requests, and _clients_, which are triggered by responses to service requests. The executor is responsible for taking messages from the input queues of the DDS layer and executing the corresponding callback. Since it executes callbacks to completion, it is a non-preemptive scheduler, However it does not consider all ready tasks for execution, but only a snapshot, called readySet. This readySet is updated when the executor is idle and in this step it interacts with the DDS layer updating the set of ready tasks. Then for every type of task, there are dedicated queues (timers, subscriptions, services, clients) which are processed sequentially. The following key issues were pointed out:
136138
* The executor processes _timers_ always first. This can lead to the intrinsic effect, that in overload situations messages from the DDS queue are not processed

0 commit comments

Comments
 (0)