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
num_regression with storage in NPZ files? #71
Comments
Hi @tovrstra! Thanks for the suggestion. Yeah I think an option to We would love to review a PR in that direction. 👍 |
I'm interested in this, specially for 2d arrays (e.g. For comparing scalar fields).
Perhaps I'm overthinking. Anything that improves the current implementation is actually very welcome, IMO! |
Thanks for the enthusiasm! Just a quick attempt to answer a few of the questions:
|
SGTM. About the error reporting, I think you can choose whatever you think its good enough for a first version, and perhaps we could discuss further in the PR :) |
Fixes ESSS#71 This is a first attempt, including unit tests. Also some minor issues in DataFrameRegressionFixture were fixed, which was used as a starting point for this PR. The new fixture only uses NumPy, so also the error message makes no use for pandas for formatting the errors.
It would be useful to store numerical results in NPZ files, because these files can contain arrays with arbitrary shapes. Also for large arrays, this format is more compact (binary + compression), which is useful when dealing with large arrays. The downside is obviously that NPZ files are not human-readable. Would this be a feature of interest for the project? Are there currently other ways of handling large (say 10^6 elements) and/or high-dimensional arrays?
The text was updated successfully, but these errors were encountered: