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

Lead-Connectome

You are here: Home1 / Forums2 / Support Forum (ARCHIVED – Please use Slack Channel instead)3 / Lead-Connectome4
Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • 04/01/2017 at 9:38 PM #2356
    Vinny
    Participant

    Hi,

    I’m using test data from the Human Connectome Project to try out the Lead-Connectome tool. Files were renamed to a format recognized by the Lead-Connectome software and preprocessing appears to have occurred with no problem, i.e., normalization checks revealed good agreement with the MNI template space. However, when attempting to assess structural connectivity using deterministic fibertracking, I get the following error message below in the Matlab command window. Thanks for your help.

    *** Performing structural parts of LEAD-Connectome…

    ————————————————————————
    Running job #1
    ————————————————————————
    Running ‘Segment’

    SPM12: spm_preproc_run (v6365) 15:26:09 – 01/04/2017
    ========================================================================
    Segment C:\Users\Vinit\Downloads\lead\templates\space\MNI_ICBM_2009b_NLIN_ASYM\t1.nii,1
    Failed ‘Segment’
    Error using spm_vol>spm_vol_hdr (line 80)
    File “C:\Users\Vinit\Downloads\lead\templates\space\MNI_ICBM_2009b_NLIN_ASYM\pca.nii” does not exist.
    In file “C:\Users\Vinit\Downloads\spm12\spm_vol.m” (v5958), function “spm_vol_hdr” at line 80.
    In file “C:\Users\Vinit\Downloads\spm12\spm_vol.m” (v5958), function “spm_vol” at line 61.
    In file “C:\Users\Vinit\Downloads\spm12\spm_preproc_run.m” (v6365), function “run_job” at line 84.
    In file “C:\Users\Vinit\Downloads\spm12\spm_preproc_run.m” (v6365), function “spm_preproc_run” at line 41.
    In file “C:\Users\Vinit\Downloads\spm12\config\spm_cfg_preproc8.m” (v6798), function “spm_local_preproc_run” at line 418.

    The following modules did not run:
    Failed: Segment

    Error using MATLABbatch system
    Job execution failed. The full log of this run can be found in MATLAB command window, starting with the
    lines (look for the line showing the exact #job as displayed in this error message)
    ——————
    Running job #1
    ——————
    Error while evaluating UIControl Callback

    04/01/2017 at 10:49 PM #2357
    ningfei
    Keymaster

    Hi Vinny,

    Did you upgrade LEAD from an old version without downloading the data updates or the full version? Since this pca.nii file had been added to LEAD some versions before. If so, you can get the file here. Or you may want to download the full data pack here.

    Best,
    Ningfei

    04/02/2017 at 6:11 AM #2358
    Vinny
    Participant

    Hi Ningfei,

    I downloaded Lead-DBS on Feb 10, 2017 and it was version 1.6.2. I upgraded to version 1.6.3 and have the brainshift correction feature installed. Thanks for the sending the pca.nii file; I placed it in the appropriate subfolder in the lead folder. However, now I get a new error message when assessing structural connectivity using deterministic fibertracking related to no b0.nii file existing; diff.nii, dti.bval, dti.bvec, and anat_t1 files exist in the patient folder.

    Thanks/Vinit

    Running job #1
    ————————————————————————
    Running ‘Coregister: Estimate & Reslice’

    SPM12: spm_coreg (v6435) 23:57:54 – 01/04/2017
    ========================================================================
    Failed ‘Coregister: Estimate & Reslice’
    Error using spm_vol>spm_vol_hdr (line 80)
    File “C:\Users\Vinit\Documents\MATLAB\Diffusion-raw\b0.nii” does not exist.
    In file “C:\Users\Vinit\Downloads\spm12\spm_vol.m” (v5958), function “spm_vol_hdr” at line 80.
    In file “C:\Users\Vinit\Downloads\spm12\spm_vol.m” (v5958), function “spm_vol” at line 61.
    In file “C:\Users\Vinit\Downloads\spm12\spm_coreg.m” (v6435), function “spm_coreg” at line 117.
    In file “C:\Users\Vinit\Downloads\spm12\config\spm_run_coreg.m” (v5956), function “spm_run_coreg” at line 22.

    The following modules did not run:
    Failed: Coregister: Estimate & Reslice

    Error using MATLABbatch system
    Job execution failed. The full log of this run can be found in MATLAB command window, starting with the
    lines (look for the line showing the exact #job as displayed in this error message)
    ——————
    Running job #1
    ——————
    Error while evaluating UIControl Callback

    04/02/2017 at 7:22 AM #2359
    andreashorn
    Keymaster

    Hi Vinit,

    we should in fact remove the deterministic fiber tracking module from Lead-DBS because it is a very basic, even tensor based method (https://www.mathworks.com/matlabcentral/fileexchange/21130-dti-and-fiber-tracking) that hasn’t been used in a while. It is well possible that the method is broken.
    Please try to run the GQI method instead which uses Fang-Cheng Yeh’s / DSI studio’s generalized q-sampling imaging and supports multishell data (such as from HCP). It is also deterministic and performed best in a recent open competition (http://biorxiv.org/content/early/2016/11/07/084137).

    For multishell data, this is clearly the method of choice of the ones implemented in Lead-DBS.

    Best, Andy

    04/02/2017 at 10:52 PM #2360
    Vinny
    Participant

    Thanks Andy. I’ve bolded the subset of files from HCP that I’m using for Lead-Connectome:

    anat/ Anatomical scans
    T1/T1.nii.gz MPRAGE
    T2/T2.nii.gz T2-weighted

    diff/ Diffusion scans
    raw/ unprocessed data
    mri/diff.nii.gz four shells, b-values of b1k, b3k, b5k, and b10k
    bvals.txt b-values
    bvecs.txt diffusion gradient directions
    bvecs_fsl.txt FSL compatible version of diffusion gradient directions

    I renamed the files to be compatible for reading by Lead-Connectome but get the error message that the dti.bval file is unable to be read. Is it because the bvec and bval files are in .txt extension rather than .bvec and .bval format?

    *** Performing structural parts of LEAD-Connectome…
    Building DTI files…
    Export b0…
    Error using load
    Unable to read file ‘C:\Users\Vinit\Documents\MATLAB\Diffusion-raw\dti.bval’. No such file or directory.
    Error in ea_exportb0 (line 4)
    bvals=load([options.root,options.patientname,filesep,options.prefs.bval]);
    Error in ea_prepare_dti (line 14)
    ea_exportb0(options);
    Error in ea_ft_gqi_yeh (line 13)
    ea_prepare_dti(options)
    Error in ea_perform_ft_proxy (line 6)
    eval([options.lc.struc.ft.method,'(options)’]); % triggers the fibertracking function and passes the options
    struct to it.
    Error in ea_perform_lc (line 13)
    ea_perform_ft_proxy(options);
    Error in ea_autocoord (line 109)
    ea_perform_lc(options);
    Error in ea_run (line 95)
    ea_autocoord(options);
    Error in lead_connectome>runsavebutn_Callback (line 289)
    ea_run(‘run’,options);
    Error in gui_mainfcn (line 95)
    feval(varargin{:});
    Error in lead_connectome (line 42)
    gui_mainfcn(gui_State, varargin{:});
    Error in
    matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)lead_connectome(‘runsavebutn_Callback’,hObject,eventdata,guidata(hObject))
    Error while evaluating UIControl Callback

    04/03/2017 at 3:11 AM #2361
    Vinny
    Participant

    Hi Andy,

    I tested Lead-Connectome with diffusion-weighted imaging data from BrainSuite and was able to complete all the steps and obtain the DTI connectivity matrix. For the BrainSuite data, the extensions are .bval and .bvec as opposed to the .txt extension from the HCP for the bval and bvec files. Also, I had renamed from diff.nii to dti.nii and re-ran the HCP data but the same error appeared after trying to export FA. I am not sure if the .txt extension is the issue.

    Regards/Vinit

    04/03/2017 at 3:16 AM #2362
    andreashorn
    Keymaster

    Yes, they need to be called .bval and .bvec. Alternatively, you can change these naming conventions to suit your needs in the preferences file ([Tools]->[Edit Prefs file]).

    Best, Andy

    04/03/2017 at 3:17 AM #2363
    Vinny
    Participant

    Thanks Andy

    05/17/2018 at 8:46 AM #4705
    peace
    Participant

    Dear Lead-DBS experts

    I’m new to Lead-Connectome. Where could I get more information about the preprocessing sequences implemented in both co-registration and normalization menu?

    Such as, head-motion, scrubbing, slice timing etc.

    Thanks for considering my request.

    Cheers
    Larry

    05/17/2018 at 8:52 AM #4706
    andreashorn
    Keymaster

    Hi Larry,

    the preprocessing basically follows the pipeline described in
    https://www.ncbi.nlm.nih.gov/pubmed/24099851

    Motion params are regressed out, slice timing is not corrected for, no scrubbing. WM/CSF signal is regressed out and bandpass-filtering applied within a common window (see paper).
    I’d say the rs-fMRI preprocessing pipeline currently is pretty old-school but works for most applications and is really easy to use. Then again also easy to e.g. use fMRIPREP or similar before using lead connectome.
    Also we’re much looking for people interested in implementing some additional tools into the pipeline.
    Contact me directly if that is interesting.

    Best, Andy

    05/17/2018 at 9:50 AM #4707
    peace
    Participant

    Hi Andy

    Thanks for your quick reply.

    Screen Shot 2018-05-17 at 4.40.36 PM
    https://drive.google.com/open?id=1ZEPrkbUHHEMWUpIkkAl2w4zAOt8SoTbO

    The GUI status appears busy after the preprocessing.

    I get the following error messages (“Please export the connectivity matrix first” in the Matlab after performing the graph matrix analysis. .

    Exporting coregistration check images to /Volumes/Data/untitled folder/checkreg…
    Done.
    *** Performing structural parts of LEAD-Connectome…
    *** Done.
    *** Performing functional parts of LEAD-Connectome…
    *** 1 rs-fMRI files to analyze…
    *** Done analyzing 1 rs-fMRI files…
    Error using ea_error (line 16)
    Please export connectivity matrices first.

    Error in ea_perform_lc (line 129)
    ea_error(‘Please export connectivity matrices first.’);

    Error in ea_autocoord (line 179)
    ea_perform_lc(options);

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

    Error in lead_connectome>runsavebutn_Callback (line 317)
    ea_run(‘run’,options);

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

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

    Error in
    matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)lead_connectome(‘runsavebutn_Callback’,hObject,eventdata,guidata(hObject))
    Error while evaluating UIControl Callback.
    —
    null
    —
    Best regards
    Larry

    05/17/2018 at 9:54 AM #4708
    andreashorn
    Keymaster

    Yes, please export the connectivity matrix first.

    05/17/2018 at 10:04 AM #4709
    peace
    Participant

    Hi Andy

    Thanks. How to export it?

    Cheers
    Larry

    05/17/2018 at 10:10 AM #4710
    andreashorn
    Keymaster

    “Compute Connectivity Matrix” checkbox.

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