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

[Major] No support for standard neurodata formats #9

Closed
vigji opened this issue Jan 4, 2024 · 2 comments
Closed

[Major] No support for standard neurodata formats #9

vigji opened this issue Jan 4, 2024 · 2 comments

Comments

@vigji
Copy link

vigji commented Jan 4, 2024

As the package aims at helping out people dealing with their own recordings and experiments, it would greatly benefit from supporting standard neuro data formats.

I believe that the impact of the tool would be way larger if there were some more integration with the existing ecosystem of data formats, in the current shape it feels a bit a lab-specific tool (format-wise), instead of forcing the user to structure their dataset to the highly specific requirements of the package. I could recommend for example look for at least proof-of-principle integration with NWB, or SpikeInterface.

A good way of smoothing this up would be to showcase the software on openly accessible datasets, instead of the custom datasets provided as examples.

@calebweinreb
Copy link
Owner

Thanks for the suggestion!

Right now the software is relatively format-agnostic. Most of the io functions ingest numpy arrays directly, rather than paths to data in a specific format. So in a sense it is no more format-specific than matplotlib.

I agree that interfacing with standard formats would be useful through. To that end, we developed a conversion tool that generates SNUB datasets directly from NWB files (see #17). See documentation here: https://github.com/calebweinreb/SNUB/blob/dev/docs/source/nwb.rst

@vigji
Copy link
Author

vigji commented Feb 5, 2024

I see the point that you make in referring to it as an almost matplotlib-like tool in being data-agnostic. Still, I feel that including pipelines to generate the data from nwb files does lower the energy barrier for adoption for new users, and gives a good tool to dig into open datasets. I feel that this is addressed now!

@vigji vigji closed this as completed Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants