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

Feature request: Excluding a time range for spikesorting. #157

Closed
bapungiri opened this issue Dec 11, 2019 · 2 comments · Fixed by #595
Closed

Feature request: Excluding a time range for spikesorting. #157

bapungiri opened this issue Dec 11, 2019 · 2 comments · Fixed by #595
Labels
enhancement New feature or request

Comments

@bapungiri
Copy link

It will be helpful if certain time periods can be excluded from spikesorting. Specially helpful for really long recordings where small unavoidable noisy periods can influence unit isolation/cluster-quality. This will eliminate an added step of creating another binary file excluding those noisy periods. This may also be helpful in excluding other irrelevant epochs for analysis.

@chris-angeloni
Copy link

You can set ops.trange = [0 inf]; to include a time range that doesn't include noise. I'm not sure if this is good for indexing multiple periods though?

@marius10p
Copy link
Contributor

ops.trange currently only works for a single continuous segment of the recording. We would need to keep track of one time offset per batch, which is doable, but I won't have time to do for a while.

@marius10p marius10p added the enhancement New feature or request label Dec 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants