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

Adding more options for data storage #82

Open
swkeemink opened this issue Mar 2, 2020 · 4 comments
Open

Adding more options for data storage #82

swkeemink opened this issue Mar 2, 2020 · 4 comments

Comments

@swkeemink
Copy link
Member

Currently all extracted and separated data are stored as .npy files. A more common storage format would be HDF5, and for some user cases it might also be useful to not store anything at all.

I propose an optional argument like 'file_format', which can be 'npy', 'HDF5', or None.

This relates to #22 and might solve #81 .

@scottclowe
Copy link
Member

I support this enhancement going ahead.

@swkeemink
Copy link
Member Author

I have added the option for defining the data format as None, but still need to work on an hdf5 implementation. See pull request #86.

@scottclowe
Copy link
Member

We already have an issue for adding HDF5 support: #22.

@swkeemink
Copy link
Member Author

It wasn't written very well, but that one is for loading hdf5 files into FISSA containing ROIs or imaging data. However we should probably just combine them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants