Artifact detection enforcement in the v1 spikesorting pipeline

[samuelbray32]

Working on helper functions for finding spikesorting merge ids based on a restriction and ran into a few questions:

• The v1 spikesorting pipeline no longer enforces that users run artifact detection. This is divergent from the v0 pipeline where it was required (with the option of artifact parameters=None)

• This means that the path for tracing an experimental interval like an epoch to the spikesorting is dependent on whether artifact detection is used.

• If this is intended, I think the Tutorial notebook should emphasize usage of the tables clearly. From personal experience, the LFPV1 pipeline follows this unenforced artifact detection and makes it easy to miss the options.

Open to other suggestions on how to make this smoother as well

[edeno]

@khl02007 thoughts on this?

[samuelbray32]

Adjacent to this, the example notebooks for clusterless and sorted decoding don't restrict to sorts from a given interval in making the groups, which is non-trivial if artifact was used.

Making a helper function to find sorts of interest to help with this