Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
- The forum ‘Support Forum (ARCHIVED – Please use Slack Channel instead)’ is closed to new topics and replies.
I was looking at the electrode coordinates from STN DBS in MNI space, and congruently with your paper on probabilistic conversion, the z-coordinates were at about -6. But the AC z-coordinate was stated to be at about +3 or 4, which is strange because that would place the electrode 9 mm below the AC, while when converted to AC/PC coordinates it was at 3 mm below MCP.
Accoding to Brett (2002) the origin of the MNI space was at about 4 mm above the AC.
Therefore my question is, how is the AC coordinate defined? Is the sign for the z-coordinate the same as for the other coordinates, up being positive and down negative?
I assume you’re referring to the reco.acpc coordinates inside the ea_reconstruction.mat file?
Indeed, I just checked and am not entirely sure if these are correct. In fact, the option to write out ACPC coordinates has been disabled by default a while ago but if you have an older installation (with older prefs), it would still do it in your case.
There is an MNI to ACPC tool (inside the tools menu) in which you can map from MNI to ACPC based on selected patients. In there, it is unequivocal how coordinates are mapped and to which point they refer to. Please use this one instead.
The AC lead-dbs uses is at -0.5948, 2.1606, -3.2329 mm which I drew in per hand. However, it’s in 2009b NLIN ASYM space as everything in Lead-DBS, so not the 152 space Brett refers to (more on this here: http://www.lead-dbs.org/?p=1241).
Hope this helps!
(will check and correct if necessary the acpc coord writeout in the next release).
|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.|