whoisyourneighbour

How to know EEG channel neighbours

https://github.com/rahulvenugopal/whoisyourneighbour

Science Score: 44.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
    Found CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (7.6%) to scientific vocabulary
Last synced: 6 months ago · JSON representation ·

Repository

How to know EEG channel neighbours

Basic Info
  • Host: GitHub
  • Owner: rahulvenugopal
  • License: mit
  • Language: MATLAB
  • Default Branch: main
  • Size: 284 KB
Statistics
  • Stars: 0
  • Watchers: 2
  • Forks: 0
  • Open Issues: 0
  • Releases: 1
Created over 2 years ago · Last pushed 11 months ago
Metadata Files
Readme License Citation

README.md

Do you really know your neighbourhood?

So, I came across this warning in Fieldtrip toolbox website

The context

  • Whenever we use spatially spanning cluster-level statistics, it is very important for the algorithm to know what electrodes are near each other
  • Each cap maker has their own way of putting up where electrodes are in space (X, Y, and Z values)
  • Somewhere in the study, we choose neighbours for each electrode, either on purpose or by default (mostly by default)
  • You may lookup the ftprepareneighbours function to know in depth about common methods (distance, triangulation, template) in this domain
  • BY the way, mne uses Delaunay triangulation for this and I opened my mouth widely on seeing the warning in mne's documentation page

If you're taken aback by these intricate nuances or wondering what on earth I'm referring to, delving into one of my previous Readme files could provide some clarity

Let's take a step back and examine the issue from its foundation

Take a look at the 64 channel montage from easy cap for actiChamp plus amplifier from brainproducts

  • Take Fz electrode, who are its neighbours?

  • [ ] F1, F2
  • [ ] F1, F2, AFz, FCz
  • [ ] F1, F2, AFz, FCz, AF3, AF4, FC1, FC2

  • Establishing a neighborhood boundary is tricky (now I know the logic of territory wars). Where does us end and them begin if you want to think like Sapolsky. Eh, I've gotten off track. Now, think about Cz. If you are one of those who thought I was being generous with option C in the previous example, booom!

Hope I have convinced you about Knowing Thy Neighbours. Amen

By the way, you will find a small matlab script which will objectively tell you who are your neighbours based on a simple distance measure calculated from your own cap manufacturer's locations (I mean X, Y, Z locations) in this repo

Owner

  • Name: Rahul Venugopal
  • Login: rahulvenugopal
  • Kind: user
  • Location: Bengaluru
  • Company: Centre for Consciousness Studies, NIMHANS

PhD Scholar, Centre for Consciousness Studies, NIMHANS, Bengaluru, India. Consciousness-Cognition-EEG-Sleep-Meditation-Statistics-Dynamical Systems-Dataviz

Citation (CITATION.cff)

# This CITATION.cff file was generated with cffinit.
# Visit https://bit.ly/cffinit to generate yours today!

cff-version: 1.2.0
title: TFCE cluster setup
message: 'If you use this software, please cite it as below.'
type: software
authors:
  - family-names: Venugopal
    given-names: Rahul
    orcid: 'https://orcid.org/0000-0001-5348-8845'
    affiliation: Centre for Consciousness Research
identifiers:
  - type: doi
    value: 10.5281/zenodo.15244373
repository-code: 'https://github.com/rahulvenugopal/WhoIsYourNeighbour'
abstract: >-
  This code is used for multiple research works where we
  define the neighborhood based on the channel location file
  provided by the EEG amplifier and cap manufacturers
keywords:
  - EEG
  - TFCE
  - Cluster stats
license: MIT
version: 1.0.0
date-released: '2025-04-19'
doi: 10.5281/zenodo.15244373

GitHub Events

Total
  • Release event: 1
  • Push event: 3
  • Create event: 1
Last Year
  • Release event: 1
  • Push event: 3
  • Create event: 1