SpikeInterface / SpikeInterface/spikeinterface
Multiple template comparison 'm_tcmp'
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
Hi,
I have used pairwise 'p_tcmp' comparisons for matching units in two recording sessions and it works with the agreement scores. However, when I am comparing/matching multiple recordings m_tcmp I am not sure what feature to use, since m_tcmp don't take agreement_scores.
My goal is to match units in all recordings at once instead of going through pairs. Doing it pair by pair, which I have been ding so far, is time intensive to match across multiple recordings.
Please let me know how could I create something like an agreement scores that will allow me to match the similarity of unit templates across multiple recordings.
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the documentation or API entry points for p_tcmp and m_tcmp, focusing on how agreement_scores is handled for pairwise versus multiple recordings. Determine whether a multi-recording similarity or agreement feature is feasible, and define completion as either supporting the requested matching workflow or documenting the available approach and its limitations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100