Lead-DBS
  • Home
  • Slack User Channel
  • About
    • Deep Brain Stimulation
    • Publications
    • Citing Lead-DBS
    • Data & Code inclusion philosophy
    • List of Lead-DBS dependencies
    • Lead Connectome
    • Lead-OR
  • News
  • Help/Support
    • Learn Lead-DBS yourself
    • Slack User Channel
    • Forum
    • Knowledge Base
      • Lead-DBS Methods
        • AC/PC to MNI conversion
        • DBS Network Mapping
        • Subcortical Electrophysiology Mapping (SEM)
      • Atlases/Resources
        • Cortical Atlas Parcellations (MNI-Space)
        • Subcortical Atlases (MNI-Space)
        • The DISTAL atlas
        • Macaque Atlases (MNI-Space)
        • Normative Connectomes
        • IXI Database
      • Walkthrough-Videos
      • Other Videos
      • Screenshots
  • Manual
  • Workshops
    • Brisbane February 2020
    • Machine Learning – Berlin September 2019
    • Berlin September 2019
    • Past workshops
      • Hamburg February 2019
      • Shanghai September 2018
      • Berlin 2016
  • Download
  • Contact
  • Click to open the search input field Click to open the search input field Search
  • Menu Menu

Stimulation contacts coordinates?

You are here: Home1 / Forums2 / Support Forum (ARCHIVED – Please use Slack Channel instead)3 / Stimulation contacts coordinates?4

Tagged: .mat, brainshift correction, normalization, reconstruction, stimulation contacts

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • 06/06/2017 at 10:12 AM #2714
    tsieger
    Participant

    Hi,
    please, is it possible to read the coordinates of the reconstructed stimulation contacts from some .mat file in the patient directory?

    I noticed that there is ea_reconstruction.mat file in the patient directory, containing several different sets of coordinates,
    perhaps 2×4 contacts in AC/PC, native, MNI, and subcortically-refined (i.e. brainshift-corrected) spaces:

    
    a=load('ea_reconstruction.mat);
    >> a.reco.acpc.coords_mm{1}
    ans =
       12.9738   -0.5765   -6.4287
       13.2689    0.2484   -4.6312
       13.5639    1.0734   -2.8338
       13.8590    1.8984   -1.0363
    >> a.reco.native.coords_mm{1}    
    ans =
        9.9016   19.6273  -73.0613
       10.4545   20.1438  -71.2103
       11.0074   20.6603  -69.3593
       11.5604   21.1769  -67.5083
    >> a.reco.mni.coords_mm{1}      
    ans =
       14.9746  -10.1242  -15.7690
       15.5192   -9.0578  -13.6511
       15.9094   -8.0424  -11.3782
       16.1868   -7.0526   -9.0660
    >> a.reco.scrf.coords_mm{1}   
    ans =
       10.3017   24.3384  -75.7406
       10.8587   24.8301  -73.8912
       11.4157   25.3217  -72.0418
       11.9727   25.8134  -70.1924
    

    Please, what do the individual coordinates refer to?
    Are they corrected for brainshift?

    (It seems that the subcortically-refined coordinates are native coordinates corrected for brainshift, not MNI coordinates. Are the MNI coordinates also brainshift-corrected, or not? If not, can one easily compute brainshift-corrected MNI coordinates?)

    Thanks.

    Best,
    Tomas

    06/06/2017 at 12:46 PM #2717
    andreashorn
    Keymaster

    Hi Tomas,

    – the mni is in mni space and brainshift corrected (if you did perform brainshift correction).
    – native is in space of the postop image (e.g. postop_tra.nii or rpostop_ct.nii)
    – scrf is in space of the anatomical images (e.g. anat_t1.nii) and is similar to native but brainshift corrected – i.e. if you compare the two, you should see the amount of brainshift
    – the acpc fields are coordinates relative to the AC/PC system (auto-converted/marked as defined in Horn 2017 neuroimage).

    Also thanks for your nice comments in the other post from my side :)

    Best, Andy

    06/06/2017 at 5:11 PM #2721
    tsieger
    Participant

    Hi Andy,
    thanks for your comprehensive answer.
    So, comparing scrf and native coordinates, I can estimate the amount of brainshift, e.g. more than 4 mm in the antero-posterior direction in one patient:

    >> a.reco.scrf.coords_mm{1}(1,:)-a.reco.native.coords_mm{1}(1,:)
    ans =
    -1.2301 4.3909 0.4404

    Let me please ask one mow question. I’m curious why, if I apply the brainshift, I usually (in most patients) get electrodes missing the STN (fig. below, A), while when omitting the brainshift correction, the electrodes go thru STN, as expected (fig. B). The weird thing is that the brainshift correction seems to make sense for this patient (C), so it is not clear to me why it failed to make the position of the electrodes more accurate. Perhaps there is a problem with the normalization of the post-operative MRI (D)? Apparently, the post-operative MRI is not aligned with the MNI template well enough (D), while the pre-operative is (C).
    Could you please comment on this? What would be the remedy for this situation? I would love to correct for the apparent brain shift, but the correction seems to make things worse.

    Thanks.

    Best, Tomas

    06/07/2017 at 9:10 AM #2725
    tsieger
    Participant

    Oops, I accidentally swapped some pictures in the figure above, and made the text of my previous post #2721 confusing. I’m very sorry for that.

    The figure above is OK now, and the corrected problem description is:

    If I apply the brainshift correction, I usually (in most patients) get electrodes missing the STN (fig. B), while when omitting the brainshift correction, the electrodes go through STN, as expected (A). The weird thing is that the brainshift correction seems to make sense for this patient (C, green arrows), so it is not clear why the correction moved the electrodes away from the STN. Perhaps there is a problem with the MRI normalization? Apparently, the post-operative MRI is not aligned with the MNI template well enough (E), while the pre-operative is (D).
    What would be the recommended way of dealing with this problem? Shall I perform another MRI normalization? Shall I omit the brainshift correction? (Of course, I would like to have the position of my electrodes reconstructed as accurate as possible, so I would like to perform the correction.)

    Thanks, Tomas

    06/09/2017 at 4:52 AM #2732
    andreashorn
    Keymaster

    Dear Tomas,

    this indeed looks a bit worrisome and I’d love to inspect that subject myself. Could you please send it to me in anonymized form? Best would be the complete processed folder with all the files, if possible.

    We have had trouble with brainshift correction in the past and fixed it recently. But I assume you use the newest version and since you even have applied the hotfix, this shouldn’t be the cause.

    Thanks so much, best, Andy

    06/12/2017 at 2:33 PM #2742
    tsieger
    Participant

    Dear Andy,
    sure, I’m sending a link to the patient folder data directly via email.

    Yes, I’m using the latest version of LeadDBS 1.6.3.4, with the hotfix from 2017-06-12 morning applied.

    Best, Tomas

    06/16/2017 at 6:03 AM #2775
    andreashorn
    Keymaster

    So just in case someone else reads this, the issue could be resolved and was due to a misregistration when applying the coarse+fine mask in the brainshift removal tool on tsieger’s patient.

  • Author
    Posts
Viewing 7 posts - 1 through 7 (of 7 total)
  • The forum ‘Support Forum (ARCHIVED – Please use Slack Channel instead)’ is closed to new topics and replies.

Forum Statistics

Registered Users
131
Forums
1
Topics
185
Replies
607
Topic Tags
81
Empty Topic Tags
12

Subscribe to our newsletter

Recent Posts

  • Lead-DBS 3.0 out now!
  • Lead-OR out now
  • Bug in Lead-DBS v2.5
  • Lead-DBS v2.5 out now!
  • Lead-DBS on the cover of NeuroImage

Archives

  • October 2023
  • August 2021
  • July 2021
  • March 2021
  • September 2020
  • June 2019
  • November 2018
  • September 2018
  • August 2018
  • March 2018
  • November 2017
  • September 2017
  • July 2017
  • April 2017
  • July 2016
  • June 2016
  • May 2016
  • March 2016
  • December 2015
  • November 2015
  • April 2015
  • January 2015
  • December 2014
  • October 2014
  • September 2014
  • July 2014
  • June 2014

Imprint | Privacy Policy

Scroll to top Scroll to top Scroll to top
We use cookies to ensure that we give you the best experience on our website. You may “Accept All” or visit "Cookie Settings" to provide a controlled consent.
Cookie SettingsAccept All
Manage consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
PHPSESSIDsessionThis cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed.
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
CookieDurationDescription
_ga2 yearsThis cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.
_gat_gtag_UA_52019623_11 minuteThis cookie is set by Google and is used to distinguish users.
_gid1 dayThis cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form.
Third-party
Cookies from third-party contents on the website.
CookieDurationDescription
CONSENT16 years 5 months 17 days 13 hoursThese cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback.No sensitive data is collected unless you log in to your google account, in that case your choices are linked with your account, for example if you click “like” on a video.
IDE1 year 24 daysUsed by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile.
test_cookie15 minutesThis cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies.
VISITOR_INFO1_LIVE5 months 27 daysThis cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website.
vuid2 yearsThis domain of this cookie is owned by Vimeo. This cookie is used by vimeo to collect tracking information. It sets a unique ID to embed videos to the website.
YSCsessionThis cookies is set by Youtube and is used to track the views of embedded videos.
yt-remote-connected-devicesneverNo description available.
yt-remote-device-idneverNo description available.
SAVE & ACCEPT
Powered by CookieYes Logo