Future development of waveforms #829
Description
As initialized in #457, the current handling of waveforms within the Neo framework is non ideal due to multiple reasons
- unintuitive dimensionality in comparison to
AnalogSignals - bad performance for large datasets / no lazy option here
Suggested changes are:
- Detach the representation of waveforms from
Spiketrains and represent these as separate, more performance oriented object. - Use the
array_annotationmechansims for waveform handling. Potentially there is also a lazy handling of numpy arrays possible here? - More ideas?