Axel Huebl

Hi @wwshunan , Thank you for the question. In order to get a complex embedded boundary from STL files with varying potential on it into a WarpX simulation, you need...

Sounds good :+1: We could also separate into default/min/max standard for read and write.

> Note that the MultiFab wrapper is maintained since it is persistent across load balancing, while the underlying MultiFabs are deleted and regenerated. I might need a recap why we...

Great, glad this could be solved. For action items we need to address for WarpX' PICMI implementation: 1. We should error out if defined PICMI parameters are silently ignored. 2....

Thanks, good points! 1. I think the `value` descriminator for a constant record component is sufficient, because `value` is a reserved attribute in the openPMD standard and using it without...

Maybe a bit duply with #1088

P.S.: Does (conditionally) using the new "large count" support in MPI4 help to remove that limit? Section 19.2+ of https://www.mpi-forum.org/docs/mpi-4.1/mpi41-report.pdf

Thanks, we'll check again with that! cc @titoiride We used BP4 temporarily because of a bug on our end, but we fixed that now (https://github.com/BLAST-WarpX/warpx/pull/5634).

Hi @leofang @kmaehashi @jakirkham @seberg, I am working on Python bindings for [AMReX](https://amrex-codes.github.io/amrex/) and a series of GPU science codes (e.g., the 2022 ACM Gordon Bell Prize code [WarpX](https://github.com/ECP-WarpX/WarpX)) and...

> I don't think this provides a solution. Since the openPMD plugin always passes coordinates to Paraview in SI units, rescaling gridSpacing and gridGlobalOffset and gridUnitSI will yield exactly the...