Axel Huebl

@s-sajid-ali just checking where you found `read_iterations` in the docs/examples - we just want to make sure we don't accidentally advertise it outside of streaming (read-once) workflows yet :)

I see, yes the comment ```py # In parallel contexts, it's important to explicitly open iterations. # This is done automatically when using `Series.write_iterations()`, # or in read mode `Series.read_iterations()`....

Thanks a lot! Can you isolate the last commit as a bugfix PR for 0.16.0?

This https://github.com/spack/spack/pull/45582 worked for me locally, let's see if it fixes here.

We have an implementation in Geant4 that we used to write particles that we then load in WarpX. You can find the implementation here: https://github.com/LDAmorim/GPos

That's a great point and was a bit undervalued for the initial binding implementation. One can add to a pybind binding multiple optional arguments with a raw string (body) and...

Refs.: - Quincy Koziol's ATPESC23 or HUG23 slides (to be linked) - @jeanbez's HUG23 slides https://docs.google.com/presentation/d/1AdQNynZ7Qe40fdwNQ_MvZFBPVWZd4x6GuCUx6IkfWxU/edit#slide=id.g23ba479a05a_0_7

As a side note, there are non-blocking MPI-I/O ops now coming to MPI (cutesy of Quincy Koziol's work on the standard). HDF5 is planning to use it to introduce async...

Other details: - check `H5Pget_mpio_actual_io_mode` and of not as expected, `H5Pget_mpio_no_collective_cause` Things like accidental **datatype** conversions, **dataspace** conversion (both between declaration and write) and too small I/O requests (

ah, actually the exception has the name: > Further description: [HDF5] Unsupported simple attribute type 216172782113784119 for position.