Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Addressing Kilosort3 Errors

未关闭
#66 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
文档
描述清晰度
需要澄清
活跃度
停滞
技术栈
docker

调研方向

Start by reviewing the containerized Kilosort3 build process and the linked SpikeInterface and Kilosort issues. The issue does not name files, tests, or a defined documentation target; completion would require an agreed scope, such as documenting how these images are built or updating the containerized Kilosort3 version.

由索引模型根据 Issue 内容生成。

描述

Hello

In running the containerized version of Kilosort3 with spike interface, we've been running into some errors that seem to be related to the underlying Kilosort3 code, not spike interface or the containerization (similar to https://github.com/SpikeInterface/spikeinterface/issues/2272). I have some experience trying to fix these errors inside kilosort (e.g., https://github.com/MouseLand/Kilosort/issues/285). Would it be possible for me to try to build updated versions of the containerized Kilosort3 that you all create for spike interface after having attempted to debug the original Kilosort3 code? I'd appreciate any resources or information you could pass along on how you build the containerized versions so I can follow the same process. If this information is readily available somewhere, I apologize. I've never built a containerized version of a piece of software like this, so it is new to me. Thank you!

~Nick

主要语言
Dockerfile
星标
9
派生
8
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

SpikeInterface/spikeinterface-dockerfiles 的其他 Issue

查看 SpikeInterface/spikeinterface-dockerfiles 的全部 Issue

相似的 Issue

更多 DevOps Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。