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
  • Click to open the search input field Click to open the search input field Search
  • Menu Menu

problem after coregistration

You are here: Home1 / Forums2 / Support Forum (ARCHIVED – Please use Slack Channel instead)3 / problem after coregistration4
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • 06/17/2017 at 4:57 AM #2777
    Nik Haliasos
    Participant

    Greetings to all,
    i am trying to do my first runs with the software. I have one anat.nii and one postop_tra.nii MRI volumes T2 axials
    It does not matter what type of coregistration i use, when i go to check the normalization i get a

    Skip showing normalization of J:\Medical images\leaddbs\glanat.nii,1
    Skip showing normalization of J:\Medical images\leaddbs\glpostop_tra.nii,1
    Skip showing normalization of J:\Medical images\leaddbs\glpostop_cor.nii,1

    and it does not allow me to view the scans

    Then when i go to the next step to reconstruct i get the
    Error in ea_checkfiles (line 34)
    ea_error(‘Please put a suitable postoperative anatomy file inside patient folder and
    normalize it first.’);

    any thoughts?

    thank you
    Nik

    • This topic was modified 8 years ago by Nik Haliasos.
    06/17/2017 at 1:23 PM #2779
    ningfei
    Keymaster

    Hi Nik,

    Would be more helpful if you could show the current contents of your subject folder. Seems you missed some files there.

    Best,
    Ningfei

    06/17/2017 at 7:28 PM #2780
    Nik Haliasos
    Participant

    I did some progress – tried another combination of coregistration and normalization methods and it seems to be working although the registration result is not so great – is there any way to manually correct the registration?

    Another issue that came up afterwards is that the pre-recon of the electrodes i cannot get it to work either in the automatic or manual way. I tried focusing on the manual process, the red square and crosshair come up but the slice shown inside this popup windows is the lower postop slice where it does not contain the electrode so matlab afterwards goes into an endless loop of “lowering inital factor to -xxxxxx” and never finds it – i had to Ctrl+C after 1min

    Nik

    06/17/2017 at 7:38 PM #2781
    andreashorn
    Keymaster

    Hi Nik,

    you should go step by step – if the registration is not good, Lead-DBS will not find the electrode.
    We need a bit more info to really help you. You could also check out our Slack channel where you could easily send us some screenshots (See Help/Support above).
    It’s not so easy anymore to do normalizations manually, but you could easily perform coregistrations (e.g. post-
    to pre or between multiple pre images) manually somewhere else.

    In case of post-op CT, you’d need to call the registered CT “rpostop_ct.nii”, in case of postop MRI just call it postop_tra.nii. If you have multiple postop MRIs, you could call them postop_tra.nii and postop_cor.nii, postop_sag.nii.

    If all your acquisitions are manually co-registered, just choose “already coregistered” during normalization.

    Re normalization, I’d recommend to start with ANTs which seems most robust.

    Hope this helps, Andy

    06/17/2017 at 7:39 PM #2782
    andreashorn
    Keymaster

    …one thing that could have been is a segfault error in ANTs, especially likely when running on Windows. This could explain the first error from your first message. Unfortunately, Matlab doesn’t detect the system event segfault and continues as if the called routine had been successful. Ningfei recently fixed the ANTs binaries for Windows, so it could make sense to call “Apply Hotfix” from the Install menu to get up to nightly build state.

    06/17/2017 at 8:13 PM #2783
    Nik Haliasos
    Participant

    thank you for your time ..even on a saturday
    I am using postop MRI for the moment

    will go onto the Slack channel to send some pics if needed

    Nik

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

Forum Statistics

Registered Users
131
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 Scroll to top 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