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

error using pre-Reconstruct

You are here: Home1 / Forums2 / Support forum ARCHIVED – Please use Slack Channel instead3 / error using pre-Reconstruct4

Tagged: error, pre-reconstruct

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • 02/08/2018 at 11:26 AM #4123
    Nabkr
    Participant

    Hi Lead-DBS team,
    I am trying to use the Lead-DBS for the first time with preoperative MRI and postoperative CT scan. After following the manual I was able to complete DICOM export, coregistration and Normalisation without any error but while doing the pre-Reconstruct, it gives an error saying:

    Estimated point not yet defined. Using second empirical point.
    Subscript indices must either be real positive integers or logicals.

    Error in ea_reconstruct_trajectory (line 226)
    mask(round(estpoint(2)-options.maskwindow : estpoint(2)+options.maskwindow), …

    Error in ea_reconstruct (line 45)
    [trajectory,trajvector]=ea_reconstruct_trajectory(trajectory,lnii,side,refine,options);

    Error in ea_runtraccore (line 37)
    [coords,trajvector{side},trajectory{side},tramat]=ea_reconstruct(options.patientname,options,side,lnii);

    Error in ea_autocoord (line 199)
    [coords_mm,trajectory,markers]=ea_runtraccore(options);

    Error in ea_run (line 96)
    ea_autocoord(options);

    Error in lead_dbs>run_button_Callback (line 187)
    ea_run(‘run’,options);

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

    Error in lead_dbs (line 43)
    gui_mainfcn(gui_State, varargin{:});

    Error in matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)lead_dbs(‘run_button_Callback’,hObject,eventdata,guidata(hObject))

    Error while evaluating UIControl Callback

    My settings for pre-Reconstruct was Target: STN,GPi or Vim and mask window size: auto. I could not change the Method part as it is locked in TRAC/CORE (Horn 2015).

    Your help would be really appreciated.

    Many thanks in advance.

    Regards,
    Nabin

    02/08/2018 at 11:31 AM #4124
    andreashorn
    Keymaster

    Hi Nabin,

    maybe first step is to change the entrypoint to “Manual” and click on the leads when asked.
    https://leaddbs.gitbooks.io/leaddbs-manual/content/Reconstruction%20of%20Electrode%20Trajectory.html

    Best, Andy

    02/08/2018 at 2:23 PM #4125
    Nabkr
    Participant

    Thank you Andy. Got through that step. But it is taking taking really long to write out 2D . Is it usual ? Also in the tutorial video it says it takes a while, so was wondering if it is something that needs overnight ? Say in a PC with 8GB RAM, 3 ghz processor running MATLAB2015.

    Thanks again.

    Best,
    Nabin

    02/08/2018 at 2:32 PM #4126
    andreashorn
    Keymaster

    To write out 2D results you mean?
    The step that takes long is the ea_screenshot function which uses myaa (antialiasing) code to write out high resolution figures. Could in theory bypass that and use a simple saveas() command if the slow speed bugs you too much. Guess it also depends on the atlas. Does 3D visualization work and did you check reconstruction in the intermediate step?

    Best, Andy

    02/08/2018 at 3:15 PM #4127
    Nabkr
    Participant

    Thanks Andy. Yes, I checked the recontruction as explained also in the video and the 3D visualization also works fine. also, I figured out that its my Matlab, somehow it gets stuck after some steps. I closed all, restarted the matlab again and did write out to 2D and it works fine now.

    Many thanks again for your prompt support. Really appreciate.

    Best,
    Nabin

    02/08/2018 at 3:50 PM #4128
    andreashorn
    Keymaster

    Great, glad that it works!

    Best, Andy

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 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
131
Forums
1
Topics
185
Replies
607
Topic Tags
81

Subscribe to our newsletter

Latest Tweets

  • Tweet Avatar
    leaddbs
    @leaddbs
    RT @neumann_wj: Our #ECG contamination paper on implantable bidirectional brain stimulation systems is live. Great and fast paced c… https://t.co/Rkwp86ZxKE

    20h
  • Tweet Avatar
    leaddbs
    @leaddbs
    RT @andreashorn_: Clinically relevant study showing ECG artifacts are higher when IPG implanted on the left side. 👏👏 this will likely… https://t.co/ostng3NZxN

    20h
  • Tweet Avatar
    leaddbs
    @leaddbs
    Interesting single center case series with CM + ANT-DBS vs. CM-DBS only in 16 children and adults with drug-resista… https://t.co/0gzbgQlHud

    2d

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