<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: PROPELLER-EPI for high-resolution DTI</title>
	<atom:link href="http://www.refscan.info/2007/02/01/propeller-epi-for-high-resolution-dti/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.refscan.info/2007/02/01/propeller-epi-for-high-resolution-dti/</link>
	<description>Magnetic Resonance Imaging news, information, and journal club, with minimal spin.</description>
	<pubDate>Wed, 19 Nov 2008 22:37:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Aziz</title>
		<link>http://www.refscan.info/2007/02/01/propeller-epi-for-high-resolution-dti/#comment-18</link>
		<dc:creator>Aziz</dc:creator>
		<pubDate>Thu, 08 Feb 2007 12:48:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.refscan.info/2007/02/01/propeller-epi-for-high-resolution-dti/#comment-18</guid>
		<description>Dustin, how about doing a Journal Club post on it? Basically just skip the intro, explain the theory using the paper's figs as needed, show a result or two, and then critique/speculate.</description>
		<content:encoded><![CDATA[<p>Dustin, how about doing a Journal Club post on it? Basically just skip the intro, explain the theory using the paper&#8217;s figs as needed, show a result or two, and then critique/speculate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dustin</title>
		<link>http://www.refscan.info/2007/02/01/propeller-epi-for-high-resolution-dti/#comment-17</link>
		<dc:creator>Dustin</dc:creator>
		<pubDate>Thu, 08 Feb 2007 04:43:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.refscan.info/2007/02/01/propeller-epi-for-high-resolution-dti/#comment-17</guid>
		<description>That's a nifty paper.  Here's the short version:

1.  Certain sequences (e.g., PROPELLER, SNAILS) rely on multiple acquisitions.  To account for phase differences in the sequential acquisitions that arise from motion, correction is done based off of the repeatedly-acquired center of k-space (a major recurring theme in reconstruction).

2.  Aliasing and blurring throw off the accuracy of this phase correction.

3.  However, the correction still works IF you include it in the reconstruction.  Mathematically, this works the same way as a parallel imaging reconstruction, with each of the low-resolution phase maps serving the same purpose as the images from the separate coils.

The rest of the paper is straightforward testing of the idea.

It's a very elegant approach.  It seamlessly integrates PI and phase correction--it should complement almost anything else you want to do with PROPELLER, really (or any other technique that repeatedly acquires the center of k-space).</description>
		<content:encoded><![CDATA[<p>That&#8217;s a nifty paper.  Here&#8217;s the short version:</p>
<p>1.  Certain sequences (e.g., PROPELLER, SNAILS) rely on multiple acquisitions.  To account for phase differences in the sequential acquisitions that arise from motion, correction is done based off of the repeatedly-acquired center of k-space (a major recurring theme in reconstruction).</p>
<p>2.  Aliasing and blurring throw off the accuracy of this phase correction.</p>
<p>3.  However, the correction still works IF you include it in the reconstruction.  Mathematically, this works the same way as a parallel imaging reconstruction, with each of the low-resolution phase maps serving the same purpose as the images from the separate coils.</p>
<p>The rest of the paper is straightforward testing of the idea.</p>
<p>It&#8217;s a very elegant approach.  It seamlessly integrates PI and phase correction&#8211;it should complement almost anything else you want to do with PROPELLER, really (or any other technique that repeatedly acquires the center of k-space).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aziz</title>
		<link>http://www.refscan.info/2007/02/01/propeller-epi-for-high-resolution-dti/#comment-16</link>
		<dc:creator>Aziz</dc:creator>
		<pubDate>Wed, 07 Feb 2007 20:39:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.refscan.info/2007/02/01/propeller-epi-for-high-resolution-dti/#comment-16</guid>
		<description>Ah, Dustin, a related reference:

&lt;b&gt;Simultaneous phase correction and SENSE reconstruction for navigated multi-shot DWI with non-cartesian k-space sampling&lt;/b&gt;

Liu et al. Magn Reson Med. 2005 Dec;54(6):1412-22. PMID &lt;a href="http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?db=pubmed&#038;cmd=Retrieve&#038;dopt=AbstractPlus&#038;list_uids=16276497&#038;query_hl=10&#038;itool=pubmed_docsum" rel="nofollow"&gt;16276497 &lt;/a&gt;

I emailed you about it, hopefully you can comment on it?</description>
		<content:encoded><![CDATA[<p>Ah, Dustin, a related reference:</p>
<p><b>Simultaneous phase correction and SENSE reconstruction for navigated multi-shot DWI with non-cartesian k-space sampling</b></p>
<p>Liu et al. Magn Reson Med. 2005 Dec;54(6):1412-22. PMID <a href="http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?db=pubmed&#038;cmd=Retrieve&#038;dopt=AbstractPlus&#038;list_uids=16276497&#038;query_hl=10&#038;itool=pubmed_docsum" rel="nofollow">16276497 </a></p>
<p>I emailed you about it, hopefully you can comment on it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: short-axis PROPELLER at Reference Scan</title>
		<link>http://www.refscan.info/2007/02/01/propeller-epi-for-high-resolution-dti/#comment-8</link>
		<dc:creator>short-axis PROPELLER at Reference Scan</dc:creator>
		<pubDate>Tue, 06 Feb 2007 05:58:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.refscan.info/2007/02/01/propeller-epi-for-high-resolution-dti/#comment-8</guid>
		<description>[...] worth noting that this paper was also referenced by Chuang et al in the previous Journal Club paper. SAP-EPI can&#8217;t quite get as good results on its own as the aforementioned technique, but the [...]</description>
		<content:encoded><![CDATA[<p>[...] worth noting that this paper was also referenced by Chuang et al in the previous Journal Club paper. SAP-EPI can&#8217;t quite get as good results on its own as the aforementioned technique, but the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aziz</title>
		<link>http://www.refscan.info/2007/02/01/propeller-epi-for-high-resolution-dti/#comment-5</link>
		<dc:creator>Aziz</dc:creator>
		<pubDate>Fri, 02 Feb 2007 12:59:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.refscan.info/2007/02/01/propeller-epi-for-high-resolution-dti/#comment-5</guid>
		<description>The PROPELLER recon is a beast. I'll have to do a post on it later but in a nutshell they first need to make sure that the blades are all centered identically. They do this by lowpass filtering the blade in k-space, using a 2D triangular function. They then subtract the phase of the filtered blade from the unfiltered blade (in image space - they do FFFTs on both). This basically solves both the k-space center displacement problem as well as incidental motion-related phase. Then they inverse-FFT the corrected blade back to the k-space domain for the next step.

Once they have all the corrected blades, they need to make sure that the blade orientations are also exact. They basically do a correlation-based correction for k-space rotation using the magnitude of the k-space data. Rebecca improved on that for her MS thesis project if I recall and can comment further.

Next up is bulk translation, which they do by creating a reference image formed by the average of all the k-space centers from each blade, though in my dissertation I showed better results using the first blade as the reference. 

Finally, they do a correlation between all the corrected blades to try and reject blades with too much through-plane motion. After that, they finally get to the re-gridding process and combine the blades all together. 

So, as to the question of how homodyne and PROPELLER would play together, you tell me :) It does seem fiendishly complex. A casual PubMed search shows no results for "PROPELLER homodyne" but there mihgt be something out there, maybe buried in ISMRM abstracts.

The authors here avoid throwing a monkey wrench into these nontrivial works by separating the recon into stages. They are doing parallel imaging to acquire each blade, so the entire PROPELLER recon is a black box downstream. So, if you wanted to include homodyne, I imagine that would be the best way to do that also - use it to acquire a single blade. 

Ah, I see I made a conceptual mistake in my post though. By using homodyne for a single blade, they wont really see any significant decrease in scan time, any more than they do by using parallel imaging. So homodyne isn't the answer to reduced scan time unless you can do the Hard problem of integrating it into the PROPELLER recon. 

BTW, without cheating by looking at the reference, I bet you can tell me why they use a triangular function for the filter. You're the recon God around here, Dustin :) </description>
		<content:encoded><![CDATA[<p>The PROPELLER recon is a beast. I&#8217;ll have to do a post on it later but in a nutshell they first need to make sure that the blades are all centered identically. They do this by lowpass filtering the blade in k-space, using a 2D triangular function. They then subtract the phase of the filtered blade from the unfiltered blade (in image space - they do FFFTs on both). This basically solves both the k-space center displacement problem as well as incidental motion-related phase. Then they inverse-FFT the corrected blade back to the k-space domain for the next step.</p>
<p>Once they have all the corrected blades, they need to make sure that the blade orientations are also exact. They basically do a correlation-based correction for k-space rotation using the magnitude of the k-space data. Rebecca improved on that for her MS thesis project if I recall and can comment further.</p>
<p>Next up is bulk translation, which they do by creating a reference image formed by the average of all the k-space centers from each blade, though in my dissertation I showed better results using the first blade as the reference. </p>
<p>Finally, they do a correlation between all the corrected blades to try and reject blades with too much through-plane motion. After that, they finally get to the re-gridding process and combine the blades all together. </p>
<p>So, as to the question of how homodyne and PROPELLER would play together, you tell me <img src='http://www.refscan.info/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> It does seem fiendishly complex. A casual PubMed search shows no results for &#8220;PROPELLER homodyne&#8221; but there mihgt be something out there, maybe buried in ISMRM abstracts.</p>
<p>The authors here avoid throwing a monkey wrench into these nontrivial works by separating the recon into stages. They are doing parallel imaging to acquire each blade, so the entire PROPELLER recon is a black box downstream. So, if you wanted to include homodyne, I imagine that would be the best way to do that also - use it to acquire a single blade. </p>
<p>Ah, I see I made a conceptual mistake in my post though. By using homodyne for a single blade, they wont really see any significant decrease in scan time, any more than they do by using parallel imaging. So homodyne isn&#8217;t the answer to reduced scan time unless you can do the Hard problem of integrating it into the PROPELLER recon. </p>
<p>BTW, without cheating by looking at the reference, I bet you can tell me why they use a triangular function for the filter. You&#8217;re the recon God around here, Dustin <img src='http://www.refscan.info/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dustin</title>
		<link>http://www.refscan.info/2007/02/01/propeller-epi-for-high-resolution-dti/#comment-4</link>
		<dc:creator>Dustin</dc:creator>
		<pubDate>Fri, 02 Feb 2007 05:44:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.refscan.info/2007/02/01/propeller-epi-for-high-resolution-dti/#comment-4</guid>
		<description>I know that homodyne and PI have been successfully combined in several situations.  I'd be more worried about homodyne and PROPELLER--doesn't the recon rely heavily on phase differences in the low-resolution regime?</description>
		<content:encoded><![CDATA[<p>I know that homodyne and PI have been successfully combined in several situations.  I&#8217;d be more worried about homodyne and PROPELLER&#8211;doesn&#8217;t the recon rely heavily on phase differences in the low-resolution regime?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
