Closed ax3l closed 3 months ago
ah, actually the exception has the name:
Further description: [HDF5] Unsupported simple attribute type 216172782113784119 for position.
Error recovery is currently not yet as fine-grained as it would ideally be, the currently-released version is the first approach of openPMD-api at error recovery after all. We are currently planning to refactor (to a large part rewrite) the handling of scientific default values such as the position. Currently, there is basically explicit logic for each single attribute that has a definition in the openPMD standard, which is not really ideal nor is it flexible. This issue is linked to https://github.com/openPMD/openPMD-api/issues/1439 since a rewrite should consider this point. Ref. the issue description:
- Reading defaults would happen at the same time as now (during parsing). It would deal leniently with missing / wrong values, e.g. by just setting the default, or ignoring it.
The error message looks reasonable for now and points to the attribute named position
being wrong. Tracking in #1439 for the underlying issue.
With @RemiLehe today, we looked at a file that had an unsupported 128bit
long double
data type in the meshposition
attribute.We noticed that the exception when skipping the mesh during read was not pointing at the
position
attribute name yet, which we might be able to add.The exception traceback we got was
x-ref https://github.com/LASY-org/lasy/pull/179