JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for FSL Archives


FSL Archives

FSL Archives


FSL@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

FSL Home

FSL Home

FSL  March 2011

FSL March 2011

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Siemen's vibration artifact and Gallichan correction

From:

kochunov <[log in to unmask]>

Reply-To:

FSL - FMRIB's Software Library <[log in to unmask]>

Date:

Mon, 28 Mar 2011 08:31:29 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (78 lines)

Interesting. I have seen the vibration artifacts from two systems. The
artifacts from these systems were very similar to each other and nowhere as
severe as these shown here. However, our data were collected with 89
directions, reading Dan's post I think the higher number of directions was
the reason why these artifacts were less prominent on our end. 
Cheers
peter

-----Original Message-----
From: FSL - FMRIB's Software Library [mailto:[log in to unmask]] On Behalf
Of Daniel Gallichan
Sent: Monday, March 28, 2011 4:51 AM
To: [log in to unmask]
Subject: Re: [FSL] Siemen's vibration artifact and Gallichan correction

Hi Darren and others

Sorry to join the conversation late - being more involved in MR physics I
have to confess I don't actually subscribe to the FSL list...  

I have just  a few comments to add.

Firstly, I definitely agree with Darren that you are seeing the same
vibration artefact as we observed on the system in Oxford prior to the
Siemens hardware adjustment. However, if you see an effect with |x| as low
as 0.45 then I imagine that you have an even bigger effect than we observed
- which could be due to small differences in hardware, or even in how you
restrain the head of the subject (we didn't test it thoroughly, but it
certainly appeared to be the case that by holding the subject in place on
the sides by applying pressure to the headphones it also creates a very good
mechanical connection for transmitting the vibrations...). Unfortunately, a
bigger effect also means you are less likely to be able to get a reasonable
correction.

The correction method described in our paper is unfortunately also only an
approximation. The Tukey windowing function then approximates the effect of
the k-space filter which is automatically applied to the 'smaller half' of
the 3/4 Fourier data. I tried applying the technique to a couple of
30-direction datasets and observed a similarly incomplete correction to that
which you show in this thread. Having more directions effectively means that
you are able to sample more of this curve arising from the filter, and are
likely to get better results. It is also worth considering that even if the
FA maps look much better after the correction, the resulting diffusion
tensor in these regions will be less reliable than if the artefact were not
present - as the extra parameter will necessarily increase the confidence
interval on all estimated parameters. It is certainly preferable to not have
the artefact in the first place...

If you don't need to do direct comparisons of tensor values within the
affected regions, then the simplest and most reliable method to deal with
the artefact would be to identify affected regions by their residuals from a
normal tensor fit, and then exclude these regions from the datasets.
Subjects where the affect region overlaps with the region of interest would
sadly then need to be discarded - but that may be the only option left...  

You mentioned doing a voxel-by-voxel fitting approach - do you mean
effectively having different Tukey filter parameters for each voxel? If so,
I don't know how you would choose which values to use. Ideally you need to
know how the signal varies with |x| when there is no diffusion present (or
isotropic diffusion) which without vibration should be constant. With
vibration, however, this will become location-dependent. The method we
presented makes a guess at this function by averaging over all the affected
voxels which have been identified. I don't see how you could do this on a
voxel-by-voxel basis.
 
My general advice for avoiding the artefact is, as Arman mentioned, using a
full-Fourier acquisition with the necessarily longer TE. When we tried this
with iPAT=2 the TE was only marginally increased, and the SNR appeared to be
quite similar (getting a precise SNR comparision is pretty tricky -
especially where parallel imaging is involved...).

Hope this is of some use - and I hope you can still get something useful
from your data!

Cheers

Dan

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager