From 750ec3da17d96e1f6b82267af1880de3f078ff95 Mon Sep 17 00:00:00 2001 From: Hilary James Oliver Date: Wed, 19 Feb 2025 14:29:12 +1300 Subject: [PATCH] Applied more review suggestions. --- src/7-to-8/major-changes/scheduling.rst | 6 +++--- src/user-guide/running-workflows/reflow.rst | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/src/7-to-8/major-changes/scheduling.rst b/src/7-to-8/major-changes/scheduling.rst index 2201c7f84c..f0484e3a02 100644 --- a/src/7-to-8/major-changes/scheduling.rst +++ b/src/7-to-8/major-changes/scheduling.rst @@ -26,9 +26,9 @@ Cylc 8 has a new scheduling algorithm that: - Is much more efficient because it doesn't need to track as many waiting and succeeded tasks. - - waiting tasks are not pre-spawned before they are needed - - succeeded tasks are not retained across the :term:`active window` - - no costly indiscriminate dependency matching is done + - Tasks are not pre-spawned before they are needed. + - Tasks are not retained when they succeed. + - No costly indiscriminate dependency matching is done. - Distinguishes between :term:`optional ` and :term:`required ` task outputs, to support: diff --git a/src/user-guide/running-workflows/reflow.rst b/src/user-guide/running-workflows/reflow.rst index 3f8502cea9..00abf00813 100644 --- a/src/user-guide/running-workflows/reflow.rst +++ b/src/user-guide/running-workflows/reflow.rst @@ -122,8 +122,8 @@ Triggering with No Active Flows same as if you had triggered the task just before the workflow completed. Special Case: Triggering ``n=0`` (:term:`active window`) Tasks - Tasks in the :term:`active window` already have flow membership assigned - (namely that of the parent tasks that spawned them). + Tasks in the :term:`active window` already have flow membership assigned. + Flow numbers are inherited from parent (upstream) tasks in the graph. - Triggering a task with a submitted or running job has no effect (it is already triggered).