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
/** Tile regimes are the cartesian product of the following two state vectors:
2
+
State vector 1:
3
+
running: means that at the time the run loop executed, there was no upstream message I/O for the tile to handle.
4
+
processing: means that at the time the run loop executed, there was one or more messages for the tile to consume.
5
+
stalled: means that at the time the run loop executed, a downstream consumer of the messages produced by this tile is slow or stalled, and the message link for that consumer has filled up. This state causes the tile to stop processing upstream messages.
6
+
7
+
State Vector 2:
8
+
maintenance: the portion of the run loop that executes infrequent, potentially CPU heavy tasks
9
+
routine: the portion of the run loop that executes regularly, regardless of the presence of incoming messages
10
+
handling: the portion of the run loop that executes as a side effect of an incoming message from an upstream producer tile
11
+
*/
12
+
exportconstregimes=[
13
+
"running_maintenance",
14
+
"processing_maintenance",
15
+
"stalled_maintenance",
16
+
"running_routine",
17
+
"processing_routine",
18
+
"stalled_routine",
19
+
"running_handling",
20
+
"processing_handling",
21
+
// "stalled_handling" is an impossible state, and is therefore excluded
0 commit comments