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.

Sign up for GitHub

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

Jump to bottom

Improved data integrity checking #3

Open
153957 opened this issue Jun 22, 2014 · 0 comments
Open

Improved data integrity checking #3

153957 opened this issue Jun 22, 2014 · 0 comments

Comments

@153957
Copy link
Member

153957 commented Jun 22, 2014

Given the occurances of bad data: HiSPARC/publicdb#63
Of which I suspect may be due to data corruption, other may just be due to migration issues.
We could activate the fletcher32 option for PyTables, this means that checksums will be made for all data, which will ensure data integrity.

Additionally we could enable blosc data compression to possibly save some space and speed up data read out (making IO less of a bottleneck).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@153957