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
  • Search
  • Menu Menu

Lead_Group Analysis Assistance

You are here: Home1 / Forums2 / Support Forum (ARCHIVED – Please use Slack Channel instead)3 / Lead_Group Analysis Assistance4
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • 08/19/2016 at 10:42 AM #1378
    PhilipM
    Participant

    I’ve begun to look at my large STN-DBS dataset using Lead_Group and I am excited about the possibilities offered by your platform, although I would appreciate some guidance with analysis steps.

    I am interested in finding the distance between the active contact and each subdivision of the Accolla STN, and I seem to be able to do this.

    I am also interested in knowing for a given estimated volume of activation, whether that is within a particular subdivision (yes / no) and if possible what proportion of that VAT is within the subdivision. There is mention of this on a previous thread but when I try to use the “Correlation Between Regressors and Volume Intersections” button unfortunately I receive errors “Reference to non-existent field ‘ft’.” I have tried entering in separate scalar regressors to make sure it wasn’t that which was missing.

    Is there a way to pull this data out directly from a .mat file – either ea_stats.mat or LEAD_groupanalysis.mat?

    I’m also having some issues with visualisation. In 3D visualisation (also in Lead_DBS) not all subdivisions of the Accolla STN atlas are displayed – the motor portion on the right and the limbic / associative regions on the left. The stats all seem to calculate properly, indicating that all regions are taken into account bilaterally when measuring distance etc.

    Unfortunately I’m also having issues with 2D visualisation “Reference to non-existent field ‘backdrop’.”

    The visualisation issues are not key at present, however, and the visualisation on Lead_DBS works on an individual level as a ‘sanity check’

    Thanks again, much appreciated.

    08/19/2016 at 2:31 PM #1379
    andreashorn
    Keymaster

    Dear Philip,

    yes, lead group is widely undocumented unfortunately, sorry about that.
    Before you click “Correlation Between Regressors and Volume Intersections”, you need to calculate the DBS stats, i.e. click on the “Prepare stats” button. I hope this works, haven’t tried for some while – let me know if it doesnt.

    The info should also be inside the ea_stats.mat file of each patient after that.

    Regarding the Accolla atlas, it seems that you have an outdated data folder from an older version than 1.5 – you can simply delete the atlas_index.mat file and it will be regenerated based on the niftis on the next visualization call. Still, I’d suggest to update the datafiles, i.e. make a clean new download from the website.

    Re the 2D viz – this seems to be a bug – I guess you could circumvent it by once clicking on the settings dialog of the 2D visualizations and saving these settings. Seems there are no default settings stored in your installation somehow.

    Hope this helps, let me know if you have further questions!

    08/21/2016 at 4:33 AM #1383
    PhilipM
    Participant

    Thanks Andreas,

    Regenerating the Accolla atlas file worked for me.

    Unfortunately I am still getting the same error with the “Correlation Between Regressors and Volume Intersections / Fibrecounts” even after adding the patients, adding stimulation intensities, setting group colours and adding regressors, then pressing “Prepare Stats”. The full error is:

    Reference to non-existent field ‘ft’.

    Error in lead_group>preparedataanalysis (line 1143)
    for side=1:size(M.stats(pt).ea_stats.stimulation(usewhichstim).ft,2)

    Error in lead_group>corrbutton_Callback (line 365)
    stats=preparedataanalysis(handles);

    Error in gui_mainfcn (line 95)
    feval(varargin{:});

    Error in lead_group (line 42)
    gui_mainfcn(gui_State, varargin{:});

    Error in
    matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)lead_group(‘corrbutton_Callback’,hObject,eventdata,guidata(hObject))
    Error using ea_showatlas (line 284)
    Error while evaluating UIControl Callback

    Processing Lead_DBS_003.

    When I then try to extract the information from the .mat file (Lead_groupanalysis.mat – stats – ea_stats – stimulation – vat) there is a 2×4 structure available, but the fields AtlasIntersection and nAtlasIntersection are all [0,0,0] even though the VATs are certainly imposed upon the STN subdivisions.

    Am I following the right steps?

    Much appreciated.

    08/21/2016 at 6:56 PM #1387
    andreashorn
    Keymaster

    Hi Philip,

    I haven’t used the feature in a while but just tried on a small test dataset and can confirm it worked for me. I guess the problem is that you actually need to add a group connectome to the process even if you are not at all interested in connectivity. I never found the time to support the case of preparing DBS stats only for the VTA.

    So please make sure that you have some valid .mat files in your lead/fibers folder. You can e.g. download the 2013 group connectome from our download page here on the site. In theory you can even install it by clicking on the group connectome button from within lead.
    Then – since you’re not interested in fibers, choose the thinned out x 500 option as in my screenshot – this wont take a lot of processing time.
    Make sure you have entered all stim params for each patient correctly and chosen the Mädler or Kuncel VTA model.
    Then click on prep. DBS stats. It will prepare all the stats for all patients. When this is done, you should be able to access the data in the mat files as well. Or you can add a regressor into lead group and e.g. click “Correlation between Regressors and Volume Intersections / Fibercounts” in lead group directly.

    I think it’s great you’re trying this, it should be done more. One day I may find some time to make lead_group a bit more robust and intuitive.. I guess it’s quite powerful with many features but that also makes it quite hard to use. Also, not all features may always be up to date for the currentmost single-subject processing features. LG used to be a personal tool for quite some time and grew with features I needed at the moment :)

    Best, Andy

    LG screenshot

    08/21/2016 at 10:00 PM #1389
    andreashorn
    Keymaster

    Hi Philip,

    I think I informed you wrong and stats are not properly built. Will need to investigate a bit more on this.

    Best, Andy

    08/22/2016 at 7:13 PM #1393
    andreashorn
    Keymaster

    Hi Philip,

    so at least I wrote a hotfix which should work now.
    The easiest option would be to install lead dbs via github as described here:
    https://leaddbs.gitbooks.io/leaddbs-manual/content/Installation.html

    – then it should work. You could delete all ea_stats.mat files within your patient folders just to make sure (although I think this is not necessary).

    Alternatively, we’ll probably upload a new minor release soon, too.

    Best, Andy

    08/24/2016 at 5:32 AM #1398
    PhilipM
    Participant

    Thanks Andy, much appreciated. I can also load the .nii volumes manually into Matlab and calculate overlapping voxels myself, which gets around the problem too.

    Can I point out one other issue that got me confused for a short while?

    The 2D display flips the L-R orientation such that contact 0-3 are actually on the RIGHT electrode and contacts 8-11 are on the LEFT electrode. This threw me a bit, as the Medtronic and Boston leads are generally coded the other way around. At least here in Australasia.

    Cheers, Phil

    08/24/2016 at 1:48 PM #1400
    andreashorn
    Keymaster

    Dear Philip,

    thanks for letting me know. Yes, the nifti option is another one.
    I think 0-3 right/left is a center-wise convention, I fear.
    I heard that some centers do it reverse.
    I checked whether there is an official guideline but didnt find one. If you have any official document (e.g. Medtronic/Boston specification) stating that 0-3 should be left, I’d be happy to change it (although it would be a rather major hack).

    Best, Andy

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

Forum Statistics

Registered Users
130
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
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