So far we have covered:
Rose suite configurations.
The relationship between them is as follows:
Cylc workflows can have Rose applications. These are stored in an
directory and are configured using a
We have learned the following Cylc commands:
Draws the suite’s graph.
flow.cylcfile and prints it back out.
Validates the Cylc
flow.cylcfile to check for any obvious errors.
Runs a suite.
Stops a suite, in a way that:
Kills all running/submitted tasks.
Leaves all running/submitted tasks running.
Starts a suite, picking up where it left off from the previous run.
We have learned the following Rose commands:
Rose contains some utilities to make life easier:
- rose date
A utility for parsing, manipulating and formatting date-times which is useful for working with the Cylc cycle point:
$ rose date 2000 --offset '+P1Y1M1D' 2001-02-02T0000Z $ rose date $CYLC_TASK_CYCLE_POINT --format 'The month is %B.' The month is April.
See the date-time tutorial for more information.
Rose Built-In Applications
Along with Rose utilities there are also Rose built-in applications.
A template for running the
Runs the rose-ana analysis engine.
Provides a generic solution to configure site-specific archiving of suite files.
For the running of multiple command variants in parallel under a single job.
A framework for housekeeping a cycling suite.
- Further Topics
Tutorials going over some of the more specific aspects of Rose not covered in the main tutorial.
- Command Reference
Contains the command-line documentation (also obtainable by calling
- Rose Configuration
The possible settings which can be used in the different Rose configuration files.
- Cylc workflow Design Guide
Contains recommended best practice for the style and structure of Cylc suites.