-
Notifications
You must be signed in to change notification settings - Fork 32
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
What is the status of and where is this project heading #39
Comments
Thank you for the interest. The target is to provide general, seamless persistence for modern C++. In the next release will support sparse matrices, STL like objects including the full standard template library, and will come with improved documentation. In addition to 'regular' features there is much thought put into performance, MPI parallelism and filtering pipline. However most of the work is not coding related. To give you an example: Sparse matrices have been handled various ways across platforms, to add complexity the HDFGroup based on FNAL study will be adding CAPI supported format. To coordinate and leverage the differences requires detailed understanding of the problem. As for the 'back burner': I am financing this project from my own pocket, therefore there is priority to components my clients need. If you are an organisation that would benefit from a cross platform HPC capable general, seamless persistence for modern C++ and interested in funding the project please get in touch. steve ps. here is the link to the HDF5 Forum where I respond to H5CPP (or often HDF5 CAPI) related questions: |
@steven-varga thank you for this explanation, this is great feedback. |
This seems like a really great tool and would like to be a user, however I am wondering what the future of this project will be in terms of vision and timing. It sounds like maybe this is on the development back burner due to other exigencies or funding. If there is a better forum for this I am happy to move this somewhere else. I am mostly curious where it's going or could go.
The text was updated successfully, but these errors were encountered: