SPM examples incorrect

26 views
Skip to first unread message

thomas.nickson

unread,
Apr 9, 2014, 12:56:05 PM4/9/14
to nipy...@googlegroups.com
Hey I don't know if this is the best place for it but I tried running some of the spm examples and in fact basing some of my own pipelines on the examples provided and I don't think that they are correct. At least they don't work for me.

In the following pipelines:

http://nipy.sourceforge.net/nipype/users/examples/fmri_spm_auditory.html
http://nipy.sourceforge.net/nipype/users/examples/fmri_spm_face.html

There is code like this but it never worked for me. The indicated lines are the problem

preproc.connect([(realign,coregister,[('mean_image', 'target')]),
                 (coregister, segment,[('coregistered_source','data')]),
                 (segment, normalize_func, [('transformation_mat','parameter_file')]),
                 (segment, normalize_struc, [('transformation_mat','parameter_file'),
                                             ('modulated_input_image', 'apply_to_files'),<------------------------------
                                             (('modulated_input_image', get_vox_dims), 'write_voxel_sizes')]),<-------------------
                 (realign, normalize_func, [('realigned_files', 'apply_to_files'),
                                            (('realigned_files', get_vox_dims), 'write_voxel_sizes')]),
                 (normalize_func, smooth, [('normalized_files', 'in_files')]),
                 ])

I think they should be replaced with

preproc.connect(coregister,'coregistered_source', normalize_struc, 'apply_to_files')

This is the method used in the spm manual anyway. I'm not even sure what the modulated_input_image is but it always crashed out.

Thanks.

Satrajit Ghosh

unread,
Apr 10, 2014, 9:41:30 PM4/10/14
to nipy-user
hi thomas,

fmri_spm_face should be fine it uses the appropriate output name (bias_corrected_image). could you please submit an issue on github?

those examples were meant to mimic the tutorials. it's been a long while since we ran them. 

cheers,

satra

--

---
You received this message because you are subscribed to the Google Groups "NiPy Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nipy-user+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Thomas Nickson

unread,
Apr 12, 2014, 1:19:27 PM4/12/14
to nipy...@googlegroups.com
Okay, I'll try running the code as it's provided with some of the data next week. It doesn't fit the work flow of the manual though. When I altered to mimic that everything worked fine.

Thanks,

Tom

Satrajit Ghosh

unread,
Apr 12, 2014, 3:34:40 PM4/12/14
to nipy-user
hi tom,

please feel free to submit a PR to reflect changes in the manual - some of the code originates from 4-5 years back and we weren't as careful in reviewing code then.

cheers,

satra

Thomas Nickson

unread,
Apr 12, 2014, 3:57:09 PM4/12/14
to nipy...@googlegroups.com

What is a PR?

Chris Filo Gorgolewski

unread,
Apr 12, 2014, 4:55:39 PM4/12/14
to nipy...@googlegroups.com
It's a pull request: https://help.github.com/articles/using-pull-requests

It's a very easy way to submit improvements to github projects. Looking forward to your contribution!

Best,
Chris
Reply all
Reply to author
Forward
0 new messages