SpikeInterface / SpikeInterface/spikeinterface

Remove metrics if external packages dependencies are not met

Open
#4,323 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

metrics
Dominant language
Python
Stars
847
Forks
280
Avg merge
3d 9h
Merged PRs (30d)
29

Description

Following up on this: #4292

Comment from @h-mayorquin: https://github.com/SpikeInterface/spikeinterface/pull/4292#issuecomment-3728777082

E.g., if rp_violations requirs numba and numba is not installed, remove it from computation instead of returning NaNs

Contributor guide

No contributing guide indexed for this repository

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 with the rp_violations metric and follow the discussion in #4292, especially the linked pull request comment. Trace how external dependencies such as numba are checked and how unavailable metrics currently produce NaNs. Done means a metric whose dependencies are missing is removed from computation rather than returned as NaNs.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.