[FieldTrip] Lead Field Units in LCMV Beamformer

Tue May 3 04:37:55 CEST 2022

Hi Jan-Mathijs,

Based on discussions with colleagues, I was expecting typical lead fields to be on the scale of 1e-15, and I thought lead field units should be in units of Teslas. If I am misinterpreting it, what would a typical brain lead field look like after using an LCMV Beamformer?

The system we collect data is on a CTF 151-channel system. So I'm not sure exactly how to modify the analyses. Any guidance here would be appreciated. In its current implementation, we had the source and head model in 'cm', and the coordinate system in 'mm'.

My gut feeling is that the units are in T/cm as you described, so it is confusing to get it to T/m. I will look further into "ft_prepare_leadfield", but I am also looking into the nested functions within there. You made a good point about Marc's last note being 8 years old, so a lot of these issues may have been taken care of through the years.

If you would be able to help figure out what units these lead fields and dipole moments are expressed in, that would be helpful. It can clarify a lot of our doubts on our end. I am relatively new to such analyses, so I appreciate any help.

Thank you.

Jasen
________________________________
From: fieldtrip <fieldtrip-bounces at science.ru.nl> on behalf of Schoffelen, J.M. (Jan Mathijs) via fieldtrip <fieldtrip at science.ru.nl>
Sent: May 2, 2022 3:36 AM
To: FieldTrip discussion list <fieldtrip at science.ru.nl>
Cc: Schoffelen, J.M. (Jan Mathijs) <janmathijs.schoffelen at donders.ru.nl>
Subject: Re: [FieldTrip] Lead Field Units in LCMV Beamformer

Hi Jasen, When you state that the scale is ‘much too large’ that suggests that you have a specific expectation of the values that you typically get (using other software? what is the unit convention in that software?). Since you are not clear

Hi Jasen,

When you state that the scale is ‘much too large’ that suggests that you have a specific expectation of the values that you typically get (using other software? what is the unit convention in that software?). Since you are not clear on what type of MEG system you have been working with, I cannot comment on the figure you report. (as a side note, if you are working with Elekta data (and MEG field gradients), if I recall well you need to read in the gradiometer description specifying the ‘coilaccuracy’ option to be >=1 for the units to work well enough, otherwise the units may indeed be ill-defined).

Besides, the physical units of (MEG) leadfields should be something like T/nAm, or (T/m)/nAm etc. , so I am not sure why you mention the scale to be of ‘1e-10 T’.

This being said, correctly dealing with units is tricky, since different MEG/EEG vendors have different unit conventions (e.g. metric distances expressed in cm/m/mm, potentials expressed in muV or V etc). FieldTrip aims to work internally with SI units (i.e. m V T etc). To this end, it tries to apply the required scaling based on the specified units in the (metadata), or based on educated guesses from the dataformat. Also, FT tries hard to synchronize the units of the different data objects that are required for the computation (volume conductor, gradiometers)

However - to complicate things a bit more - , FieldTrip data structures (e.g. gradiometer descriptions with coil positions, gradient baseline lengths, and volume conductor models) are typically broadcasted to the user with units that may not be SI (e.g. MEG gradients in T/cm, volume conductor models in mm).

By the way, if you want to explore this further, I’d recommend you to compute the leadfields using ft_prepare_leadfield, since in this way you are closer to the actual computation (while still relying on FieldTrip’s bookkeeping functionality). Note that Marc’s e-mail on the discussion forum is already 8 years old, and I am pretty sure that quite some things have changed (for the better) in the mean time.

At this moment, I don’t see the need (yet) for any modification to the code, and I suggest that you explore a bit further, based on the above.

Best wishes,
Jan-Mathijs

On 25 Apr 2022, at 15:30, Jasen Devasagayam via fieldtrip <fieldtrip at science.ru.nl<mailto:fieldtrip at science.ru.nl>> wrote:

Hello Everyone,

