Lead-DBS
  • Home
  • About
    • Deep Brain Stimulation
    • Quickstart Primer (Post-OP CT-Scans)
    • Quickstart Primer (Post-OP MR-Scans)
    • Publications
    • Citing Lead-DBS
    • Data & Code inclusion philosophy
    • List of Lead-DBS dependencies
    • Lead Connectome
  • News
  • Help/Support
    • 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
        • FEM-based VTA model
      • 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

Normative connectomes and cortical lesion maps (stroke)

You are here: Home1 / Forums2 / Support Forum (ARCHIVED – Please use Slack Channel instead)3 / Normative connectomes and cortical lesion maps (stroke)4

Tagged: cortical, lesion, Normative connectome, stoke

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • 05/16/2018 at 5:11 AM #4680
    ljh
    Participant

    Hi Andreas and co.,
    I’d like to use the ‘normative connectomes’ feature of LEAD DBS in a stroke patient cohort. I’m hoping to i) draw tracts from the lesion site (a 3d nifti file) and ii) create a “disconnectivity“ matrix from existing parcellations.
    I have successfully downloaded lead-dbs and the normative connectomes I plan to use (Horn, 2013).
    Using Lead Connectome Mapper, I do the following:
     No patient directory chosen
     1. Seed: a 3d lesion map (where 1 denotes the seed region)
     2. Include structural connectivity: select Horn 2013 connectome – export in 2mm.
     3. Connectivity map from seed
     Run!

    I get an error that suggests I haven’t placed an anatomy file in the subject folder (error pasted below). However, I haven’t actually specified a patient folder, and I don’t have individual level anatomical data – just lesion maps that are already normalized etc., Any suggestions on the best way forward here?

    Best,
    Luke

    *************
    Running structural connectivity…
    Command: seed
    Iterating voxels (1/1): 100%
    Iterating fibers (1/1): 100%
    Done.
    Warning: No anatomy information found! Please put either
    anat_t1.nii, anat_t2.nii or anat_pd.nii into subject folder.

    05/16/2018 at 6:59 AM #4683
    andreashorn
    Keymaster

    Hi Luke,

    as a general rule of thumb, always ignore warnings in lead-dbs (this is just a warning, not an error).
    The result files should already be there.

    Best, Andy

    05/17/2018 at 12:56 AM #4698
    ljh
    Participant

    Hi Andy,
    Thank you for the reply – you are indeed correct! The output looks fine.

    As a follow up question – I want to investigate the structural connectivity between a seed roi (a lesion) and a common parcellation (rather than at the voxel level). To do this I have entered a the lesion as a seed roi amongst 246 other parcellation seeds and selected the ‘connectivity matrix’ option. This produces a 247 x 247 matrix which I assume denotes the number of streamlines between each of the regions I have entered into the seeds (246 parcellation rois and one lesion) – is that correct? (and if so – why does the diagonal contain values?)

    Thanks again for the help – lead dbs is a fantastic tool!

    Best,
    Luke

    05/17/2018 at 6:44 AM #4701
    andreashorn
    Keymaster

    Hi, correct – the diagonals are just streamlines going through each region alone. Can ignore it or use it to normalize connections or similar.

    05/18/2018 at 12:03 PM #4724
    ljh
    Participant

    Thanks again Andy – I had another question (sorry!). Is the above approach what you would suggest for creating a normative connectome in common parcellations (i.e., loading each ROI of a parcellation separately as a seed and then using the ‘connectivity matrix’ option)?

    While this works well in the smaller datasets, it seems to use a lot of memory in the NKI 169 atlas. For example, in a 512 parcellation of the cortex is uses over 128 GB of memory which is quite problematic. I thought perhaps there might be a more efficient option, or some extra pre-processing I could do to the dataset to reduce the memory load (although I could not find any documentation).

    Thanks again for the help, I promise to stop bothering you soon!

    05/18/2018 at 1:05 PM #4725
    andreashorn
    Keymaster

    Hi, what you could try is to make sure that all your seeds are really binary (i.e. only 0 and 1 in the images). Then it will be much faster and should also not consume as much memory. The lead mapper tool can use weighted seeds and these will be processed more elaborately given tracks need to be weighted for each voxel.
    So if you break down a parcellation into single files, make sure to use nearest neighbor interpolation or do it manually making sure your nifti file only contains booleans (e.g. no values like 0.9999 or 0.000001 at bordering regions).

    Other than that no clue how to fix it easily.

    05/31/2018 at 5:50 AM #4806
    area51
    Participant

    Hi. Totally new to this but interested in normative connectomics. Is there an online tutorial on how to do this in Lead? I have some limbic DBS subjects that do not have pre-operative DTI. I would like to run connectomics on the VAT from the lead-dbs electrode contact reconstructions.

    Thanks,
    A51

    05/31/2018 at 10:38 AM #4807
    andreashorn
    Keymaster

    Hi A51,

    good name there!
    Unfortunately I fear the documentation is scarce and we currently lack the resources to improve them.
    I guess you already checked the manual? Then the walkthrough-video on the website is probably the best asset.
    After you’ve been through that, I’d advise to join our slack channel and ask specific questions there.
    Best to clarify what’s the state of your analysis (e.g. electrodes reconstructed, VTAs calculated?) and more importantly what exactly you wish to do. Running connectomics is a bit unspecific, I assume you first want to create connectivity maps from your VTAs? But if so, what’s the next step? I.e. is there a behavioral or clinical parameter that you want to address by means of connectivity to the VTA?
    Would definitely need to have a pretty precise plan of what you want to answer to really help. Reason is that there are basically 4 regions in lead dbs where one can do one or the other (running seeds or connectivity matrices -> lead mapper; visualizing and analyzing single patient connectivity -> “convis” module directly in the lead dbs 3D viewer; running parcellation based connectivity stats from your vtas -> lead group; analyzing patient specific connectivity data -> lead connectome; group-wise analysis of such -> lead group connectome). I assume the latter two do not count here since you lack patient DTI. But just wanted to make the point that there are various tools for running connectomics in the lead suite..

    Hope this helps!

    Best, Andy

    05/31/2018 at 10:40 AM #4808
    andreashorn
    Keymaster

    …also note that most of the tools are heavily under development still and should be seen as “beta” state. IMHO the field of dbs connectomics is still developing and we predominantly put in code while we need it ourselves for specific projects. So bear with us if not everything works as intended..

    07/10/2018 at 1:38 AM #5062
    area51
    Participant

    Thanks Andy. To answer you’re questions. I would like to look at the individual patient connectivity from the VTA (electrodes and VTA already constructed with LeadDBS). We have behavioral stimulation mapping data where a behavior occurs only at certain voltages and we would like to map behavior to tracts stimulated.

    -A51

    07/10/2018 at 7:21 AM #5063
    andreashorn
    Keymaster

    Hi there,

    then easiest is to:
    – process these subjects in lead connectome. No new normalization needed but just run “fibertracking” and normalize fibers
    – then load the patients up in lead mapper -> select their stimulations as seed and patient specific connectivity in the dMRI source. Then run seed and you’ll get seedmaps from your VTA to other brain regions.
    – After that, can use the scripts ea_Amap, ea_Rmap or ea_Cmap (see Horn 2017 AoN for details) to create maps that denote your behavioral changes as a function of connectivity across patients.

    Best, Andy

  • Author
    Posts
Viewing 11 posts - 1 through 11 (of 11 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

Subscribe to our newsletter

Latest Tweets

  • Tweet Avatar
    leaddbs
    @leaddbs
    RT @MichaelOkun: Congrats to @DBSThinkTank for the new Frontiers ebook of 26 articles and so far over 100,000 views.… https://t.co/BB5xZQsYr7

    1 year
  • Tweet Avatar
    leaddbs
    @leaddbs
    An automated programming algorithm building on top of Lead-DBS! 🎉😀🎈 https://t.co/2NxaVs9K9z

    1 year
  • Tweet Avatar
    leaddbs
    @leaddbs
    There will be a live demo of @leaddbs in Workshop #5! https://t.co/JCvSGZrkuH

    1 year

Recent Posts

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

Archives

  • 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