Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Batch size #813

Open
hiroyukioya opened this issue Nov 5, 2024 · 3 comments
Open

Batch size #813

hiroyukioya opened this issue Nov 5, 2024 · 3 comments
Assignees

Comments

@hiroyukioya
Copy link

Describe the issue:

not an issue, but if I have recording of duration of 5min, can we use batch size of 5min instead of 2sec? What is your expectation?

Reproduce the bug:

No response

Error message:

No response

Version information:

v 4.0.12

@hiroyukioya hiroyukioya changed the title BUG: <Please replace this text with a comprehensive title> Batch size Nov 5, 2024
@jacobpennington
Copy link
Collaborator

jacobpennington commented Nov 6, 2024

Depending on how many channels your data has, the sorting is likely to fail due to insufficient memory. Sorting is broken up into small batches for more efficient processing, and dramatically increasing the batch size will undo that. As for how that might affect the actual sorting results (assuming you're able to run it), @marius10p would be a better person to answer that.

@marius10p
Copy link
Contributor

It means you won't get good drift correction anymore, since there is one drift per batch, and yes, it will probably run out of GPU RAM too. The edges of the batch should be dealt with correctly by Kilosort4 if that is what you are worried about.

@hiroyukioya
Copy link
Author

Thank you. That is a great info.
I could run it with 5 min batch size (we have small channel count and drift estimation is off). In terms of sorting results, what do you expect the effect of batch size (better for longer batch)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants