Skip to content

Conversation

@alejoe91
Copy link
Member

Fixes #367

@alejoe91 alejoe91 changed the title Add mux_index contact annotation Add mux_index contact annotation Oct 13, 2025
@codecov
Copy link

codecov bot commented Oct 13, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.13%. Comparing base (92c8d05) to head (0855236).
⚠️ Report is 17 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #368      +/-   ##
==========================================
+ Coverage   90.11%   90.13%   +0.02%     
==========================================
  Files          12       12              
  Lines        2083     2088       +5     
==========================================
+ Hits         1877     1882       +5     
  Misses        206      206              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@h-mayorquin
Copy link
Collaborator

#367

I find mux_index and mux_channels confusing and somewhat clashing with other concepts, as "index" and "channel" are already overloaded terms in our ecosystem. Could we take this opportunity to improve the naming?

  • For the index of the ADC to which the contact belongs, I propose adc_group or adc_index
  • For the order in which the contact is sampled within the ADC, I propose adc_sample_position or adc_sample_order.

@alejoe91 alejoe91 changed the title Add mux_index contact annotation Add adc_group/adc_sample_order contact annotation Oct 21, 2025
probe = _make_npx_probe_from_description(
pt_metadata, probe_part_number, elec_ids, shank_ids=shank_ids, mux_info=mux_info
)
if chans_saved is not None:
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
if chans_saved is not None:

(this doesn't matter, but it's existence made me stare at the indentation for ages to check it was right...)

Copy link
Member Author

Choose a reason for hiding this comment

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

not sure I understand!

Copy link
Member Author

Choose a reason for hiding this comment

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

Oh I think I understand. We need this in both cases (if probe is none or not)

Copy link
Member

Choose a reason for hiding this comment

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

I just meant that there was a repeated if chans_saved is not None, but you're right that it should have been moved down an indentation. Nice catch!

probe = np_probe_info.get("probe")

if probe is None:
# check if subset of channels
Copy link
Member

Choose a reason for hiding this comment

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

This comment should move to the chans_saved code too

@alejoe91 alejoe91 merged commit b43450b into SpikeInterface:main Oct 25, 2025
9 checks passed
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.

ADC information when subset of channels are saved

4 participants