UM/LFRic Suites Using Git Sources #566
Replies: 6 comments 53 replies
-
|
Hi this sounds awesome thanks so much for working all this out! Just a trivial nit-pick but the last 4 of the links to the example suites above don't actually go to the right suites (a/a/0/0/3 has accidentally copied and pasted d/n/ from the previous link in-place of a/a/, and similar for the others). Anyhow so glad we can science-test code-changes on github now :) Cheers! |
Beta Was this translation helpful? Give feedback.
-
|
Hi James. I have been following your instructions in u-aa003/README.md and at the end it says: Using the mirrors requires either setting the For the Met Office what should I be replacing hostname:/path/to/git_mirrors/ with? |
Beta Was this translation helpful? Give feedback.
-
|
James Bruten (@james-bruten-mo) many thanks for making these available. A few questions about setting them up on Monsoon:
|
Beta Was this translation helpful? Give feedback.
-
|
Hi what is the correct syntax for pointing to a branch in the dependencies.yaml file? I'm trying to setup a UM SCM workflow at vn14.0 using a git branch for the first time (already got one that uses only the trunk git sources working fine). The change I made to point to my branch instead of main is: This is supposed to compile using my branch from my fork here: But the extract task is failing with: Presumably I need some additional syntax in the line: Cheers! |
Beta Was this translation helpful? Give feedback.
-
|
Hi all, how do you include more than one source-code branch from git sources? (so 3 branches if you include the trunk). In my dependencies.yaml file, I tried the obvious: But with this the extract task fails: So I guess its not as simple as you can just add more entries to add more branches? Note I have other workflows which have compiled and run just fine with either one or the other of the two branches (vn14.0_ukca_chemoff_mrphys, vn14.0_comorph_dev), so its not that there's a problem with one of the branches. I also know that these 2 branches do merge cleanly (no files are modified by both of them). So I must just be getting the syntax wrong in dependencies.yaml, and need to do something different if I want 2 branches? Cheers! |
Beta Was this translation helpful? Give feedback.
-
|
Hi Mike, that's the right syntax and it's just worked for me with those branches - https://cylchub/services/cylc-review/view/james.bruten?&suite=um_ex%2Frun14&no_fuzzy_time=0&path=log/job/1/extract/01/job.err |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Dear All,
We have now upgraded our standalone example suites for the UM and LFRic to run using the Github hosted repositories. These are available at:
This changes where the Source code for the models is extracted from, not where the workflows themselves reside. While the workflows can also be moved to github, this may have implications around archiving, and therefore we recommend keeping them in the roses repository for the time being.
Each suite has a README explaining the changes required to use git sources. These are general guidelines which will likely need modifying based on your exact workflow, and the names within.
Defining Dependencies
Sources are defined from a
dependencies.yamlfile in the suite. This format supports multi-branch extraction and automated merging. For example,which will first clone the Met Office lfric_apps repository at tag
2025.12.1and then attempt to merge inmy_branchfrommy_fork. Merge conflicts will be ignored in therose-stemdirectory anddependencies.yaml, otherwise they'll raise an error.Beta Was this translation helpful? Give feedback.
All reactions