I ran into some confusion when looking at LCMV beamformed data, using the function, "ft_sourceanalysis". We are using a single shell forward model in these analyses. When looking at the output struct from this function, the lead fields were on the scale of 1e-10 T,  which seems much too large for MEG fields. Looking into FieldTrip archives, I found a similar question by Marc Lalencette from 2014 (https://mailman.science.ru.nl/pipermail/fieldtrip/2014-September/008438.html<https://urldefense.com/v3/__https://mailman.science.ru.nl/pipermail/fieldtrip/2014-September/008438.html__;!!D0zGoin7BXfl!8ajmEDfI5wL5fN4OSXedJSEn-PVa5eFeyD01jJ6amW1ywmru-EfJdiKHpjLS7yxPP_us3QngQX0OGjeLcoDljQ95Fe-2JQR8fQ$>) where it looks like the issue stems from the fact that fields are computed with respect to 'cm'.

I applied a conversion factor, by multiplying all data by 1e-4, to get from 'cm^2' to 'm^2'. I applied this conversion factor in the function "ft_compute_leadfield" in Line 260:
      lf = lf*headmodel.forwpar.scale^2*1e-4;

I had originally tried to just adjust the scaling factor, but making that one small change severely altered the data in multiple places in our pipeline, which in turn yielded lead fields on the scale of 1e-10 once again. In this case, the scaling factor is 1.

I was wondering if this would be the correct place and method to implement this modification. If not, would you have any suggestions on how to get sensible lead field values?

Thank you.

<Outlook-rebpi3hn.png>
Jasen Devasagayam, MASc
Research MEG Technologist
Neurosciences and Mental Health

The Hospital for Sick Children
686 Bay St., Toronto, ON M5G 0A4
P 416-813-7654 ext. 201535
<Outlook-3fzlys2n.png><https://urldefense.com/v3/__https://www.instagram.com/sickkidstoronto/__;!!HJOPV4FYYWzcc1jazlU!_z-ur50qPdLAjDHYrdazjQumNhsOgHecva_beSA8RIZl4a1SHJdPrXCut_sNSh9JLEXshzdkRn3cFz69mkrlSAMNKcNqFNy4XWVpig$> <Outlook-anx2aeuu.png><https://urldefense.com/v3/__https://twitter.com/SickKidsNews__;!!HJOPV4FYYWzcc1jazlU!_z-ur50qPdLAjDHYrdazjQumNhsOgHecva_beSA8RIZl4a1SHJdPrXCut_sNSh9JLEXshzdkRn3cFz69mkrlSAMNKcNqFNy8JEWS3A$> <Outlook-j5bhmd4s.png><https://urldefense.com/v3/__https://www.youtube.com/channel/UCleVfdmpkf7H5tnRRw7n39A__;!!HJOPV4FYYWzcc1jazlU!_z-ur50qPdLAjDHYrdazjQumNhsOgHecva_beSA8RIZl4a1SHJdPrXCut_sNSh9JLEXshzdkRn3cFz69mkrlSAMNKcNqFNz8sQdooQ$> <Outlook-psrt3plh.png><https://urldefense.com/v3/__https://www.linkedin.com/company/the-hospital-for-sick-children/?originalSubdomain=ca__;!!HJOPV4FYYWzcc1jazlU!_z-ur50qPdLAjDHYrdazjQumNhsOgHecva_beSA8RIZl4a1SHJdPrXCut_sNSh9JLEXshzdkRn3cFz69mkrlSAMNKcNqFNzzvsrwpw$>

________________________________

This e-mail may contain confidential, personal and/or health information(information which may be subject to legal restrictions on use, retention and/or disclosure) for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this e-mail in error, please contact the sender and delete all copies.
_______________________________________________
fieldtrip mailing list
https://mailman.science.ru.nl/mailman/listinfo/fieldtrip<https://urldefense.com/v3/__https://mailman.science.ru.nl/mailman/listinfo/fieldtrip__;!!D0zGoin7BXfl!8ajmEDfI5wL5fN4OSXedJSEn-PVa5eFeyD01jJ6amW1ywmru-EfJdiKHpjLS7yxPP_us3QngQX0OGjeLcoDljQ95Fe___WeMCQ$>
https://urldefense.com/v3/__https://doi.org/10.1371/journal.pcbi.1002202__;!!HJOPV4FYYWzcc1jazlU!_z-ur50qPdLAjDHYrdazjQumNhsOgHecva_beSA8RIZl4a1SHJdPrXCut_sNSh9JLEXshzdkRn3cFz69mkrlSAMNKcNqFNxqoASfaA$

________________________________

This e-mail may contain confidential, personal and/or health information(information which may be subject to legal restrictions on use, retention and/or disclosure) for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this e-mail in error, please contact the sender and delete all copies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.science.ru.nl/pipermail/fieldtrip/attachments/20220503/83619be9/attachment.htm>