mne-tools / mne-tools/mne-python

BUG: Check volumetric and surface morphs

Open
#9,138 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

BUG
Dominant language
Python
Stars
3.5k
Forks
1.6k
Avg merge
1d 6h
Merged PRs (30d)
100

Description

@britta-wstnr mentioned that the volumetric morphs might not (sufficiently) uniformly represent the data in the destination subject's space (e.g., voxel 1 might show up 10% as much as voxel 2). This is something that I think we can and should investigate by at least comparing surface to volumetric morphs. In particular we can:

  1. Compare the morph_mat sparse representations in terms of row and column norms (assuming we roughly match the numbers of rows and columns)
  2. Compare the distribution of neighbor-distances in the original subject space (dirac delta at pos for volume, some smooth narrow-ish distribution around some dist in mm for surface) to those of the spatially equivalent points (probably based on argmax?) in the destination subject's space.

From these we can see if surface and volume have similar before/after distributions, so we at least know how comparable the two solutions are.

I have some adult data I could use for this, including with functional localizers.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the volumetric and surface morph implementations that produce the morph_mat sparse representations and use pos for spatial points. Compare row and column norms, then compare neighbor-distance distributions between original and destination subject spaces using the adult data mentioned. Done means documenting whether the surface and volume morphs have comparable before-and-after distributions.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.