Affects: verification of single-unit spike data
This parameter specifies how close two distinct spikes can be to each other. After setting a single-unit data set, the program checks all spikes in it against all other single-unit data sets. If any spikes are closer than this amount of time to each other, they are assumed to be the same spike in more than one data set, and the program warns you of this conflict.
The reason two slightly different trigger times can be considered as identifying the same spike is that separate single-unit can be set using different thresholds. Any spike that crosses both can potentially wind up in both data sets. The trigger times may not be identical, though, since the spike may cross one threshold later than another.
|Key sequence||Parameter||Initial Value|
|<Esc>Wn<CR>SSUOM||Min. interval between spikes||0 msec|