Skip to content

Commit 15b7fbc

Browse files
committed
minor improvements.
1 parent 1084118 commit 15b7fbc

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

  • _docs/concepts/client_library/execution_management

_docs/concepts/client_library/execution_management/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,7 @@ Currently, such a processing order cannot be defined with the default ROS2 Execu
138138
For this sense-plan-act pattern, we could define one executor for each phase. The plan-phase would be triggered only when all callbacks in the sense-phase have finished.
139139

140140
**Derived requirements:**
141-
- triggered execution of callbacks
141+
- triggered execution
142142

143143
### Synchronization of multiple rates
144144

@@ -241,7 +241,7 @@ An Example of the LET concept is shown in Figure 3. Assume that two processes ar
241241
While periodic activation is possible in ROS2 by using timers, preemptive scheduling is supported by the operating system and assigning priorities on the granularity of threads/processes that correspond to the ROS nodes; it is not possible to sequentially execute callbacks, which have no data-dependency. Furthermore data is read from the DDS queue just before the callback is executed and data is written sometime during the time the application is executed. While the `spin_period` function of the rclcpp Executor allows to check for data at a fixed period and executing those callbacks for which data is available, however, with this spin-function does not execute all callbacks irrespective wheter data is available or not. So `spin_period` is not helpful to periodically execute a number of callbacks (aka tasks within a process). So we need a mechanism that triggers the execution of multiple callbacks (aka tasks) based on a timer. Data transmission is achieved via DDS which does not allow to implement a LET-semantics. To summarize, we derive the following requirements:
242242

243243
**Derived requirements:**
244-
- trigger the execution of multiple callbacks
244+
- trigger the execution
245245
- sequential processing of callbacks
246246
- data synchronization with LET semantics
247247

@@ -261,7 +261,7 @@ The rclc Executor is feature-complete, i.e. it supports all event types as the d
261261
- lifecycle
262262

263263
The flexible rclc Executor provides on top the following new features:
264-
- trigger for conditional execution
264+
- triggered execution
265265
- user-defined sequential execution
266266
- multi-threading and scheduling configuration (WIP)
267267
- LET-semantics for data synchronization of periodic process scheduling

0 commit comments

Comments
 (0)