Skip to content

Commit 89d5ed4

Browse files
Update _docs/concepts/client_library/real-time_executor/index.md
Co-Authored-By: Ralph Lange <ralph-lange@users.noreply.github.com>
1 parent 636cf90 commit 89d5ed4

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • _docs/concepts/client_library/real-time_executor

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -127,7 +127,7 @@ However, data consistency is often an issue when preemptive scheduling is used a
127127

128128
Figure 3: Data communication without and with Logical Execution Time paradigm.
129129

130-
An Example of the LET-concept is shown in Figure 2. Assume that two processes are communicating data via one global variable. The timepoint when this data is written is at the end of the processing time. In the default case (left side), the process p<sub>3</sub> and p<sub>4</sub> receive the update. At the right side of the figure, the same scenario is shown with LET-semantics. Here, the data is communicated only at period boundaries. In this case, the lower process communicates at the end of the period, so that always process p<sub>3</sub> and p<sub>5</sub> receive the new data.
130+
An Example of the LET concept is shown in Figure 3. Assume that two processes are communicating data via one global variable. The timepoint when this data is written is at the end of the processing time. In the default case (left side), the process p<sub>3</sub> and p<sub>4</sub> receive the update. At the right side of the figure, the same scenario is shown with LET semantics. Here, the data is communicated only at period boundaries. In this case, the lower process communicates at the end of the period, so that always process p<sub>3</sub> and p<sub>5</sub> receive the new data.
131131

132132
The described embedded use case relies on the following concepts:
133133
- periodic execution of processes

0 commit comments

Comments
 (0)