File tree Expand file tree Collapse file tree 1 file changed +35
-0
lines changed Expand file tree Collapse file tree 1 file changed +35
-0
lines changed Original file line number Diff line number Diff line change @@ -132,6 +132,41 @@ The graph view now has an option to group tasks by cycle point.
132
132
.. image :: changes/cylc-graph-group-by-cycle-point.png
133
133
:width: 100%
134
134
135
+
136
+ Completion Expressions
137
+ ^^^^^^^^^^^^^^^^^^^^^^
138
+
139
+ When a task finishes, its outputs are validated against a "completion
140
+ expression" to ensure that it has produced all of its
141
+ :term: `required outputs <required output> `.
142
+ If a task fails this validation check it is said to have "incomplete outputs"
143
+ and will be retained in the :term: `active window ` pending user intervention.
144
+
145
+ This completion expression is generated automatically from the graph.
146
+ By default, tasks are expected to succeed, if you register any additional
147
+ required output in the graph, then these must also
148
+ be produced.
149
+
150
+ At Cylc 8.3.0 it is now possible to manually configure this completion
151
+ expression for finer control. This is particularly useful for anyone using
152
+ :term: `custom outputs <custom output> `.
153
+
154
+ For example, ``mytask `` must produce one of the outputs ``x `` or ``y `` to pass
155
+ the configured completion expression configured here:
156
+
157
+ .. code-block :: cylc
158
+
159
+ [runtime]
160
+ [[mytask]]
161
+ completion = succeeded and (x or y)
162
+ [[[outputs]]]
163
+ x = output-x
164
+ y = output-y
165
+
166
+ For more information, see the reference for the
167
+ :cylc:conf: `[runtime][<namespace>]completion ` configuration.
168
+
169
+
135
170
----------
136
171
137
172
Cylc 8.2
You can’t perform that action at this time.
0 commit comments