You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a change to the design of the rose-stem suite. Previously, each job in the suite had an optional config associated with it - this led to a very large number of optional configs with huge amounts of duplication between them if, for example, the same bunch of settings were required in many jobs.
Therefore, in future, please do not add new optional configs to define jobs. Instead, define your job by utilising the currently available optional configs. If this is not possible, then add a new optional config to do the specific new task you require, and document this in the README file.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I just wanted to share some information about a significant change to the lfric_atm rose-stem suite which was committed yesterday in https://code.metoffice.gov.uk/trac/lfric_apps/ticket/524
This is a change to the design of the rose-stem suite. Previously, each job in the suite had an optional config associated with it - this led to a very large number of optional configs with huge amounts of duplication between them if, for example, the same bunch of settings were required in many jobs.
Now, the suite is designed so that each optional config performs a specific task. This could be turning on a particular science scheme, asking for no diagnostic output, or initialising a particular idealised test case. All of the current optional configs are listed with a brief description in https://code.metoffice.gov.uk/trac/lfric_apps/browser/main/trunk/rose-stem/app/lfric_atm/opt/README
Jobs are then constructed by including a mixture of optional config files in https://code.metoffice.gov.uk/trac/lfric_apps/browser/main/trunk/rose-stem/site/common/lfric_atm/tasks_lfric_atm.cylc. The optional configs are applied in the order specified in the "opt_confs" line, constructing a job with all of the requirements.
Therefore, in future, please do not add new optional configs to define jobs. Instead, define your job by utilising the currently available optional configs. If this is not possible, then add a new optional config to do the specific new task you require, and document this in the README file.
Any questions, just ask!
All reactions