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
The rose stem command wraps cylc install which is a bit awkward.
The bespoke command is an additional complication to working practices.
Cylc commands like cylc validate and cylc graph may fail on the source due to missing template variables.
It makes Stem seem like a system onto itself whereas it is really just setting a couple of template variables.
Consider re-implementing rose stem as a pure plugin so that the Stem working practices are the same as for any other Cylc workflow. This would require Stem workflows to use a flag file or load a Stem plugin in some way.
For example if we were to implement a template variable file for Cylc, a Stem workflow might look something like:
# cylc_template_variable_file.pyfromcylc.rose.stemimportget_stem_variablesdefget_template_variables():
# this line makes a workflow a `rose stem` workflowreturnget_stem_variables()
Otherwise we could use a flag file or configuration something like:
The
rose stem
command wrapscylc install
which is a bit awkward.cylc validate
andcylc graph
may fail on the source due to missing template variables.Consider re-implementing
rose stem
as a pure plugin so that the Stem working practices are the same as for any other Cylc workflow. This would require Stem workflows to use a flag file or load a Stem plugin in some way.For example if we were to implement a template variable file for Cylc, a Stem workflow might look something like:
Otherwise we could use a flag file or configuration something like:
The text was updated successfully, but these errors were encountered: