Skip to content

Commit 73f5065

Browse files
author
David Ellis
committed
DOC: Explains how subject_id is used in workflow
1 parent bf46eef commit 73f5065

File tree

1 file changed

+11
-0
lines changed
  • nipype/workflows/smri/freesurfer

1 file changed

+11
-0
lines changed

nipype/workflows/smri/freesurfer/recon.py

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -105,6 +105,17 @@ def create_reconall_workflow(name="ReconAll", plugin_args=None):
105105
Outpus::
106106
postdatasink_outputspec.subject_id : name of the datasinked output folder in the subjects directory
107107
108+
Note:
109+
The input subject_id is not passed to the commands in the workflow. Commands
110+
that require subject_id are reading implicit inputs from
111+
{SUBJECTS_DIR}/{subject_id}. For those commands the subject_id is set to the
112+
default value and SUBJECTS_DIR is set to the node directory. The implicit
113+
inputs are then copied to the node directory in order to mimic a SUBJECTS_DIR
114+
structure. For example, if the command implicitly reads in brainmask.mgz, the
115+
interface would copy that input file to
116+
{node_dir}/{subject_id}/mri/brainmask.mgz and set SUBJECTS_DIR to node_dir.
117+
The workflow only uses the input subject_id to datasink the outputs to
118+
{subjects_dir}/{subject_id}.
108119
"""
109120
reconall = pe.Workflow(name=name)
110121

0 commit comments

Comments
 (0)