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

Fiber Traking, DTI

You are here: Home1 / Forums2 / Support Forum (ARCHIVED – Please use Slack Channel instead)3 / Fiber Traking, DTI4

Tagged: DTI

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • 10/18/2016 at 2:49 PM #1517
    ramin.azodi
    Participant

    Hello All,

    Actually in the last step and after fusion when I am trying to work with DTI data. I selected the “Global fiber tracking method” to perform structural analysis. After 4 days my Matlab 2014.b (16 GB RAM, Core 5) is still busy, is that normal?. And when I selected “deterministic Fiber traking” I am getting following error

    
    Create the b matrices
    Voxel intensity to absorption conversion
    Create B matrix vector [Bxx,2*Bxy,2*Bxz,Byy,2*Byz,Bzz]
    Calculate Diffusion tensor, eigenvalues, and other parameters of each voxel
    Reference to non-existent field 'BackgroundThreshold'.
    
    Error in ea_DTI (line 100)
                if(S0(x,y,z)>parameters.BackgroundThreshold)
    
    Error in ea_ft_deterministictracking_kroon (line 63)
    [ADC,FA,VectorF,DifT]=ea_DTI(DTIdata,parametersDTI);
    

    Could someone tell me how I can solve this problem?

    Many Thanks,
    Ramin

    • This topic was modified 8 years, 7 months ago by ramin.azodi.
    • This topic was modified 8 years, 7 months ago by ramin.azodi.
    • This topic was modified 8 years, 7 months ago by ramin.azodi.
    • This topic was modified 8 years, 7 months ago by ramin.azodi.
    • This topic was modified 8 years, 7 months ago by ramin.azodi.
    • This topic was modified 8 years, 7 months ago by ramin.azodi.
    • This topic was modified 8 years, 6 months ago by andreashorn.
    10/18/2016 at 3:01 PM #1524
    andreashorn
    Keymaster

    Hi Ramin,

    honestly, it’s quite possible that the deterministic tracker has issues with some datasets, it’s not well tested and I wouldn’t advise to use it at all (will remove it from Lead-DBS at some point). It’s real diffusion tensor imaging (i.e. with the tensor model) and that’s quite outdated.
    The Gibbstracker sometimes takes >1 day but should not take 5 days (except it’s a really huge dataset or something similar). Does it still produce fibers at all? There should be a window that opens which should show you progress. If that’s not the case (i.e. no new window popped up), please abort Matlab and paste the error code here (i.e. where Matlab was hung when you aborted).
    Also, there should be a third option which is to use DSI studio under the hood (it’s referred to as generalized Q-imaging (by Fang-Cheng Yeh)). It’s an extremely fast and also modern fiber tracking method which should work on all datasets (i.e. single- or multishell). Can definitely recommend that method – but also can recommend the Gibbstracker (which takes ~4-8 hrs. for one subject on a modern computer).

    Also, please use the currentmost version of Lead-DBS since we fixed some fibertracking related things in the recent past.

    Let me know if that helps!

    Best, Andy

    10/19/2016 at 5:04 PM #1528
    ramin.azodi
    Participant

    Thanks a lot for your quick response and the comprehensive answer. My main problem solved now when I updated software and used the Q-sampling. But still i have a problem related to visualization.
    when I am following these steps to visualize results, I am getting this message
    Add objects ---> Open Trac ---> load FTR.mat

    Plotting fibers: K>>
    What should I do? If I press continue, I am getting this error,

    Plotting fibers:     K>> 1
    
    ans =
    
         10%Cell contents reference from a non-cell array object.
    
    Error in ea_addobj>addfibertract (line 179)
        if size(thisset{fib},1)~=3
    
    Error in ea_addobj (line 23)
                addfibertract([pana,fina],resultfig,addht,fina,[],0,options);
     
    Error using keyboard
    Error while evaluating Menu Callback0%Cell contents reference from a non-cell array object.

    Could you help me how I can visualize the results?

    Many thanks,
    Ramin

    • This reply was modified 8 years, 6 months ago by ramin.azodi.
    • This reply was modified 8 years, 6 months ago by ramin.azodi.
    10/19/2016 at 11:53 PM #1535
    andreashorn
    Keymaster

    Hi Ramin,

    I fear trying to show the whole connectome in Lead-DBS is not so easy – Matlab is not really built for this and in any case Lead-DBS isn’t at the moment.. However, just to have a good look at the whole fibers I recommend to use trackvis (www.trackvis.org). There is a file called FTR.trk inside your patient’s folder which you can load in trackvis to show fibers.
    Within Lead-DBS, the way to go would be to visualize only the fibers traversing through a volume of activated tissue.
    This video walkthrough goes through the whole process:

    Just instead of selecting a group connectome in the convis viewer in the end, select “Patient specific fiber tracts”.

    I hope this all works..
    Finally, you can also do stats on fibertracts connecting your VTA with other areas in the brain. I.e. find out whether differences in connectivity code for clinical outcome or similar. You can do some of that stuff directly using lead group – which is, to be honest, very unintuitive.. Sorry about that.. trying to improve everything but lack the time and manpower for now..

    Best, Andy

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