Glossary list of JULES words

• Ancillaries - datasets of fields at the resolution of the model, such as orography, soil moisture, etc.
• Benchmarking - A way of evaluating the and comparing changes.
• Configuration - The scientific setting chosen for the model to use.
• Driving Data - The data source that drives the model, for example: GSWP2 or Loobos or WFDTI or CHESS etc.
• Evaluation Tools - These are the different tools that are used by the community to evaluate the model at a given version, configuration with defined ancils and driving data.
• KGO - Known Good Output, this is complier specific, it is used in the rose stem testing to prove that changes are not breaking existing code or are only improving the output in an agreed acceptable way, i.e. it is intended.
• Suite - A collection of tasks, either applications and/or commands, which are scheduled to run based on the dependencies between the tasks.
• Version - The code at a defined release date, i.e. vn4.7 was released 2016-10-29 at revision number 5320.

Glossary list of Rose commands

To find out more about each command use the help, for example: rose <COMMAND> --help

• rose edit
• rose sgc
• rose slv
• rose stem
• rose stem --new
• rose stem --new -S HOUSEKEEPING=false --source=.
• rose suite-run
• rose suite-run -i #(to install only to check dependencies - development only)
• rose suite-run -- --mode=simulation --hold #(for suite design development only)
• rose suite-run --new
• rose suite-run --new --name=<NEW_NAME>
• rose suite-shutdown
• rose suite-shutdown --name=<SUITE_NAME> -- --now #(forces the suite to shutdown now and not wait)
• rosie checkout
• rosie copy
• rosie delete
• rosie go

Glossary list of Cylc commands

To find out more about each command use the help, for example: cylc <COMMAND> --help

• cylc gscan
• cylc gui
• cylc scan -c
• cylc view -g -j <SUITE_ID>
• gcylc
• tail -f <full/path/to/cylc-run/SUITE_ID/>log/suite/log #(so you can follow the progress of the suite without a GUI)

Glossary list of FCM commands

To find out more about each command use the help, for example: fcm <COMMAND> --help

• fcm add
• fcm branch
• fcm branch-create
• fcm branch-create --branch-of-branch
• fcm branch-delete
• fcm branch-diff
• fcm branch-info
• fcm branch-list
• fcm browse
• fcm checkout
• fcm commit
• fcm conflicts
• fcm copy
• fcm delete
• fcm diff
• fcm info
• fcm list
• fcm log
• fcm mkdir
• fcm merge
• fcm merge --custom --revision N[:M] [OPTIONS] SOURCE
• fcm merge --custom [OPTIONS] URL1[@REV1] URL2[@REV2]
• fcm merge --reverse --revision
• fcm move
• fcm propdel
• fcm propedit
• fcm propset|ps
• fcm remove
• fcm revert
• fcm resolve
• fcm status
• fcm switch
• fcm trac
• fcm update
• fcm www