Various small proposed improvements

src/installation.rst

@@ -19,19 +19,6 @@ Cylc runs on Unix-like systems including Linux and Mac OS.
 Via Conda (recommended)
 ^^^^^^^^^^^^^^^^^^^^^^^
 
-.. tip::
-
-   We recommend using Mamba to install Cylc.
-   Mamba (or Micromamba) can be used as
-   `a faster, drop-in replacement for the conda command
-   <https://mamba.readthedocs.io/en/latest/index.html>`_.
-   If using Conda, make sure to use the libmamba-solver by updating to
-   Conda 23.10 or using the `conda-libmamba-solver plugin for conda
-   <https://conda.github.io/conda-libmamba-solver/getting-started/>`_.
-   The classic conda environment solver may be too slow for a complex package
-   like Cylc.
-
-
 .. code-block:: sub
 
    $ conda install -c conda-forge cylc-flow
@@ -67,7 +54,7 @@ Via Pip (+npm)
    $ pip install cylc-rose metomi-rose
 
 There are also certain optional extra requirements which you may choose to
-install:
+install (already included if installing via Conda):
 
 .. code-block:: sub
 
@@ -92,15 +79,16 @@ Non-Python Requirements
 .. _Graphviz: https://graphviz.org/download/
 .. _configurable-http-proxy: https://anaconda.org/conda-forge/configurable-http-proxy
 
-These dependencies are not installed by Conda or pip:
+These dependencies are not installed by Conda or pip and may not be available on your
+system by default:
 
 * ``bash``
 * GNU `coreutils`_
 * ``ssh``
 * ``rsync``
 * ``mail`` (optional - for automated email functionality)
 
-These dependencies are installed by Conda but not by pip:
+The following dependencies are installed automatically by Conda but not by pip:
 
 * `Graphviz`_ (optional - used by ``cylc graph`` for displaying workflow
   graphs)
@@ -290,8 +278,8 @@ can be found: :ref:`UI_Server_config`.
 Bash Profile
 ^^^^^^^^^^^^
 
-Cylc :term:`job scripts <job script>` are bash scripts, which is good for
-manipulating files and processes, They invoke ``bash -l`` to allow environment
+Cylc :term:`job scripts <job script>` are bash scripts, which are good for
+manipulating files and processes. They invoke ``bash -l`` to allow environment
 configuration in login scripts.
 
 .. warning::

src/tutorial/furthertopics/clock-triggered-tasks.rst

@@ -60,7 +60,7 @@ Paste the following code into a ``flow.cylc`` file:
            [[[events]]]
                mail events = failed
        [[bell]]
-           script = printf 'bong%.02d\n' $(seq 1 $(cylc cyclepoint --print-hour))
+           script = printf 'bong%.02d\n' $(seq 1 $(cylc cyclepoint --print-hour)); sleep 5
 
 Change the initial cycle point to 00:00 this morning (e.g. if it was
 the first of January 2000 we would write ``2000-01-01T00Z``).
@@ -78,7 +78,6 @@ Stop the workflow after a few cycles using ``cylc stop --now --now clock-trigger
 Notice how the tasks run as soon as possible rather than
 waiting for the actual time to be equal to the cycle point.
 
-
 Clock-Triggering Tasks
 ----------------------
 

src/tutorial/introduction.rst

@@ -88,10 +88,29 @@ Cylc can automatically:
 
 Cylc provides a variety of command line and GUI tools for visualising,
 monitoring, and controlling workflows. The Cylc TUI (Terminal
-User Interface), web GUI, and ``cylc scan`` (bottom left) are shown below.
+User Interface), web GUI, and ``cylc scan`` are shown below.
 
-.. image:: /tutorial/img/cylc-tools.png
-   :alt: A screenshot of several Cylc tools.
+**Placeholder Images Currently Used**
+
+.. tab-set::
+
+   .. tab-item:: GUI
+
+      .. image:: ../../src/img/cylc-ui-dash.png
+         :alt: A screenshot of the Cylc GUI dashboard.
+         :width: 75%
+
+   .. tab-item:: Tui
+
+      .. image:: ../../src/img/tui-1.png
+         :alt: A screenshot of the Cylc TUI.
+         :width: 75%
+
+   .. tab-item:: CLI
+
+      .. image:: ../../src/img/cylc-cli.png
+         :alt: A screenshot of the Cylc CLI.
+         :width: 75%
 
 .. nextslide::
 

src/tutorial/runtime/configuration-consolidation/families.rst

@@ -233,8 +233,9 @@ The ``root`` Family
 
 .. practical::
 
-   .. rubric:: This practical continues on from the
-      :ref:`jinja2 practical <cylc-tutorial-jinja2-practical>`.
+   .. rubric:: In this practical we will consolidate the configuration of the
+      :ref:`weather-forecasting workflow <tutorial-cylc-runtime-forecasting-workflow>`
+      from the previous section.
 
    1. **Create A New Workflow.**
 
@@ -251,7 +252,7 @@ The ``root`` Family
 
       .. code-block:: none
 
-         RESOLUTION = {{ RESOLUTION }}
+         RESOLUTION = 0.2
          DOMAIN = -12,46,12,61  # Do not change!
 
       Rather than manually adding them to each task individually we could put
@@ -266,7 +267,7 @@ The ``root`` Family
          +    [[root]]
          +        [[[environment]]]
          +            # The dimensions of each grid cell in degrees.
-         +            RESOLUTION = {{ RESOLUTION }}
+         +            RESOLUTION = 0.2
          +            # The area to generate forecasts for (lng1, lat1, lng2, lat2).
          +            DOMAIN = -12,46,12,61  # Do not change!
 
@@ -276,23 +277,23 @@ The ``root`` Family
               script = consolidate-observations
          -    [[[environment]]]
          -        # The dimensions of each grid cell in degrees.
-         -        RESOLUTION = {{ RESOLUTION }}
+         -        RESOLUTION = 0.2
          -        # The area to generate forecasts for (lng1, lat1, lng2, lat2).
          -        DOMAIN = -12,46,12,61  # Do not change!
 
           [[get_rainfall]]
               script = get-rainfall
-              [[[environment]]]
+         -    [[[environment]]]
          -        # The dimensions of each grid cell in degrees.
-         -        RESOLUTION = {{ RESOLUTION }}
+         -        RESOLUTION = 0.2
          -        # The area to generate forecasts for (lng1, lat1, lng2, lat2).
          -        DOMAIN = -12,46,12,61  # Do not change!
 
           [[forecast]]
               script = forecast 60 5  # Generate 5 forecasts at 60 minute intervals.
               [[[environment]]]
          -        # The dimensions of each grid cell in degrees.
-         -        RESOLUTION = {{ RESOLUTION }}
+         -        RESOLUTION = 0.2
          -        # The area to generate forecasts for (lng1, lat1, lng2, lat2)
          -        DOMAIN = -12,46,12,61  # Do not change!
                   # The path to the files containing wind data (the {variables} will
@@ -313,7 +314,7 @@ The ``root`` Family
               script = post-process exeter 60
          -    [[[environment]]]
          -        # The dimensions of each grid cell in degrees.
-         -        RESOLUTION = {{ RESOLUTION }}
+         -        RESOLUTION = 0.2
          -        # The area to generate forecasts for (lng1, lat1, lng2, lat2).
          -        DOMAIN = -12,46,12,61  # Do not change!
 

src/tutorial/runtime/configuration-consolidation/index.rst

@@ -73,8 +73,8 @@ structure of a workflow and avoid duplication.
 .. toctree::
    :maxdepth: 1
 
-   jinja2
    families
+   jinja2
    parameters
 
 
@@ -139,10 +139,12 @@ The Three Approaches
    could use them to simplify the workflow from the previous tutorial. *Work
    through them in order!*
 
-* :ref:`families <tutorial-cylc-families>`
-* :ref:`jinja2 <tutorial-cylc-jinja2>`
-* :ref:`parameters <tutorial-cylc-parameterization>`
+.. toctree::
+   :maxdepth: 1
 
+   families
+   jinja2
+   parameters
 
 .. _cylc-tutorial-consolidation-conclusion:
 

src/tutorial/runtime/configuration-consolidation/jinja2.rst

@@ -165,57 +165,54 @@ This would result in:
 
 .. ifslides::
 
-   Next section: :ref:`tutorial-cylc-families`
+   Next section: :ref:`tutorial-cylc-parameters`
 
 
 
 .. _cylc-tutorial-jinja2-practical:
 
 .. practical::
 
