You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The epoch table is currently a compound-dtype table. This makes it hard to extend and inefficient for querying along a single feature.
Part of this move of making Epochs a DynamicTable should also involve removing the use of RegionReferences for indexing into an array of TimeSeriesIndex. Removing this will make the schema less dependent on HDF5 primitives and make it easier to use alternative backends.
Problem/Use Case
The epoch table is currently a compound-dtype table. This makes it hard to extend and inefficient for querying along a single feature.
Part of this move of making Epochs a DynamicTable should also involve removing the use of RegionReferences for indexing into an array of TimeSeriesIndex. Removing this will make the schema less dependent on HDF5 primitives and make it easier to use alternative backends.
Relates to #643
Checklist
The text was updated successfully, but these errors were encountered: