Summary

Suite Structure

So far we have covered:

The relationship between them is as follows:

Cylc workflows can have Rose applications. These are stored in an app directory and are configured using a rose-app.conf file.

We have learned the following Cylc commands:

cylc graph

Draws the suite’s graph.

cylc config

Processes the flow.cylc file and prints it back out.

cylc validate

Validates the Cylc flow.cylc file to check for any obvious errors.

cylc play

Runs a suite.

cylc stop

Stops a suite, in a way that:

cylc restart

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:

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.

Along with Rose utilities there are also Rose built-in applications.

fcm_make: A template for running the fcm make command.
rose_ana: Runs the rose-ana analysis engine.
rose_arch: Provides a generic solution to configure site-specific archiving of suite files.
rose_bunch: For the running of multiple command variants in parallel under a single job.
rose_prune: 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 --help).
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.