-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rose macro: suite level functionality #1498
Comments
@kaday - would this be something you'd be interested in doing? |
Yes, I will assign it to myself. |
When this issue is resolved, is it worth thinking about how to connect rose suite-run --validate
# which will be roughly equivalent to:
rose macro --validate && rose suite-run |
@matthewrmshin - one to discuss - at present majority of our core suites would fail that test for one reason or another. |
The |
@hjoliver - I like the idea of having that option too - its more a reservation about how people are using the metadata. A number of our suites have, for example, UM apps with multiple optional configs for different modes. The core config is often stripped down to the shared settings with the contents for each of the ways it could be run (e.g. short step, long step, recon, forecast etc.) in optional configs. All together, with whatever combination of configs will be run, the config would validate but as far as rose macro etc. see it it fails the metadata tests. Do you see similar usage at NIWA with your UM apps? |
Just had an upvote on this from a user here. |
I somehow missed the question from @arjclark above. At NIWA our use of UM apps is still rather primitive - UMUI 8.4 jobs converted with |
@kaday - as discussed at today's meeting I'm grabbing this from you with a view to prioritising it in the very near future. |
Looks like this is going to be a somewhat non-trivial change - as the code currently stands its not nicely set up for running in more than one place (or even accepting arguments for running on more than one app) so it might take a while - need to make sure changing it doesn't break anything else. |
I did say that ages ago! And completely agree. |
Looking back at the discussion on |
@matthewrmshin - please see the commentry above about the setup of our operational suites and the way people develop their suites. cylc validate and rose macro validation are two potentially quite different things. |
I believe we can extend the CLI to allow switching on/off validation of different parts of the suite. |
We should be able to run rose macro across a whole suite and retrieve errors (a.la. rose edit) rather than one app at a time.
@benfitzpatrick - if you find the duplicate supersede it with this.
The text was updated successfully, but these errors were encountered: