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

Running in patient space only

You are here: Home1 / Forums2 / Support Forum (ARCHIVED – Please use Slack Channel instead)3 / Running in patient space only4

Tagged: Native Space

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • 12/06/2019 at 4:15 PM #8812
    tsieger
    Participant

    Hi,
    would it be possible to use Lead-DBS to work solely in patient’s native space, please? For example, to reconstruct and extract stimulation electrode from non-normalized MRI, or compute VTA in native space? For now, it seems that reconstruction strictly requires normalized images.

    My use case would be to reconstruct the electrodes in native space (before any non-linear mapping took place) and visualize VTA in native space too, superimposing the VTA on patient’s preop image.

    Well, I understand that normalization would be needed to compute VTA (in order to know the distribution of WM/GM), or to show atlases, available in MNI, in native space (to determine the mapping between native and MNI space). But perhaps this would only pose “side steps”, while the main processing would take place in native space?

    Thanks.
    Best regards,
    Tomas

    12/06/2019 at 4:32 PM #8813
    andreashorn
    Keymaster

    Hi hi, yes, this already works – but you have to run the normalization once.
    Then just visualize in native space instead of MNI and do your VTA calculations there.

    12/06/2019 at 5:57 PM #8819
    tsieger
    Participant

    Thanks. Still, is it possible to extract electrodes in native space, in patient’s MRI being not affected in a nonlinear way?

    12/06/2019 at 6:37 PM #8820
    andreashorn
    Keymaster

    Yes of course that’s a core feature of Lead-DBS. In the first popup under 7. Visualization simply choose native space and then 3D visualize which will be in native space. If you calculate a VTA there, it will be calculated in native space. You still have to run normalization to do so but the results will not be affected by this (only the atlas nuclei will be based on the normalization).

    12/09/2019 at 11:13 AM #8833
    tsieger
    Participant

    OK, VTA can be computed in native space.
    However, it seems that electrode reconstruction can be performed in normalized space only, as when I attempt to pre-reconstruct electrodes without normalizing first, it fails with: glpostop_tra.nii" does not exist., even though I choose the ‘Native Patient Space’ option under ‘7. Visualization’.
    Maybe, I’m missing something.

    12/09/2019 at 11:48 AM #8837
    andreashorn
    Keymaster

    Yes, you always need to run normalizations. However, that doesn’t mean they are actually used.
    For prereconstruction, some of the algorithms need some waypoints that are defined in MNI space and then transformed to native space.
    So again i) yes you will always need to run normalizations in Lead-DBS but ii) you can still use the native space reconstructions that do not really use the normalization and iii) if you use atlases in native space that are not manually reconstructed, the inverse of the normalization will be used.

    Best, Andy

    12/09/2019 at 1:55 PM #8841
    tsieger
    Participant

    Great, thanks a lot.
    Tomas

  • 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