Currently, spikes in a spiketrain are not sorted in time. This could be confusing for users. On the other hand, sorting should not just automatically happen, as this may also cause bugs. This issue aims to find a clear, transparent solution (in code and/or documentation) to define if and when Spiketrains are sorted.
Currently, spikes in a spiketrain are not sorted in time. This could be confusing for users. On the other hand, sorting should not just automatically happen, as this may also cause bugs. This issue aims to find a clear, transparent solution (in code and/or documentation) to define if and when Spiketrains are sorted.