-   .. rubric:: In this practical we will consolidate the configuration of the
-      :ref:`weather-forecasting workflow <tutorial-cylc-runtime-forecasting-workflow>`
-      from the previous section.
+   .. rubric:: This practical continues on from the
+      :ref:`Families practical <cylc-tutorial-families-practical>`.
 
    3. **Use Jinja2 To Avoid Duplication.**
 
-      The ``RESOLUTION`` environment variable is used by multiple tasks.
-      Rather than writing it out multiple times we will use Jinja2
-      to centralise this configuration.
+      We have already consolidated the ``RESOLUTION`` environment variable
+      in the previous tutorial.  However, lets say we want to reference
+      the resolution elsewhere in the workflow, not just as an
+      environment variable.  For example, we might want to include the
+      resolution in a filename.  To achieve this, we can define a Jinja2
+      variable for the resolution, which can be used anywhere in the workflow.
 
-      At the top of the :cylc:conf:`flow.cylc` file add the Jinja2 shebang line. Then
-      copy the value of the ``RESOLUTION`` environment variable and use it to
-      define an ``RESOLUTION`` Jinja2 variable:
+      At the top of the :cylc:conf:`flow.cylc` file you should see the Jinja2
+      shebang line has been included for you.  Copy the value of the
+      ``RESOLUTION`` environment variable and use it to define a Jinja2 variable:
 
       .. code-block:: cylc
 
          #!Jinja2
 
          {% set RESOLUTION = 0.2 %}
 
-      Next replace the key, where it appears in the workflow, with
+      Next replace the key within the root definition with
       ``{{ RESOLUTION }}``:
 
       .. code-block:: diff
 
-         [[get_rainfall]]
-            script = get-rainfall
+         [[root]]
             [[[environment]]]
          -          RESOLUTION = 0.2
          +          RESOLUTION = {{ RESOLUTION }}
 
-         [[forecast]]
-            script = forecast 60 5  # Generate 5 forecasts at 60 minute intervals.
-            [[[environment]]]
-         -          RESOLUTION = 0.2
-         +          RESOLUTION = {{ RESOLUTION }}
+      And add a reference to the resolution in the MAP_FILE filename of the
+      ``forcast`` task:
 
-         [[post_process_exeter]]
-            # Generate a forecast for Exeter 60 minutes in the future.
-            script = post-process exeter 60
-            [[[environment]]]
-         -          RESOLUTION = 0.2
-         +          RESOLUTION = {{ RESOLUTION }}
+      .. code-block:: diff
+
+         -  MAP_FILE = "${CYLC_TASK_LOG_ROOT}-map.html"
+         +  MAP_FILE = "${CYLC_TASK_LOG_ROOT}-map-{{ RESOLUTION }}-resolution.html"
 
       Check the result with ``cylc config``. The Jinja2 will be processed
-      so you should not see any difference after making these changes.
+      so you should not see any difference after making these changes, other than
+      the MAP_FILE filename now including the resolution.

src/tutorial/runtime/configuration-consolidation/parameters.rst

@@ -182,7 +182,7 @@ Parameters can be either strings or integers:
 .. ifslides::
 
    .. rubric:: This practical continues on from the
-      :ref:`Families practical <cylc-tutorial-families-practical>`.
+      :ref:`Jinja2 practical <cylc-tutorial-jinja2-practical>`.
 
    Next section: :ref:`Which approach to use
    <cylc-tutorial-consolidation-conclusion>`
@@ -314,7 +314,7 @@ Parameters can be either strings or integers:
 
              [task parameters]
                  station = aldergrove, camborne, heathrow, shetland
-            +        site = exeter, edinburgh
+            +    site = exeter, edinburgh
 
          Next we parameterize the task in the graph:
 

src/tutorial/scheduling/integer-cycling.rst

@@ -71,7 +71,8 @@ To make a workflow repeat we must tell Cylc three things:
    * ``initial cycle point = 1`` tells Cylc to start counting cycle points
      from 1.
    * ``P1`` is the :term:`recurrence`; a ``P1`` :term:`graph string`
-     repeats at every integer :term:`cycle point`.
+     tells Cylc to repeat at every integer :term:`cycle point`
+     (whereas ``R1`` means "run once").
 
    The first three :term:`cycles<cycle>` look like this, with the entire
    workflow repeated at each cycle point:

src/user-guide/interventions/index.rst

@@ -113,7 +113,7 @@ Re-Run Multiple Tasks
          :width: 75%
 
    .. tab-item:: CLI
-      :sync: gui
+      :sync: cli
 
       .. code-block:: console