Hi, iEEG epilepsy researcher here. I wanted to ask about how to best annotate white matter and other channels that might not be part of your interest. Other examples include: out, csf, ventricle. Ideally there is a place to annotate this within the BIDS layout for iEEG data. This specifically comes up for SEEG (depth electrodes).
Currently iEEG-BIDS channels.tsv file has “status”, which is constrained to “good/bad”, and status_description. Would this be the right data points to modify to account for that?
The location of the electrodes and therefore the properties of the tissue at the location should actually be noted in the _electrodes.tsv file. If you add custom columns this should indeed be described in an _electrodes.json file as indicated by @sappelhoff
Properties of the amplifier and recorded signals are stored in the _channels.tsv If a recorded channel has a bad signal because it is in the csf, this can be described in the _channels.tsv file. The reason for this is that BIDS makes a clear distinction between electrodes (hardware contacts at a certain position) and channels (signals recorded by the amplifier).
I was validating our dataset with the BIDS validator, and got this error:
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a “.bidsignore” file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
I got the same error for events. tsv.
Both files are at the level mydataset/events.json and mydataset/electrodes.json. Do you have any recommendations what is causing this error?