We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Suggestions from Titus:
Have 2 equivalent ways to run things:
A short and sweet command that infers file structure:
% taco workflow1 my-workflow-files
A longer and more explicit command:
% taco workflow1 --config-yaml=-my-workflow-files/config.yaml --params-yaml=my-workflow-files/params.yaml
A third, optimal, but more difficult way is to let the user provide a list of input files:
% taco workflow1 --input-files <list of files>
The text was updated successfully, but these errors were encountered:
This is a broader issue than #13 (eliminate redundancy) but that's an important first step
Sorry, something went wrong.
To infer structure,
$ taco workflow1 my-workflow-files
could just glob.glob("my-workflow-files/*conf*") and glob.glob("my-workflow-files/*params*") and assert both have only 1 element.
glob.glob("my-workflow-files/*conf*")
glob.glob("my-workflow-files/*params*")
No branches or pull requests
Suggestions from Titus:
Have 2 equivalent ways to run things:
A short and sweet command that infers file structure:
A longer and more explicit command:
A third, optimal, but more difficult way is to let the user provide a list of input files:
The text was updated successfully, but these errors were encountered: