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

Normalization

You are here: Home1 / Forums2 / Support Forum (ARCHIVED – Please use Slack Channel instead)3 / Normalization4
Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • 10/28/2016 at 6:11 PM #1574
    Katherine
    Participant

    Hi,

    I recently downloaded Lead-DBS from your website. I am using matlab2012 and SMP12. My pre-op image is T2 Axial series. My post-op image includes the Ax 3dSPGR. I also have COR and Sag FSPGR Reform images. I converted to nii and renamed according to the instructions. I am struggling with the normalization process and would appreciate your help. When I try to run the normalization (ANT) I get the following warning:

    Running ‘Image Calculator’
    Warning: The images do not all have the same dimensions – using 1st image
    Warning: The images do not all have same orientation and/or voxel sizes. – using first image
    ImCalc Image … then gives path to lanat, lpost op etc
    Done ‘Image Calculator’
    Done

    And then error message.
    Warning: Error showing normalization of
    C:\Users\….\glanat.nii,1
    > In ea_show_normalization at 115
    In ea_autocoord at 124
    In ea_run at 95
    In lead_dbs>run_button_Callback at 259
    In gui_mainfcn at 96
    In lead_dbs at 43
    In @ (hObject,eventdata)lead_dbs(‘run_button_Callback’,’Object,eventdata,guidata(hObject))

    Best, Katherine

    10/28/2016 at 11:24 PM #1575
    andreashorn
    Keymaster

    Dear Katherine,

    sorry to hear – two things:
    1. please completely ignore the warning about the Image Calculator. It’s actually a “feature not a bug” we abuse the SPM Image Calculator to get images into the exact same space. It’s misleading for users, of course, and I wanted to disable the warnings for a long time already.. But in general you can safely ignore all warnings in Lead-DBS..

    2. Regarding the error – it seems to happen in the “Show Normalization” Step (not in the actual normalization process). So I think images should have been normalized. You could check e.g. with SPM check coreg or 3D Slicer whether gl*.nii files are in MNI space (e.g. compare them to the file mni_hires.nii in the lead/templates/ folder).

    It’s still very weird that you cannot visualize normalization directly in Lead-DBS.
    To debug, could you please comment lines 22 and 126-128 in ea_show_normalization and rerun the “Check Normalization” Step only?
    Post the error message here then if you get the chance.

    Best, Andy

    10/29/2016 at 8:14 AM #1576
    Katherine
    Participant

    Hi Andy,

    Thanks for your response. This is the error message I obtain when I comment out lines 22, and 26-28 in ea_show_normalization.

    Error: File: ea_show_normalization.m Line: 114 Column: 5
    Illegal use of reserved keyword “catch”.
    Error in ea_autocoord (line 124)
    ea_show_normalization(options);
    Error in ea_run (line 95)
    ea_autocoord(options);
    Error in lead_dbs>run_button_Callback (line 250)
    ea_run(‘run’,options);
    Error in gui_mainfcn (line 96)
    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

    Best,
    Katherine

    10/29/2016 at 9:01 PM #1577
    andreashorn
    Keymaster

    Sorry Katherine,

    the line numbers I told you were wrong.. Please revert the changes made and instead comment out lines
    22 as well as 114-116 – and send me the error that will pop up then.

    Best, Andy

    10/30/2016 at 6:12 AM #1578
    Katherine
    Participant

    Hi Andy,

    Thanks! I was wondering about the lines. This is the error message I get now.

    Error in zscore (line 3)
    MeanM = ones(size(M, 1), 1) * mean(M);
    Error in ea_show_normalization (line 91)
    mni_img.img(:)=zscore(mni_img.img(:));
    Error in ea_autocoord (line 124)
    ea_show_normalization(options);
    Error in ea_run (line 95)
    ea_autocoord(options);
    Error in lead_dbs>run_button_Callback (line 250)
    ea_run(‘run’,options);
    Error in gui_mainfcn (line 96)
    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

    Best,
    Katherine

    10/30/2016 at 4:00 PM #1579
    andreashorn
    Keymaster

    Okay, thanks! Seems you are using a different zscore script which is masking the original Matlab one.
    If you type
    which zscore
    you will see which file Matlab uses when zscore is called. You could then rename/delete that file if it’s not relevant for other projects and/or remove it from the Matlab path.

    Then it should work I guess – and you could afterwards uncomment the lines again.

    Best, Andy

    11/02/2016 at 6:59 PM #1586
    Katherine
    Participant

    Thanks Andy,

    I eliminated the other zscore script. However, I still cannot view the normalization. The error message that comes up is:
    Error in ea_show_normalization (line 86)
    pt.img=(pt.img-min(pt.img(:)))/(max(pt.img(:)));
    Error in ea_autocoord (line 124)
    ea_show_normalization(options);
    Error in ea_run (line 95)
    ea_autocoord(options);
    Error in lead_dbs>run_button_Callback (line 250)
    ea_run(‘run’,options);
    Error in gui_mainfcn (line 96)
    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

    I am able to proceed to the next step to “pre-construct” and “localize DBS electrodes”. The localization is way off however — it places the electrode in the cortex. The co-registration looks fine in SPM when I use the T1 SPGR image but not when I use my lower resolution T2 image. I appreciate your help.

    Best,
    Katherine

    11/02/2016 at 7:02 PM #1587
    andreashorn
    Keymaster

    Hi Katherine,

    did you re-uncomment the lines we commented before?
    Probably that’s the reason.

    Best, Andy

    11/02/2016 at 8:34 PM #1588
    Katherine
    Participant

    Hi Andy,

    I did uncomment the lines and obtained a general error. Then I re-commented them before I sent the error message.

    Warning: Error showing normalization of
    C:\…\glanat.nii,1.
    > In ea_show_normalization at 115
    In ea_autocoord at 124
    In ea_run at 95
    In lead_dbs>run_button_Callback at 250
    In gui_mainfcn at 96
    In lead_dbs at 43
    In @(hObject,eventdata)lead_dbs(‘run_button_Callback’,hObject,eventdata,guidata(hObject))

    Best,

    Katherine

    11/02/2016 at 8:40 PM #1589
    andreashorn
    Keymaster

    Weird. Could you send me the general error (when uncommenting the lines)

    The snippet in your last message is just a warning (no error).

    Best, Andy

    11/02/2016 at 10:26 PM #1591
    Katherine
    Participant

    Hi Andy,

    You are correct. There is no error – just a warning for each gl image stating that there is an error showing normalization. I assumed there was an error though because the windows are not popping up so I can check or view the normalization. Do you know why this might be?

    Best,

    Katherine

    11/03/2016 at 12:40 AM #1593
    andreashorn
    Keymaster

    Oh okay – sorry for not getting that.

    could you again send me the error that shows up? Unfortunately, in your message from 6:59 the crucial first line is missing :(

    sorry that this is so complicated. It really should work well, usually..

    Best, Andy

    02/27/2017 at 11:45 AM #2144
    Atefeh
    Participant

    Hello,
    I am trying to normalize the images, but I get this error:

    Undefined function or variable “to”.

    Error in ea_normalize_ants (line 80)
    ea_ants_nonlinear(to,from,[directory,options.prefs.gprenii],weights,metrics,options);

    Error in ea_autocoord (line 92)
    eval([options.normalize.method,'(options)’]); % triggers the normalization function and passes the options struct to it.

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

    Error in lead_dbs>run_button_Callback (line 192)
    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

    I would be happy, if someone could help.

    Best,
    Atefeh

  • 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
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