Skip to content

FUGUE interface refactoring #857

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

Merged
merged 13 commits into from
Jul 29, 2014
Merged

Conversation

oesteban
Copy link
Contributor

(edited)

Deep revision of the interface. Including the following changes:

  • Added doctests, 3 new examples as in fugue usage.
  • Interface now uses the name_template system
  • Reviewed parameter interactions (xors, requires) and special outputs (namely: shift maps and field maps)

oesteban added 3 commits June 11, 2014 12:32
FUGUE interface was adding wrong parameter in forward warping mode.
Added the missing doctest of the interface.
@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling 0998e5e on oesteban:bug/fixFUGUEsettings into e815741 on nipy:master.

@oesteban
Copy link
Contributor Author

In reality, tests are passing.

oesteban added 2 commits July 3, 2014 18:55
Deeply reviewed the interface to use the new name_template system,
along with the correction of several issues. Also includes changes
of another PR, so close nipy#856.
@oesteban oesteban changed the title Fix incorrect requirement of FUGUE input FUGUE interface refactoring Jul 4, 2014
oesteban added 2 commits July 4, 2014 12:07
The workflow was using an input with its name changed.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.05%) when pulling 3a82578 on oesteban:bug/fixFUGUEsettings into e815741 on nipy:master.

oesteban added 2 commits July 7, 2014 15:42
Also replaced the name_source dynamic setting with str instead of lists,
as it seems to produce errors when executing as MapNode of workflows.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) when pulling cd329a4 on oesteban:bug/fixFUGUEsettings into e815741 on nipy:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.04%) when pulling f083895 on oesteban:bug/fixFUGUEsettings into e815741 on nipy:master.

@chrisgorgo
Copy link
Member

Are you still experiencing problems with mapnode or is it ready to merge?

@oesteban
Copy link
Contributor Author

I think this is OK, but let me double-check. I'm currently using this PR (rather intensively) and tomorrow I will check if all my workflows finished alright.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) when pulling aee0789 on oesteban:bug/fixFUGUEsettings into bf7938e on nipy:master.

@oesteban
Copy link
Contributor Author

This is working OK

chrisgorgo added a commit that referenced this pull request Jul 29, 2014
@chrisgorgo chrisgorgo merged commit af406fe into nipy:master Jul 29, 2014
@oesteban oesteban deleted the bug/fixFUGUEsettings branch July 29, 2014 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants