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

latest update problem

You are here: Home1 / Forums2 / Support Forum (ARCHIVED – Please use Slack Channel instead)3 / latest update problem4
Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • 05/29/2017 at 9:46 AM #2666
    astrid
    Participant

    Hi,
    I updated Lead on Friday (v 1.6.3.4) and now i cannot open 3D reconstructions I did with the previous version anymore, either in individuals or in the group, here are the error msg:
    Error using ea_error (line 15)
    Couldn’t visualize electrode from patient 1.

    Error in ea_elvis (line 104)
    ea_error([‘Couldn”t visualize electrode from patient ‘,num2str(pt),’.’]);

    Error in ea_write (line 46)
    resultfig=ea_elvis(options);

    Error in ea_autocoord (line 200)
    ea_write(options)

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

    Error in lead_dbs>run_button_Callback (line 190)
    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 @(hObject,eventdata)lead_dbs(‘run_button_Callback’,hObject,eventdata,guidata(hObject))

    Error while evaluating UIControl Callback

    >>
    Error using ea_error (line 15)
    Couldn’t visualize electrode from patient 1.

    Error in ea_elvis (line 104)
    ea_error([‘Couldn”t visualize electrode from patient ‘,num2str(pt),’.’]);

    Error in lead_group>vizbutton_Callback (line 362)
    resultfig=ea_elvis(options,M.elstruct(get(handles.patientlist,’Value’)));

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

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

    Error in @(hObject,eventdata)lead_group(‘vizbutton_Callback’,hObject,eventdata,guidata(hObject))

    Error while evaluating UIControl Callback

    I guess there is an issue with the latest update?
    Best,
    Astrid

    05/29/2017 at 4:05 PM #2668
    ningfei
    Keymaster

    Hi Astrid,

    The above log seems to be from lead group. Have you also tried it in lead dbs with the data from patient 1 (the first one in lead group subject list)? Before doing that, please apply a hotfix first. Just unzip it into your lead folder and overwrite the old files. You may also want to reset the lead preferences to default from the Preferences menu. Let me know what you got then.

    Best,
    Ningfei

    05/29/2017 at 4:22 PM #2669
    astrid
    Participant

    With these options, there is still the same bugs with electrode visualization,
    when investigating more, the error seems to come from ea mapelmode2reco:

    [el_render(pt).el_render,el_label(:,pt)]=ea_showelectrode(resultfig,elstruct(pt),pt,options);
    To use ‘radtodeg’, you might need:
    radtodeg – Mapping Toolbox

    Error in ea_mapelmodel2reco (line 61)
    if 90-radtodeg(acos(dot(…

    Error in ea_showelectrode (line 56)
    [X,electrode,err]=ea_mapelmodel2reco(options,elspec,elstruct,side,resultfig);

    Best,
    Astrid

    05/29/2017 at 4:27 PM #2670
    andreashorn
    Keymaster

    Hi astrid,

    could you try to replace “radtodeg” with “rad2deg” in line 61 in ea_mapelmodel2reco?

    Best, Andy

    05/29/2017 at 5:21 PM #2671
    astrid
    Participant

    Hi Andreas,
    I did but also got the pbm as rad2deg is also a function of the Mapping Toolbox
    Best!
    Astrid

    05/29/2017 at 5:29 PM #2672
    andreashorn
    Keymaster

    Hi Astrid,

    true, please replace with this file:
    https://github.com/leaddbs/leaddbs/blob/master/ea_mapelmodel2reco.m

    Best, Andy

    05/30/2017 at 5:05 PM #2676
    astrid
    Participant

    Hi,
    thank you for the answers! it is working fine now,
    I have an additional issue though concerning the connectomes, the groupconnectome file seems to have changed path, I unzipped the lead data file as explained, but it still did not find any modality (indicating that no connectivity data is found)
    I tried a dirty way of doing this by renaming groupconnectomes data.mat and placing them in a folder in dMRI and it seemed to work (at least it built the ea_pm) untill a certain point,
    finally i wondered how in addition to the ea_pm we could get the meshes of the fibers to plot them in trackvis for instance?
    Thank you again!
    Best,
    Astrid

    05/30/2017 at 9:38 PM #2679
    ningfei
    Keymaster

    Hi Astrid,

    Yes. Both the path and the naming of the group connectome data have changed. It should be placed in lead/connectomes/dMRI/ as you already noticed.

    Maybe I don’t get you right, but if you just want to visualize the fibers from groupconnectome data in trackvis, I guess Andy might already have the trk files. In general, the conversion can be done by ea_ftr2trk, if the space is known.

    Best,
    Ningfei

    05/31/2017 at 11:04 AM #2684
    pdeman
    Participant

    hi,
    in the connectome gui, stimulation-based results part.
    the list of modality available correspond to what ? the group connectomes ?

    to fill this list, you use this:

    % check for canonical fiber sets
    fdfibs=dir([ea_getconnectomebase('dmri'),filesep]);
    for fdf=1:length(fdfibs)
        if fdfibs(fdf).isdir && ~strcmp(fdfibs(fdf).name(1),'.')
            [~,fn]=fileparts(fdfibs(fdf).name);
            modlist{cnt}=fn;
            sf(cnt)=1;
            cnt=cnt+1;
        end
    end

    ea_getconnectomebase return ‘lead/connectomes/dMRI/’ (and then you add again a filesep it’s not necessary)
    then you list what’s inside this directory using dir and you keep in modlist only the directory (if fdfibs(fdf).isdir)
    so the connectome files are not seen.

    we made a directory (let’s say “general”) in ‘/lead/connectomes/dMRI’ and then we see this directory in the modality list in the stimulation based results.

    then when we try to do something.
    it looks for a data.mat file in /lead/connectomes/dMRI.
    what should be this data.mat file ?

    moreover we would like to generate for each patients, the fiber meshs resulting from the stimulation-based results.
    and load in lead_group each patient fiber mesh (not the total fibers but the one selected by the stimulation-based results).
    if each patient can have their fibers in a different color that’s a bonus:)

    05/31/2017 at 10:28 PM #2689
    ningfei
    Keymaster

    Hi,

    Yes, the filesep there is reduntant, but this won’t affect the result of dir.

    As I said, the groupconnectome data should be unzipped into lead/connectomes/dMRI/ now. You will then see some folders with the name like “Groupconnectome (Horn 2013) full” there. The data.mat files are in these folders. If you have all the group connectome data ready, you will see them in the “Prepare DBS stats” section under “which connectivity metric to use” (seems the popupmenu is not large enough to show the full names of the folders), from where you can also choose the patient specific fiber tracts.

    Best,
    Ningfei

    06/01/2017 at 3:50 AM #2693
    andreashorn
    Keymaster

    … so new structure should be
    /dMRI/NameOfGroupConnectome/data.mat

    …as a side note, I had written this change to you guys when I implemented it since I knew it would lead to trouble :)
    Not sure whether via mail or slack but I did think of you when changing the structure.

    The change was/will be needed because we now have a definite format for structural and functional connectome files. In fMRI, connectomes are not stored as single files but folders with a multitude of subject files. I also wanted to allow different ways to store structural connectomes that need multiple files. So I decided to replace the .mat files with folders inside of which is (for now) a single file named data.mat

    Best, Andy

    06/01/2017 at 9:30 AM #2694
    pdeman
    Participant

    ok for the folder problem.

    about the display of the fibertracks selected by the vat for each patient.
    is it possible to display all of them in lead_group ?
    we can’t find the mesh of the fibertracks selected.
    we have the ea_pm file, but not the fibers.
    (I am talking specifically about the fibers selected by the simulation of the stimulations, not the DTI of the patient, we don’t have them for these patients, we use the groupconnectom).

    • This reply was modified 5 years, 9 months ago by pdeman.
    06/01/2017 at 10:21 AM #2697
    andreashorn
    Keymaster

    As said via email, no (see mail).
    Please use a fibertracking software for that (TrackVis/DSI Studio)

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