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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

FSL Home

FSL Home

FSL  2004

FSL 2004

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Talairach VS MNI

From:

Cinly Ooi <[log in to unmask]>

Reply-To:

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

Date:

Thu, 30 Sep 2004 13:50:43 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (143 lines)

Christopher Bailey wrote:

>Perhaps I shouldn't start this thread...but I'm so tempted...
>
No worry... I bite. As long as this don't start up a flame war that's
valid discussion. Please understand that I'm looking at it from an
engineer point of view.

By the way, I only focus on the subject of "Talairach vs MNI" and is
*NOT* commenting on why FSL is using MNI.

>
>Here's how I understand the Talairach VS MNI issue (most of it thanks to
>Matt Brett, see):
>
>http://www.mrc-cbu.cam.ac.uk/Imaging/Common/mnispace.shtml
>
>The brain sliced and diced by Talairach and Tournoux in the late 80s was
>that of a small elderly woman. The brain had been lying around in a jar
>of formaldehyde for some significant amount of time before the fellows
>started on the project. How well does this brain represent our typical
>(cognitive at least) FMRI subject population? How well does any single
>brain?
>
Its always a trade off. With only one brain, the results can be skewed
towards that brain's particularity. However, if you start averaging
brains, the brain regions become more fuzzy as there is a smoothing
effect. Not to mention that your transform parameter might matter.

Now, if you are worry about formadehyde distorting the brain (which as a
layman, I think it will), and I worry about averaging having a
detrimental effect, why not we try using the two brains from the
"Visiable Human Project". At least the male subject (god bless him), is
as "fresh" as you can get, and the resolution the best. Combining him
with her, we might have a very detail map with good labelling. At such
resolution, we might be able to introduce engineering principles such as
uncertainty measurement.

The biggest problem as I can see with any altas is the accuracy. I know
of people looking at areas 3mm across, but in imaging accept anything
6mm around the area of interest to be spot on the area. I even went into
a bitter discussion with somebody on it (I say 6mm is spot on, (s)he
says, no, its 3mm away and therefore on the wrong region). I think what
we need is a measure of confidence, say 3mm +/- 1mm at 90% confident
interval. That, together with good labelling on the template, will give
me more confident on my result.

>Another matter is their Brodmann labelling: they never performed
>/any/ histological examinations on their brain! Brodmann areas were
>written down on the basis of comparing their own drawings to those of
>Brodmann... A group in Germany presented progress on some some serious
>work on a Brodmann atlas at HBM04; we shall no doubt hear about that
>soon.
>
>The MNI 152 is the first "half" of a bigger average standard brain
>called prospectively something like the ICBM brain. [For some strange
>reason, the other half has never emerged...?] It is a linear average of
>152 "young adults". It's origin is defined to be at the AC, just like in
>the Talairach atlas. Not surprisingly, the MNI average differs from the
>Talairach brain (cf. ages, genders, no formaldehyde...). Basically, the
>further you go from AC, the less structures align.
>
>
That's probably true with any templates. It all depends on how the
averaging etc is done.

>mni2tal.m is a piecewise-linear (i.e. globally nonlinear) transformation
>from MNI "space" to Talairach "space". Different transformations are
>applied different parts of the brain to try to squeeze the MNI average
>into an old woman's brain...
>
So with transformation the other way round. The thing is, the more
transformation you do, the less accurate your result. Transforming from
subject space -> MNI ->Talairach is going to introduce more uncertainty,
then a direct subject space -> Talairach alone.

>
>Why are we so bent on giving coordinates relative to the AC of a single
>old woman? Because we want to use the atlas to give names to our blobs,
>even Brodmann-names?
>
Conversely, why so bent on giving corrdinates relative to a smooth (read
fuzzy) average brain image of 152 subjects? When transforming to a
single brain, although the brain is distorted (with or without
formadihyde), might be better if the actual brain coordinate can be
determine accurately. Ever consider this?

This are all trade-off. As I see it, engineering problems.

>Personally, after reading about the issue, I
>decided it would be more productive to spend some time learning
>neuroanatomy. Identifying structures in MRs isn't impossible, even for a
>computer-geek such as myself.
>
I suggest adding an extra dimension, since you claim to be a geek:
Understand the error introduce in the acquisition of data, how it
affects transformation etc. This is because in the end, it comes back to
how well can you trust the data.

>
>Don't get me wrong, coordinates are great. That way we can double-check
>each other, compare activations etc.
>
But you must understand the error in the measurement etc. This, I'm
afraid, most users do not.

>In principle, I mean, because the
>confusion around MNI/Talairach has been around for so long now that I
>don't know what to think when I read publications. Are they really
>Talairach coordinates (how did they get them?), or are they actually MNI
>and they just didn't realise (cf. the naming confusion even in FSL:
>img2talcoord)? I think the problem is that "Talairach space" has become
>a synonym for "standard space" and the distinction vanishes into the
>code of the software packages we use.
>
Let's just say Talairach is the de-facto standard. One way of seeing it
as the "standard space" is that it is the reference to wich all other
coordinate system can be compared to. It might or might not be the
lowest standard, but at least its a standard useful for comparing. As a
universal "standard", it is going to be much better then everyone
finding their own standard to compare to.

>
>I would advocate the use of the MNI average both as the registration
>standard (as is allways the case) and as the coordinate system when
>reporting activations. mni2tal just adds a layer of uncertainty to the
>whole process (can you imagine what a "piecewise linear" transformation
>does?). I also suggest that the FSL developers change their naming
>conventions, since when most of us see the word "Talairach", we
>instantly get a mental image of the atlas.
>
>
I'm neutral on the subject. As long as the user knows what they are
doing, that's fine.

The questions here is whatever everyone else is comfortable in doing
this. If everyone is using "Talairach" and you are using "MNI", your
coordinate system might be superior, but if others have to convert it
back to "Talairach", that makes discussion difficult.

Thanks,
Cinly

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