Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Best way to record/store electrode locations #20

Open
rachaelgarner opened this issue Jan 17, 2019 · 1 comment
Open

Best way to record/store electrode locations #20

rachaelgarner opened this issue Jan 17, 2019 · 1 comment
Assignees
Labels

Comments

@rachaelgarner
Copy link

Hi, I'm working on registering the electrode contacts for a subject into a common space. Many of our subjects are using a 10/20 system, so I have each contact labeled as Cz, Fp1, etc. I found a study (Okamoto et al., 2004) that reported cartesian coordinates for this system in MNI space, and am wondering if these would be readable by RAVE? Also if so, where in my directory should I include a txt/csv file with the coordinates? From the demo data it looks like electrodes.csv is in data_dir, not raw dir, so would it be better to import the electrode coordinate file following preprocessing? Thanks!

10-20tomni

@dipterix
Copy link
Collaborator

@rachaelgarner During the preprocess, RAVE will automatically generate several "meta" files. electrodes.csv is one of them. By default, all electrodes will be set to (0,0,0) with a blank label. You can open this file, copy-paste MNI x, y, z here directly to Coord_x, Coord_y, Coord_z in electrodes.csv. The column Label is for the electrode name. Then RAVE will render whatever coordinates given in this file.

Here's an example of electrodes.csv.

An example of electrodes.csv

To find this csv file, let's say your project is MyProj and subject code is sub1 and data_dir is using the default directory, then in ~/data_dir/MyProj/sub1/rave/meta/electrodes.csv.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants