-
Notifications
You must be signed in to change notification settings - Fork 93
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
parameters: expansion and inter-suite trigger graph syntax #2266
Comments
@hjoliver Can you provide a quick |
(This was reported by Xiao at BoM). This should work, but fails validation:
But Xiao's example was more like this:
This should have the same effect as:
Maybe there's a use case for that. However this assumes the same parameter range and template in both suites. Use of two parameters would expand all-to-all (like |
(assuming I remember correctly how the substitution in of the remote task works) It's worth noting that this
Is bad, as multiple polling tasks all polling the same remote is redundant, extra task proxies, dependencies etc. Better to have:
so only one remote polling operation takes place for the one thing that is of interest. |
@arjclark - that's a very good point. I'll inquire of Xiao as to her use case... |
You mention in this bit:
I suspect Xiao may have something along lines of:
Which is less redundant but its better to have a dummy task in the remote suite to represent the whole family of things being finished. (though linearisation now being recorded in the suite db should hopefully mean we can poll family statuses via the cylc suite-state command in future) |
Attempts to do the above get failed by validation.
The text was updated successfully, but these errors were encountered: