Please could you update the advice for family-family triggering to make use of skip mode.

https://cylc.github.io/cylc-doc/stable/html/workflow-design-guide/efficiency.html#family-to-family-triggering

Worth skimming the docs to see if we document any other dummy task use cases anywhere.

Please could you update the advice for family-family triggering to make use of skip mode.

https://cylc.github.io/cylc-doc/stable/html/workflow-design-guide/efficiency.html#family-to-family-triggering

Worth skimming the docs to see if we document any other dummy task use cases anywhere.

Good call: I've realized responding to Ronnie's comments that we've somewhat overloaded the term dummy to mean

• A task formally following the dummy task submission pathway
• An informal dummy mode task (i.e. an implicit task) or a task with script = true.
• A task which is a "dummy" with respect to it's graphing function. It can't be a true dummy task, but it could be a dummy like live task as described above, or a task carrying our some real work.

I've tried to remove either of the second two use cases for the word dummy.

I also found two references to "dummy-local" mode which hasn't been a thing for at least 3 years (I deleted it).

Good call: I've realized responding to Ronnie's comments that we've somewhat overloaded the term dummy to mean

Repeating my comment from the cylc-flow PR:

IMO opinion a "dummy task" is just a task that has no purpose beyond its role in the graph structure, i.e. it does not run a job that does anything useful at all. So dummy mode and simulation mode (and now skip mode) both (all) run dummy tasks.

However, it is potentially a bit confusing given the distinct mode names.

Now that we have (presumably) made simulation mode a lot more robust and useful ... can we consider ditching dummy mode? (we did discuss this somewhere once...). I'll put this question on the meeting agenda...

Either way, we should get the terminology straight and document it.

I've tried to respond to comments from @MetRonnie and @hjoliver (if you're both saying the same thing I'll run with it).

After a certain amount of thought I've restored the references to dummy tasks and added some disambiguation in the glossary.

I've also renamed the two main files to reflect the difference between workflow and task run modes. To this end 4d9f535 contains actual changes, whilst 7408002 is just the file renaming.