contact_ids?

Open
#263 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Start with the ReadTheDocs format specification linked in the issue and compare it with the example JSON file in the probeinterface_library repository. Document the existing contact_id field in the format specification, using the example to verify its spelling and placement; done means the field is described on the documentation page.

Written by the indexing model from the issue text.

Description

enhancement format

There are examples of json files with contact_id, e.g. https://github.com/SpikeInterface/probeinterface_library/blob/main/neuronexus/A4x8-5mm-100-400-703/A4x8-5mm-100-400-703.json

however the ReadTheDocs does not mention this field: https://probeinterface.readthedocs.io/en/latest/format_spec.html

Dominant language
Python
Stars
85
Forks
49
Avg merge
13h 47m
Merged PRs (30d)
3

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.

More from SpikeInterface/probeinterface

All issues in SpikeInterface/probeinterface

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.