<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mri on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/mri/</link>
    <description>Recent content in Mri on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 12 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/mri/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AFNI vs MRtrix3 vs Nipype in 2026: Which Open-Source Neuroimaging Pipeline Should You Standardize On?</title>
      <link>https://www.pistack.xyz/posts/2026-09-12-afni-vs-mrtrix3-vs-nipype-neuroimaging-pipelines/</link>
      <pubDate>Sat, 12 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-12-afni-vs-mrtrix3-vs-nipype-neuroimaging-pipelines/</guid>
      <description>&lt;h2 id=&#34;a-single-study-terabytes-of-data-and-three-grown-up-toolkits&#34;&gt;A Single Study, Terabytes of Data, and Three Grown-Up Toolkits&lt;/h2&gt;&#xA;&lt;p&gt;One diffusion MRI dataset from a moderate cohort easily reaches several hundred gigabytes before any processing begins. Add functional runs, anatomical scans, and longitudinal follow-ups and you are managing petabytes. The bottleneck stopped being the scanner years ago — it is now the analysis pipeline, and the difference between a defensible result and an unpublishable one is often which toolkit produced it and whether a reviewer can rerun it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
