Getting Started: Copying a Workflow for the Regional Nesting Suite

To begin working with the regional nesting suite, you first need to create your own copy of an existing workflow.

As introduced in the Global Modelling Practical, you can do this using the rosie command-line tool — see there for the difference between copying and checking out. As in that practical, copy the workflow rather than checking it out. Monsoon3 uses a dedicated branch of the workflow, so the source you copy differs by platform:

Met Office

rosie copy u-by395

Monsoon

See also

For help choosing the correct Monsoon3 service and finding the official setup guidance, see Using Monsoon3.

rosie copy u-by395/u-by395_lfric_monsoon3

Other

Warning

“Other” means your own machine, or a system run by another institution (see Choosing your platform). This step cannot be completed there without local equivalents of the Met Office services it depends on: a supported LFRic build environment, repository access, shared ancillary data, and an HPC batch queue. The commands below are given so you can follow along and adapt them to your site, not because they will work unchanged.

rosie copy u-by395

Alternatively, you can check out the workflow instead of copying it:

Met Office

rosie checkout u-by395

Monsoon

rosie checkout u-by395/u-by395_lfric_monsoon3

Other

Warning

“Other” means your own machine, or a system run by another institution (see Choosing your platform). This step cannot be completed there without local equivalents of the Met Office services it depends on: a supported LFRic build environment, repository access, shared ancillary data, and an HPC batch queue. The commands below are given so you can follow along and adapt them to your site, not because they will work unchanged.

rosie checkout u-by395

Either command reports the new suite ID it created, and the local copy it made under ~/roses. Make a note of that ID: the rest of this practical refers to it as <suite-id>.