You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: notebooks/introduction_nipype.ipynb
+6-49Lines changed: 6 additions & 49 deletions
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@
77
77
"deletable": true,
78
78
"editable": true,
79
79
"slideshow": {
80
-
"slide_type": "slide"
80
+
"slide_type": "subslide"
81
81
}
82
82
},
83
83
"source": [
@@ -131,7 +131,9 @@
131
131
"\n",
132
132
"You and your problems with fMRI data. I'm perfectly happy with FreeSurfer's command line interface. It gives me all I need to do surface based analyses.\n",
"Of course, you can run your sequential FreeSurfer scripts as you want. But wouldn't it be nice to optimize computation time by using parallel computation?"
135
137
]
136
138
},
137
139
{
@@ -144,8 +146,6 @@
144
146
}
145
147
},
146
148
"source": [
147
-
"Of course, you can run your sequential FreeSurfer scripts as you want. But wouldn't it be nice to optimize computation time by using parallel computation?\n",
148
-
"\n",
149
149
"Let's imagine you want to do smoothing on the surface, with **two different FWHM** values, on **both hemispheres** and this on **six subjects**, all in **parallel**? With Nipype this is as simple as that:\n",
150
150
"\n",
151
151
"```python\n",
@@ -161,47 +161,6 @@
161
161
"```"
162
162
]
163
163
},
164
-
{
165
-
"cell_type": "markdown",
166
-
"metadata": {
167
-
"deletable": true,
168
-
"editable": true,
169
-
"slideshow": {
170
-
"slide_type": "subslide"
171
-
}
172
-
},
173
-
"source": [
174
-
"# If you want to have good normalization, you need ANTs!\n",
175
-
"\n",
176
-
"I agree, but there's just a difference between this:\n",
"Let's assume we want to do preprocessing that uses **SPM** for *motion correction*, **FreeSurfer** for *coregistration*, **ANTS** for *normalization* and **FSL** for *smoothing*. Normally this would be a hell of a mess. It would mean switching between multiple scripts in different programming languages with a lot of manual intervention.\n",
235
-
"\n",
236
-
"**Nipype does all that for you! In parallel and in a very intuitive way!**\n",
193
+
"Let's assume we want to do preprocessing that uses **SPM** for *motion correction*, **FreeSurfer** for *coregistration*, **ANTS** for *normalization* and **FSL** for *smoothing*. Normally this would be a hell of a mess. It would mean switching between multiple scripts in different programming languages with a lot of manual intervention. **Nipype comes to the rescue!**\n",
<h1id="I-don't-need-that,-I'm-happy-with-FreeSurfer!">I don't need that, I'm happy with FreeSurfer!<aclass="anchor-link" href="#I-don't-need-that,-I'm-happy-with-FreeSurfer!">¶</a></h1><p>You and your problems with fMRI data. I'm perfectly happy with FreeSurfer's command line interface. It gives me all I need to do surface based analyses.</p>
<p>Of course, you can run your sequential FreeSurfer scripts as you want. But wouldn't it be nice to optimize computation time by using parallel computation?</p>
11919
11945
11920
11946
</div>
11921
11947
</div>
@@ -11925,7 +11951,6 @@ <h1 id="I-don't-need-that,-I'm-happy-with-FreeSurfer!">I don't need that, I'm ha
<p>Of course, you can run your sequential FreeSurfer scripts as you want. But wouldn't it be nice to optimize computation time by using parallel computation?</p>
11929
11954
<p>Let's imagine you want to do smoothing on the surface, with <strong>two different FWHM</strong> values, on <strong>both hemispheres</strong> and this on <strong>six subjects</strong>, all in <strong>parallel</strong>? With Nipype this is as simple as that:</p>
<h1id="If-you-want-to-have-good-normalization,-you-need-ANTs!">If you want to have good normalization, you need ANTs!<aclass="anchor-link" href="#If-you-want-to-have-good-normalization,-you-need-ANTs!">¶</a></h1><p>I agree, but there's just a difference between this:</p>
<h1id="But-I-like-my-neuorimaging-toolbox">But I like my neuorimaging toolbox<aclass="anchor-link" href="#But-I-like-my-neuorimaging-toolbox">¶</a></h1><ul>
11980
11975
<li>You can keep it! But instead of being stuck in MATLAB with SPM, or having scripting issues with FreeSurfer, ANTs or FSL,..</li>
11981
11976
<li><strong>Nipype</strong> gives you the possibility to cherry-pick the algorithms that you prefer from many different sofware packages.</li>
@@ -11990,9 +11985,8 @@ <h1 id="But-I-like-my-neuorimaging-toolbox">But I like my neuorimaging toolbox<a
<h1id="A-short-Example">A short Example<aclass="anchor-link" href="#A-short-Example">¶</a></h1><p>Let's assume we want to do preprocessing that uses <strong>SPM</strong> for <em>motion correction</em>, <strong>FreeSurfer</strong> for <em>coregistration</em>, <strong>ANTS</strong> for <em>normalization</em> and <strong>FSL</strong> for <em>smoothing</em>. Normally this would be a hell of a mess. It would mean switching between multiple scripts in different programming languages with a lot of manual intervention.</p>
11994
-
<p><strong>Nipype does all that for you! In parallel and in a very intuitive way!</strong></p>
<h1id="A-short-Example">A short Example<aclass="anchor-link" href="#A-short-Example">¶</a></h1><p>Let's assume we want to do preprocessing that uses <strong>SPM</strong> for <em>motion correction</em>, <strong>FreeSurfer</strong> for <em>coregistration</em>, <strong>ANTS</strong> for <em>normalization</em> and <strong>FSL</strong> for <em>smoothing</em>. Normally this would be a hell of a mess. It would mean switching between multiple scripts in different programming languages with a lot of manual intervention. <strong>Nipype comes to the rescue!</strong></p>
0 commit comments