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
DataChunkIterator currently assumes that the iterator yields one element along the iteration dimensions at a time. We should clarify this in the documentation:
Add to the main docstring of DataChunkIterator a note that describes the expected iteration behavior
Add note to DataChunkIterator.maxshape to indicate that for iterators this adds a dimension to the chunk generated by the iterator. E.g. if the iterator produces chunks of (x,y) the DataChunkIterator will have a shape of (None, x, y)
Enhance DataChunkIterator to allow iterators that return multiple blocks of data along the iteration dimension. This is useful in case where, e.g., reading single timesteps from a file is very expensive and we want the iterator to return a range of timesteps directly from the file. This would require an additional parameter to control this behavior, e.g., multistep_chunks=True to indicate that chunks retrieved from the iterator contain multiple parts along the iteration dimension.
Description
DataChunkIterator currently assumes that the iterator yields one element along the iteration dimensions at a time. We should clarify this in the documentation:
Alternative approach:
multistep_chunks=True
to indicate that chunks retrieved from the iterator contain multiple parts along the iteration dimension.This has come up on the NWB Slack channel https://nwb-users.slack.com/archives/C5XKC14L9/p1622668229009900?thread_ts=1622588105.009100&cid=C5XKC14L9
Checklist
The text was updated successfully, but these errors were encountered: