RF: Accept nipype configurations from users #229
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
|
Hello @effigies, Thank you for updating! Cheers! There are no style issues detected in this Pull Request. 🍻 To test for issues locally, Comment last updated at 2020-04-06 20:55:42 UTC |
effigies
force-pushed
the
rf/nipype_config
branch
2 times, most recently
from
bf2cfd6
to
5baaa1f
Compare
effigies
force-pushed
the
rf/nipype_config
branch
from
5baaa1f
to
ff30814
Compare
effigies
force-pushed
the
rf/nipype_config
branch
from
ff30814
to
80a0c51
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.
Right now we're quite inflexible about how we handle nipype configurations. This changes the precedence to:
I've also set the default crashfile format to
pklzwhen installed normally, and switch it totxtin containers.