You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/docs/configuration/advanced/configuration-coupling-multi.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,11 +48,12 @@ Still, even with only explicit schemes, you can do very strange combinations. So
48
48
49
49
The mesh over which the data is communicated plays no role. We get a circular dependency:
50
50
51
-
```txt
52
-
A -- first to second --> B;
53
-
B -- first to second --> C;
54
-
C -- first to second --> A;
55
-
```
51
+
{% mermaid %}
52
+
graph LR
53
+
A -->|first to second| B
54
+
B -->|first to second| C
55
+
C -->|first to second| A
56
+
{% endmermaid %}
56
57
57
58
All three participants are a second participant in a serial coupling scheme, in which they receive data. Thus, they all wait for data in `initialize`, which is, however, only sent in the `advance` call of another participant, as explained on the [coupling flow pages](couple-your-code-coupling-flow.html).
0 commit comments