As described in the Rose documentation (e.g. here), and as I've tried to illustrate with my 'pink bubble' drawing here, a Rose suite is composed of apps. JULES Rose suites always have two apps that run sequentially: fcm_make (the compilation step) and jules (actually running the model).
If you prefer to understand this in a more UNIX way, see screenshot right: the JULES Rose suite is simply a directory on your file system (at location $RSUITE in my notes) that contains some files (including the textfile suite.rc) and two subdirectories app/fcm_make/ and app/jules/ . Kerry Smout-Day also illustrated the same structure nicely in her JULES tutorial here.
- For former UMUI users, suites and apps are what used to be called jobs and tasks.
- The config file for the jules app contains all the namelist files described on the JULES manual pages (select your version of JULES and find section "The JULES namelist files").
- Rose suites for running JULES are available via the Rosie Go system (see here). Additionally, all Rose suites are also available via the repository (e.g. my one u-am539), but rather use Rosie Go if you can. Note that Rose suites can be automatically upgraded using rose app-upgrade, e.g. if you find and download a suite on Rosie Go for JULESvn4.6 then you can use a single command to upgrade it to the latest version of JULES: see here.
- Note that all Rose suites are set up with links to particular driving and ancillary data inside them, but they can always be applied to other driving and ancillary data as necessary.
- The suite.rc textfile controls how the apps of the suite relate to each other and the order in which they are run. You can specify complex and repeating runs of JULES using this (see e.g. here for using it to loop through a set of JULES runs with changing parameter settings). If you want to know more about how to use this, see the Suite Design Guide and/or Kerry Smout-Day's tutorials on the JULES manual pages.