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
By default, in most cases, Drake builds all targets specified in the workflow files. Sometimes it can be useful to specify it explicitly...
I'm confused-- is ... the default or not?
Apparently it is not because I a workflow such that if I run drake I get some "input not found" errors (for inputs which are outputs of steps in the workflow!) but the error goes away when I run drake ....
Unfortunately the workflow is complicated and I have been unsuccessful in creating a simple shareable example. Any thoughts on why drake might fail to find an output while drake ... works? Thanks!
The text was updated successfully, but these errors were encountered:
@potash apologies, without an example workflow i'm not sure what might be happening here. the best i can do is point you to some historic literature that may be related: #149
The manual states
I'm confused-- is
...
the default or not?Apparently it is not because I a workflow such that if I run
drake
I get some "input not found" errors (for inputs which are outputs of steps in the workflow!) but the error goes away when I rundrake ...
.Unfortunately the workflow is complicated and I have been unsuccessful in creating a simple shareable example. Any thoughts on why
drake
might fail to find an output whiledrake ...
works? Thanks!The text was updated successfully, but these errors were encountered: