Skip to content

Commit 51433c0

Browse files
authored
Tidy placement of admonition (#802)
1 parent 347efa1 commit 51433c0

File tree

1 file changed

+10
-12
lines changed

1 file changed

+10
-12
lines changed

src/user-guide/writing-workflows/parameterized-tasks.rst

Lines changed: 10 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -112,25 +112,23 @@ Any number of parameters can be used at once. This parameterization:
112112
model<run,obs> # for run = 1..2 and obs = ship, buoy, plane
113113
model<run><obs> # Alternatively, from Cylc 8.2.0
114114
115-
.. versionadded:: 8.2.0
116-
117-
From this version you can also use the equivalent ``model<run><obs>``
118-
syntax. This allows more flexibility in templating: You can now construct
119-
names like ``beginning<run>middle<obs>end``.
120-
121-
.. note::
122-
123-
Before Cylc 8.2.0 this syntax worked in many cases, but was
124-
not formally supported, and failed if used in the names of
125-
:ref:`families<families_and_parameters>`.
126-
127115
expands to these tasks names:
128116

129117
.. code-block:: none
130118
131119
model_run1_ship, model_run1_buoy, model_run1_plane,
132120
model_run2_ship, model_run2_buoy, model_run2_plane
133121
122+
.. note::
123+
124+
The ``model<run><obs>`` syntax was introduced in Cylc 8.2.0.
125+
This allows more flexibility in templating; you can now construct
126+
names like ``beginning<run>middle<obs>end``.
127+
Before Cylc 8.2.0 this syntax worked in many cases, but was
128+
not formally supported, and failed if used in the names of
129+
:ref:`families<families_and_parameters>`.
130+
131+
134132
Here's a simple but complete example workflow:
135133

136134
.. code-block:: cylc

0 commit comments

Comments
 (0)