-
Notifications
You must be signed in to change notification settings - Fork 532
EHN: Improve JSON interfaces #1047
New issue
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
Conversation
if force_run: | ||
self._always_run = True | ||
|
||
def _process_name(self, name, val): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hi @satra, thinking about the [string[.[@]string]]
format, I guess there's no use for the @
here right? I've implemented only the dot element to create nested dictionaries
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the @
in datasink allows people to dump multiple outputs to the same location and that nipype won't allow connecting two different outputs to the same input.
i'm not sure yet of all the use cases for this interface, but perhaps we can implement it later if needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 on implementing it later, let's see what happens when people use this
@oesteban - sync with master and update changes for merge. feel free to merge this. |
Conflicts: CHANGES
Following #1020, the idea of this PR is improving these new interfaces.
defaults
input toJSONFileGrabber
so that one can set default settings to workflows in case the JSON file with settings does not exist.JSONFileSink
outputs, as @satra suggested in ENH: IO interfaces to JSON files #1020 or maybe with a novel paradigm.