add --generate_run_script #164
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jfennick
force-pushed
the
generate_run_script
branch
3 times, most recently
from
ea17b60 to
2c9f7b1
Compare
jfennick
force-pushed
the
generate_run_script
branch
from
2c9f7b1 to
a69a3f3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some users have been getting confused about the difference between WIC and CWL.
In particular, some users have been running
wic --yaml ... --run_localand erroneously ascribing the stdout (i.e. the error messages) to WIC and claiming there are errors with WIC.
This PR allows users to instead do
wic --yaml ... --generate_run_scriptfollowed by
./run.shwhich should hopefully make the distinction between WIC and the CWL runner(s) more clear.