Custom coordinates - which space?

46 views
Skip to first unread message

Grace Edwards

unread,
May 5, 2023, 5:57:31 PM5/5/23
to roast-users
Hi Andy,

We are stimulating hMT/ Vertex using predetermined coordinates  - i.e. 3 cm dorsal and 5 cm leftward for hMT. Using brainsight, we then localize exactly where the electrodes are in each individual so we can run a simulation using roast(). I have the custom coordinates in MNI space for each participant - what space is roast expecting in the subj_customLocations txt file

Thanks,
Grace

Yu (Andy) Huang

unread,
May 6, 2023, 5:37:51 PM5/6/23
to Grace Edwards, roast-users
Hi Grace,

That text file expects coordinates in the voxel space of the original MRI that you'll use to run the simulation. 

Hope this helps.

--
You received this message because you are subscribed to the Google Groups "roast-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to roast-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/roast-users/87cf0575-7792-42e9-a1d6-a448f6858571n%40googlegroups.com.

Grace Edwards

unread,
May 18, 2023, 12:02:08 PM5/18/23
to roast-users
Hi Andy,

I have tried running roast using all the possible coordinates read out from brainsight (brainsight, nifti, MNI - which I converted back to voxel space using MNI2slice.m) on our native space anatomical and the electrodes end up in odd positions - sometimes overlapping or totally off the head (closer to where the neck would be - see the example attached). Do you have any ideas as to what might be happening? I have also attached our coordinates file.

Thanks,
Grace
S16.anat_customLocations
Example.png

Grace Edwards

unread,
Jun 14, 2023, 2:24:14 PM6/14/23
to roast-users

Hi Andy,

I'm still trying to figure out my coordinates problem, and it seems that my issue doesn't just lie with the coordinates, so potentially a combination between the coordinates and anatomical? I came to this conclusion by running a simulation using T5 and Cz ("roast([pathnameNative,'/',sub,'.anat.nii'], {'T5',0.75,'Cz',-0.75}, 'electype', {'pad','pad'}, 'elecsize', {[50,50,3],[50,50,3]}, 'simulationTag', 'hMTsimulation_EEG') (see photo1), and navigating in the electric field window (see photo2), I localized a voxel under each of my electrodes to see if I could reproduce the simulation using custom coordinates of provided in voxel space (e.g. T5 at 59,73,128 in photo2). 

Adding these coordinates to my custom locations file, I then ran the a simulation, but I wasn't able to replicate the T5 - Cz simulation instead I got a strange output (photo3)… what do you think could be going on here?

Thanks,

Grace

photo3.png
photo1.png
photo2.png

Yu (Andy) Huang

unread,
Jun 15, 2023, 7:30:24 PM6/15/23
to Grace Edwards, roast-users
HI Grace,

The problem may be that you did not provide the custom electrode coordinates using the original MRI. ROAST will do some preprocessing if the original MRI is not in standard orientation. So if you want to place electrodes at customized locations, please get the coordinates using the original MRI (the MRI you used to run ROAST). See this example for more information.

Hope this helps. 

Reply all
Reply to author
Forward
0 new messages