Open ax3l opened 3 years ago
The id provider can be de-selected in the GUI in paraview at read-time, so it's not blocking the usage.
Long-term solution for this is going to be the introduction of custom (non-standard) groups in the openPMD hierarchy similar to custom attributes. That's going to require some redesign in our frontend, but it's an issue that has come up several times now. Until then, deselecting the "mesh" in Paraview is a good workaround.
PIConGPU at the moment "mis-uses" fields to store the RNG metrix generator states via
picongpu_idProvider
for checkpoints.We could try to handle this more graceful (ignore) in the ParaView (5.9) plugin. https://gitlab.kitware.com/paraview/paraview/-/blob/v5.9.0/Wrapping/Python/paraview/algorithms/openpmd.py
Example data set: https://github.com/openPMD/openPMD-example-datasets/pull/14