SpikeInterface / SpikeInterface/spikeinterface

SpykingCircus2 Spike Sorting/Multiprocessing

Open
#2,840 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hi all,

I am currently attempting to run SpykingCircus2 on some .pl2 data, but I keep running into a RuntimeError:

RuntimeError:
An attempt has been made to start a new process before the
current process has finished its bootstrapping phase.

    This probably means that you are not using fork to start your
    child processes and you have forgotten to use the proper idiom
    in the main module:

        if __name__ == '__main__':
            freeze_support()
            ...

    The "freeze_support()" line can be omitted if the program
    is not going to be frozen to produce an executable.

I know this order is related to multiprocessing, but I have tried multiple methods (run_sorter_jobs, set global job kwargs) to run without necessarily using multiprocessing. Is this just an open issue or is there a way to address this? Also, let me know if I should provide code or the full error trace.

Thanks!

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 by reproducing SpykingCircus2 with the reported .pl2 data and inspect the multiprocessing behavior around run_sorter_jobs and global job kwargs. The issue does not name files or tests; done means establishing a reproducible cause and a documented way to run the sorter, with the full traceback or example code if needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.