Join GitHub today
Installation issues with support for Python API #279
@ax3l I am really glad you're taking much efforts to have people adopt these standards which I hope people really do!
Yep, it did build smoothly with no problems when I passed no arguments but there was some trouble when passing
It's been a while since I tried to build but AFAIK there was some error regarding
That error regarding
I tried looking up and I think installing ADIOS might fix it but it was mentioned in under optional I/O dependencies in the README (and/or it could be that I have pybind installed incorrectly) but I didn't really try installing it yet. I guess I'll tinker a bit more and might raise an issue in OpenPMD-API repo with feedback on what could have been better in my perspective. :)
Also, I tried installing it with spack
but for some reason spack always ended up installing Python 2.7.15 even when I created a symbolic link in
Initially it did say it was running Python 3.6 with
And conda installation really did go smooth, no errors in da way. :D
That said, I am myself very new to HDF5 and OpenPMD in general, so it may be just something to do with my lack of clear understanding at the moment. :/
This report is just a copy-paste from PlasmaPy/PlasmaPy-PLEPs#13 (comment).
Dear @ritiek, thank you a lot for trying out the API and your detailed report!
MPI support for openPMD-api means: MPI parallel backend support for clusters. For example, parallel HDF5 or MPI aggregated ADIOS1 writing. MPI-enabled libraries should always be build from source on clusters, for various reasons (stability, hardware support such as infiniband, performance).
Nope, adios is just yet another backend that can write serial and MPI parallel files :-) You want ADIOS if you write on large clusters with more than ~1'000 MPI ranks (for example, see: https://arxiv.org/abs/1706.00522).
yay, excellent! :)
Don't worry, these are exactly the reports we like :-)