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: docs/sections/user_guide/yaml/rocoto.rst
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -172,6 +172,7 @@ Let's dissect the following task example:
172
172
envars:
173
173
person: siri
174
174
dependency:
175
+
hangdependency:
175
176
176
177
Each task is named by its UW YAML key. Blocks under ``tasks:`` prefixed with ``task_`` will be named with what follows the prefix. In the example above the task will be named ``hello`` and will appear in the XML like this:
177
178
@@ -197,7 +198,7 @@ The name of the task can be any string accepted by Rocoto as a task name (includ
197
198
<value>siri</value>
198
199
</envar>
199
200
200
-
``dependency:`` -- [Optional] Any number of dependencies accepted by Rocoto. This section is described in more detail below.
201
+
``dependency:`` and ``hangdependency`` -- [Optional] Any number of dependencies accepted by Rocoto. This section is described in more detail below.
201
202
202
203
The other keys not specifically mentioned here follow the same conventions as described in the :rocoto:`Rocoto<>` documentation.
203
204
@@ -274,6 +275,11 @@ The ``datadep_foo:`` and ``datadep_bar:`` UW YAML keys were named arbitrarily af
274
275
275
276
This example also demonstrates the use of Rocoto's **boolean operator tags** in the structured UW YAML, e.g., ``<or>``, ``<not>``, etc. The structure follows the tree in the Rocoto XML language in that each of the subelements of the ``<and>`` tag translates to a subtree in UW YAML. Multiple boolean operator tags can be set at the same level, just as with any other tag type, by adding a descriptive suffix starting with an underscore. In the above example, the ``and:`` key could have equivalently been named ``and_data_files:`` to achieve an identical Rocoto XML result.
276
277
278
+
``hangdependency:``
279
+
^^^^^^^^^^^^^^^^^^^
280
+
281
+
A ``hangdependency:`` block supports syntax identical to a ``dependency:`` block. Rocoto will interpret the resulting ``<hangdependency>`` XML element as specifying one or more conditions that, when satisfied, indicate that the task is hung and should be killed.
0 commit comments