You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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.
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.
The text was updated successfully, but these errors were encountered: