Currently, there are 3 different sorting approaches implemented
The latter two are basically identical in terms of workflow, so they are described in the same section. For the waveclus pipeline, waveclus preprocessing to create snippets from Broadband is required.
How to use waveclus to sort spikes is a topic on its own, please see Waveclus for more detailed information
Sorting in plexon is - similar to waveclus - a topic on its own. However, there are a few internal rules:
All of these issues can make online snippet sorting very difficult. However, realigned snippets will have the (due to shift) missing information padded with 0's. This means that shifted snippets might appear like a different cluster. So they will potentially have to be sorted with redefined principle components for each subset.
Session_blocks_N.plx are based on online snippets
Session_realigned_blocks_N.plx are based on realigned online snippets
Session_from_BB_blocks_N.plx are based on waveclus clustering
Importantly, when you save a plx file, it never overwrites an existing file, but rather appends “-01” to the file name. If that filename already exists as well, it will append “-02” instead, and so on. That means, all files with “-NN” affixes are manually saved. Because of that, for all steps after sorting, the plx file extension (-01, -02, …) to use is defined in the plx_file_table.