ieeg electrode annotation and surface-labelling #482
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was a request from some of our clinical collaborators here (@arunthurai is helping facilitate this), for being able to identify what hippocampus label is associated with each electrode contact, and provide some means for visualizing these in group space. It allows the user to define another image as the anatomical reference space too..
@jordandekraker I know you have a hippomaps example using ieeg data, but the use-case and input data are a bit different. In your example you're calculating something per electrode using non-bids data, mapping it to volume-space (with a radius around each electrode), and then mapping it to the hippocampus surfaces. Here we are making use of a BIDS electrodes tsv file as input, and simply finding the closest hippocampal vertex, and annotating the tsv file, along with creating gifti outputs to indicate the closest vertex for each electrode contact.
Anyways happy to discuss this further in case we want to expand on this (leaving it as a draft for now)..
Happy to also discuss general issues of scope of hippunfold -- I see this PR as within scope of hippunfold (and not part of a separate tool) because it is relying on BIDS spec inputs (e.g the ieeg electrodes tsv file), and producing outputs that are congruent with the existing hippunfold outputs. I.e. something that provides some minimal mapping which users could then make use of in their more involved analyses..
@arunthurai if you want to try it out, something like this should work (needs the --path options because of the peculiarities of your bids dataset):