Viewing 3 posts - 1 through 3 (of 3 total)
Viewing 3 posts - 1 through 3 (of 3 total)
- The forum ‘Support Forum (ARCHIVED – Please use Slack Channel instead)’ is closed to new topics and replies.
Are there any guides or further information on using Lead-DBS for lead localization based on a single postoperative MRI scan? I have successfully localized leads using preoperative MRI and postoperative CT, but I am trying to now complete the process solely with a postoperative MRI. What is the proper name for the nifti file of the postoperative mri that should be in the patient folder? I keep getting an error “Please put a suitable postoperative anatomy file inside the patient folder and normalize it first” on the pre-Reconstruct step.
you’d need a preop scan (call them anat_t1.nii and anat_t2.nii) and at least one postoperative MRI (postop_tra.nii) – call that one tra even if it’s sagittal. If you have multiple postop scans, you can call them postop_tra.nii, postop_cor.nii and postop_sag.nii
Now if you don’t have any baseline preop scan it’s hard to do it (given the lead artifacts will have a nonlinear impact on the normalization step). What you can do is to use the Linear Three-step protocol (but do make sure to read the associated schönecker paper so that you understand what really happens there).
If you want to try that, you’d make a duplicate of the single postop scan and call one copy postop_tra.nii, the other copy anat_t*.nii
Thank you so much for the fast reply. Will test this out now. I did a quick search and came up with this dead url (http://www.andreas-horn.de/leaddbs/Lead_manual/book/Normalization%20of%20Images.html). Can you direct me to the paper you referred to? Thanks!
|cookielawinfo-checkbox-analytics||11 months||This 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-functional||11 months||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checkbox-necessary||11 months||This 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-others||11 months||This 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-performance||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".|
|PHPSESSID||session||This 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.|
|_ga||2 years||This 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_1||1 minute||This cookie is set by Google and is used to distinguish users.|
|_gid||1 day||This 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.|
|CONSENT||16 years 5 months 17 days 13 hours||These 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.|
|IDE||1 year 24 days||Used 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_cookie||15 minutes||This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies.|
|VISITOR_INFO1_LIVE||5 months 27 days||This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website.|
|vuid||2 years||This 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.|
|YSC||session||This cookies is set by Youtube and is used to track the views of embedded videos.|
|yt-remote-connected-devices||never||No description available.|
|yt-remote-device-id||never||No description available.|