Skip to content

Add neuron selection support to SequenceInterpolator and SpikeInterpolator#126

Open
Vrittigyl wants to merge 8 commits intosensorium-competition:mainfrom
Vrittigyl:neuron-selection
Open

Add neuron selection support to SequenceInterpolator and SpikeInterpolator#126
Vrittigyl wants to merge 8 commits intosensorium-competition:mainfrom
Vrittigyl:neuron-selection

Conversation

@Vrittigyl
Copy link
Copy Markdown
Contributor

Description

This PR adds support for selecting specific neurons in both SequenceInterpolator and SpikeInterpolator.

Users can now pass either:

  • neuron_ids: biological neuron IDs mapped using meta/unit_ids.npy
  • indexes: direct neuron indexes

If both are provided:

  • A warning is raised if they refer to the same neurons.
  • A ValueError is raised if they refer to different neurons.

Changes

  • SequenceInterpolator

    • Added neuron filtering using neuron_ids or indexes.
    • Filters loaded data and normalization statistics to match selected neurons.
  • PhaseShiftedSequenceInterpolator

    • Filters phase_shifts to match selected neurons when neuron selection is used.
  • SpikeInterpolator

    • Added neuron filtering using neuron_ids or indexes.
    • Rebuilds the spike array and indices to include only selected neurons.

This allows loading and processing only a subset of neurons, reducing memory usage and improving flexibility when working with imaging datasets.

Closes #124

@gitnotebooks
Copy link
Copy Markdown

gitnotebooks bot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds neuron-subset selection to interpolators so callers can load/process only specific neurons by biological IDs (meta/unit_ids.npy) or by direct column/neuron indexes, reducing memory usage for large datasets (Issue #124).

Changes:

  • Extend SequenceInterpolator to accept neuron_ids / indexes and filter loaded data + normalization stats accordingly.
  • Extend PhaseShiftedSequenceInterpolator to filter phase_shifts consistently with neuron selection.
  • Extend SpikeInterpolator to accept neuron_ids / indexes and rebuild spikes/indices arrays for the selected neurons.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 223 to +276
@@ -230,20 +269,34 @@ def __init__(
else:
self._data = np.load(self.root_folder / "data.npy")

# Filter selected neurons from data
if self.indexes is not None:
self._data = self._data[:, self.indexes]
self.n_signals = len(self.indexes)

Copy link

Copilot AI Mar 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New neuron-selection behavior (filtering _data, updating n_signals, filtering means/stds, and filtering phase_shifts in PhaseShiftedSequenceInterpolator) is not covered by existing tests. Please add test cases exercising neuron_ids and indexes selection (including mismatch between the two, ordering behavior, and normalization stats shape after filtering).

Copilot uses AI. Check for mistakes.
@codecov
Copy link
Copy Markdown

codecov bot commented Mar 11, 2026

Codecov Report

❌ Patch coverage is 77.94118% with 15 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
experanto/interpolators.py 77.94% 15 Missing ⚠️

📢 Thoughts on this report? Let us know!

Comment on lines 286 to 291
@@ -230,20 +290,34 @@ def __init__(
else:
self._data = np.load(self.root_folder / "data.npy")
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO if data gets cached, we should only cache the indexed neurons. Downside is that if someone alters self.indexes of the instance later manually, it is still relying on the old data. But I think I still prefer this. What do you think @pollytur ?

If changing indexes later is a real use case, one could handle it with a function that takes care of it and would reload the data appropriately, but I am not sure we need it right now.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’ve changed the logic so caching happens after applying neuron_indices, so only the selected subset is loaded into memory. According to me this would keep memory usage efficient for large data.
can revert changes if needed

else:
self._data = np.load(self.root_folder / "data.npy")

# Apply indexing BEFORE caching
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @pollytur
as far as I know, if one applies indexes to memmap as lists or arrays, this loads a copy into RAM (see https://stackoverflow.com/questions/18614927/how-to-slice-memmap-efficiently or https://stackoverflow.com/questions/78426050/how-to-index-a-numpy-memmap-without-creating-an-in-memory-copy)
Only regular continuous slicing creates just a view, but I don't think neuron ids will always be continuous.

Have you thought about this? We might need to set caching to True if neurons are indexed. Or we find a workaround (I haven't investigated it yet).

Copy link
Copy Markdown
Contributor

@pollytur pollytur Mar 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great catch, no I have not thought about it tbh
we probably want to investigate the workaround (changing order of neurons as we need and save it as a temp memmap file is the first though but thats insanly memory inefficient since neuronal responses are also the heaviest part of the dataset from a memory perspective...)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or maybe instead of directly indexing, we could iteratively fetch only the required columns (or in chunks) and optionally cache them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add an option to select specific unit_ids or just indexes of neurons

4 participants