Version 27 (modified by annette, 5 years ago) (diff)

Useful information for running with Rose

See also (redirects to Collaboration Twiki):

Switching versions of Rose and/or cylc

  • On puma and MONSooN export the variables: CYLC_VERSION=x.y.z and ROSE_VERSION=YYYY.MM.DD
  • On Archer use module switch command. It is advisable to use the same versions of Rose and Cylc on puma and Archer.

Viewing the suite run graph without running

When developing suites, it can be useful to check what the run graph looks like after jinja evaluation etc. To do this without running the suite:

rose suite-run -i --name=puma-aa045  # install suite in cylc db only
cylc graph puma-aa045                # view graph in browser       

To just view the dependencies on the command line:

cylc ls -t puma-aa045

Setting the default size of the rose edit window

Setting the default size of the rose edit window and the width of the rose edit left hand menu pane can be very helpful.

Edit ~/.metomi/rose.conf

Adding the following information to the file sets the default size and width of the rose config-edit (rose edit) window:

SIZE_WINDOW = (1100, 650)

For details of further customisations that can be made to the rose edit window see:

Launching Rose commands

It is possible to launch many of the Rose tools from the various GUIs. For example you can run or edit suites from rosie go, run suites from rose edit, and view log files from rose suite-gcontrol whilst the suite is running.

When running rose from the command line make sure to run from the appropriate roses/ directory or append the suite name using --name=puma-aa045, e.g.

rose suite-shutdown --name puma-aa015

Stop archiving of log files

By default, when a suite is run, the log files from the previous run will be tarred up. To avoid this run rose suite-run with the flag --no-log-archive.

Diff'ing suites

There is no formal mechanism for this as yet. But there is a tool rose config-dump which sort all of the app files in the suite into a common format, which then allows for diff to be run on the command-line between suite files. For more info see:

Adding UM user diagnostics

This works in a different way to the old UMUI and no longer uses user-STASHmaster files.

Instead the STASHmaster file is held in the UM trunk. To make changes, place your modified version in the file/ subdirectory of the app, e.g:


Passing arguments to fcm_make

Rose deals with fcm_make as a special app, see:

To pass arguments, such as -vvv for full verbose output:

  • Set the environment variable ROSE_TASK_OPTIONS=-vvv
  • Or add args=-vvv at the top of the fcm_make rose-app.conf file.

Rose tip of the day

For more Rose hints see the "tip of the day" from the Rose team: