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
We need to define an interface for users to author recipes. Which part do they write? How do we take the user part and make it in to a machine-understandable workflow to submit to the cluster?
Right now we're using templating, and we really don't like it because it's hard to validate. Trey is exploring an alternate approach on a branch (reconsider-recipe-templating).
We think we should explore multiple approaches to user recipe design. For example, if we use a context manager to load the parsl configuration (e.g. executor, provider), do we call it under the hood or expect the user to use the context manager? What will enable the typechecker to do the best validation on the recipe?
The text was updated successfully, but these errors were encountered:
We need to define an interface for users to author recipes. Which part do they write? How do we take the user part and make it in to a machine-understandable workflow to submit to the cluster?
Right now we're using templating, and we really don't like it because it's hard to validate. Trey is exploring an alternate approach on a branch (
reconsider-recipe-templating
).We think we should explore multiple approaches to user recipe design. For example, if we use a context manager to load the parsl configuration (e.g. executor, provider), do we call it under the hood or expect the user to use the context manager? What will enable the typechecker to do the best validation on the recipe?
The text was updated successfully, but these errors were encountered: