Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add functionality for analyzing data streams #38

Closed
ajtritt opened this issue Jun 23, 2017 · 1 comment
Closed

add functionality for analyzing data streams #38

ajtritt opened this issue Jun 23, 2017 · 1 comment
Labels
category: enhancement improvements of code or code behavior priority: high impacts proper operation or use of feature important to most users
Milestone

Comments

@ajtritt
Copy link
Member

ajtritt commented Jun 23, 2017

Originally reported by: Andrew Tritt (Bitbucket: ajtritt, GitHub: ajtritt)


Within the specification, there are fields that can be determined from other datasets that might be written from a DataChunkIterator. For example, the field .num_samples can be determined from .data. If data is passed in as a DataChunkIterator, num_samples can only be determined when the DataChunkIterator is exhausted.

We need a class that can analyze a DataChunkIterator while it is being read from. Once the DataChunkIterator is closed, this class should be able to call back to some other object for further processing (e.g. setting a variable), or provide a way for its result to be read.


@ajtritt ajtritt added priority: high impacts proper operation or use of feature important to most users category: enhancement improvements of code or code behavior labels Aug 3, 2017
ajtritt added a commit that referenced this issue Aug 9, 2017
@oruebel oruebel added this to the NWB 2.x milestone Oct 23, 2017
jcfr pushed a commit to jcfr/pynwb that referenced this issue Jan 29, 2019
@rly
Copy link
Contributor

rly commented Apr 11, 2024

Closing because not a priority requested by users, though @CodyCBakerPhD et al are working on improved progress bars around DataChunkIterator.

@rly rly closed this as completed Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: enhancement improvements of code or code behavior priority: high impacts proper operation or use of feature important to most users
Projects
None yet
Development

No branches or pull requests

3 participants