@@ -147,7 +147,7 @@ def get_vox_dims(volume):
147
147
l1analysis = pe .Workflow (name = 'analysis' )
148
148
149
149
"""Generate SPM-specific design information using
150
- :ref:`nipype.algorithms.modelgen.SpecifyModel `.
150
+ :ref:`nipype.algorithms.modelgen.SpecifySPMModel `.
151
151
"""
152
152
153
153
modelspec = pe .Node (interface = model .SpecifySPMModel (), name = "modelspec" )
@@ -272,7 +272,7 @@ def makelist(item):
272
272
-----------------------------------------
273
273
Here we create a structure that provides information
274
274
about the experimental paradigm. This is used by the
275
- :ref:`nipype.algorithms.modelgen.SpecifyModel `
275
+ :ref:`nipype.algorithms.modelgen.SpecifySPMModel `
276
276
to create the information necessary to generate an SPM design matrix.
277
277
"""
278
278
@@ -326,7 +326,7 @@ def makelist(item):
326
326
pipeline. Thus for this pipeline there will be subject specific
327
327
sub-directories.
328
328
329
- The :func:`nipype.pipeline.engine.Workflow.connect` function creates the
329
+ The :func:`~ nipype.pipeline.engine.workflows. Workflow.connect` method creates the
330
330
links between the processes, i.e., how data should flow in and out of
331
331
the processing nodes.
332
332
"""
@@ -390,8 +390,8 @@ def getstripdir(subject_id):
390
390
The code discussed above sets up all the necessary data structures
391
391
with appropriate parameters and the connectivity between the
392
392
processes, but does not generate any output. To actually run the
393
- analysis on the data the :func:`nipype.pipeline.engine.workflows.Workflow.run`
394
- function needs to be called.
393
+ analysis on the data the :func:`~ nipype.pipeline.engine.workflows.Workflow.run`
394
+ method needs to be called.
395
395
"""
396
396
397
397
if __name__ == '__main__' :
0 commit comments