Skip to content

Fix/vol2surf #1078

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

Closed
wants to merge 3 commits into from
Closed

Fix/vol2surf #1078

wants to merge 3 commits into from

Conversation

soligschlager
Copy link

surf_reg option was broken.
We ran the tests, but weren't sure whether that went ok

surf_reg = traits.Bool(argstr="--surfreg", requires=["target_subject"],
desc="use surface registration to target subject")
surf_reg = traits.String(argstr="--surfreg %s", requires=["target_subject"],
desc="registration surface to target subject (default sphere.reg)")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in such a case, you may want to explicitly set the default value of the traits to sphere.reg

surf_reg = traits.String('sphere.reg', ..., usedefault=True)

@soligschlager
Copy link
Author

we considered that, too, but thought rather to mimic freesurfer's original behavior:
If --surfreg is not specified, it defaults to using sphere.reg.
What do you think?

@satra
Copy link
Member

satra commented Apr 9, 2015

@SaOligg88 -

for this to work we need to ensure versioning is in place (and it's only somewhat in place). say for example, freesurfer changes the default from sphere.reg to fancynew.reg. then from a nipype perspective it won't rerun a node because it doesn't know that some default has changed, and from a reproducibility perspective running an older script may not generate the same output because it's actually being called with different parameters.

so i would suggest that we start moving towards encoding the defaults where we can. we will over time start moving the specification to the underlying software themselves (e.g., like slicer), such that these things are automatically picked up together with versioning.

@djarecka
Copy link
Collaborator

@soligschlager are you still working on this PR? Do you need help?

@djarecka
Copy link
Collaborator

@soligschlager - please let us know if you're planning to work on this PR, otherwise I'll try to review and finish.

@soligschlager
Copy link
Author

Hi there, no, unfortunately I'm not. Thanks for checking.

@djarecka
Copy link
Collaborator

@soligschlager - thank you for answering. I will review and check what is still missing.

@djarecka djarecka self-assigned this Dec 14, 2017
oesteban added a commit to oesteban/nipype that referenced this pull request Jan 3, 2018
Close nipy#1078 as this PR supercedes that one
@mgxd mgxd closed this in #2352 Jan 9, 2018
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