SpikeInterface / SpikeInterface/spikeinterface
relative paths
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
We currently use spikeinterface in a pipe, when for each new recording the script
- creates a new directory,
- does preprocessing saved into
(recording directory)/preproc, - runs spikesorter of choice,
- saves sorting into directory
(recording directory)/sorting-savedand - runs wave extractor(s) which saves results into
(recording directory)/waves.
I can then use the waves folder to see the results.
However, we save all data and processing in a central storage. After copying the results there and downloading them onto another computer, nothing works. The culprits are absolute paths in JSON files.
Would it be possible to use relative paths that will be agnostic of the absolute location of the result folders?
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 tracing the JSON files written for the preproc, sorting-saved, and waves directories, then reproduce the failure by moving the result folders to another computer. Check how those files refer to their output locations. Done means copied results can be downloaded elsewhere and used without absolute-path failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100