Lead-DBS
  • Home
  • About
    • Quickstart Primer (Post-OP MR-Scans)
    • Data & Code inclusion philosophy
    • Quickstart Primer (Post-OP CT-Scans)
    • Deep Brain Stimulation
    • Lead Connectome
    • Publications
    • List of Lead-DBS dependencies
    • Citing Lead-DBS
  • News
  • Contact
  • Help/Support
    • Manual
    • Knowledge Base
      • Atlases/Resources
        • Subcortical Atlases (MNI-Space)
        • Cortical Atlas Parcellations (MNI-Space)
        • Macaque Atlases (MNI-Space)
        • The DISTAL atlas
        • FEM-based VTA model
        • Normative Connectomes
      • Lead-DBS Methods
        • Subcortical Electrophysiology Mapping (SEM)
        • AC/PC to MNI conversion
        • Connectivity Benefit Mapping
      • Other Videos
      • Screenshots
      • Walkthrough-Videos
    • Slack User Channel
    • Forum
  • Workshops
    • Past workshops
      • Berlin 2016
      • Shanghai September 2018
      • Hamburg February 2019
    • Berlin September 2019
    • Machine Learning – Berlin September 2019
    • Brisbane February 2020
  • Download
  • Lead-Connectome
  • Search
  • Menu Menu

microelectrode recording positions

You are here: Home1 / Forums2 / Support forum ARCHIVED – Please use Slack Channel instead3 / microelectrode recording positions4
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • 07/19/2018 at 5:23 AM #5120
    checkoutchap
    Participant

    hi there,

    i am using a stealthstation surgical navigation system for DBS electrode trajectory planning.

    during implantation, we collect microelectrode recordings at various depths along the planned trajectory.

    after surgery, we collect a CT scan and register it to the pre-op anatomical MRI to determine the actual lead position.

    i would like to determine the anatomical locations of the microelectrode recordings. however, the ‘planned’ and ‘actual’ trajectories do not perfectly match (due to minor surgical inaccuracies).

    is there a way that lead-dbs can determine microelectrode recording locations by ‘correcting’ the planned trajectory by the ‘actual’ trajectory? if so, do you know if it is possible to export the stealthstation plan into matlab?

    cheers

    • This topic was modified 2 years, 6 months ago by checkoutchap.
    07/19/2018 at 6:42 AM #5122
    andreashorn
    Keymaster

    Hi there,

    you can base the MER on your postoperative lead in lead-dbs. Just open the MER tool to point fiducials.
    Import from stealth station – never done that. No clue how it would work, probably, you’d need to write an importer yourself.

    Best, Andy

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

Your Account

Log In
Register

Forum Statistics

Registered Users
132
Forums
1
Topics
185
Replies
607
Topic Tags
81

Subscribe to our newsletter

Latest Tweets

  • Tweet Avatar
    leaddbs
    @leaddbs
    Nice study led by @DrAlfonsoFasano on GPi-DBS for pediatric dystonia. Voxel cluster most associated with clinical i… https://t.co/IScNqVQX94

    18h
  • Tweet Avatar
    leaddbs
    @leaddbs
    This is probably the oldest easteregg in @leaddbs, surprising that it survived until now from the very first releas… https://t.co/qqcUBw3nW1

    5d
  • Tweet Avatar
    leaddbs
    @leaddbs
    RT @Chencheng_Zhang: Our study demonstrates the beneficial effects of GPi-DBS for treating camptocormia in PD patients in the short term https://t.co/eq03g2oKb2

    5d

Recent Posts

  • Lead-DBS on the cover of NeuroImage
  • Lead-DBS on the cover of Biological Psychiatry
  • Lead-DBS on the cover of Annals of Neurology
  • Crucial methodological updates for Lead-DBS
  • 2nd Lead-DBS Workshop in Shanghai, China

Archives

  • 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

Impressum & Datenschutzerklärung

Scroll to top