When opening a .pvd file in ParaView 6.1.0, the PVD reader fails to parse timestep attribute values that are written in scientific notation with an explicit-sign exponent (e.g. 0.8006087E+01). For every timestep entry, it emits:
ERROR: In vtkPVDReader.cxx, line 175
vtkPVDReader (0x...): Could not parse timestep string: 0.8006087E+01 Setting time value to 0
As a result every timestep is set to 0, so the dataset loads with no usable time information.
The same .pvd file:
-
opens correctly in ParaView 6.0.0 with all timesteps parsed, and
-
the referenced
.vtufiles open without any problem in 6.1.0 (the issue is isolated to PVD timestep parsing, not the underlying data).VSLICE_0000.zip (21.3 KB)
I attach the attach the VSLICE_0000.zip to reproduce the issue.
Best,
E.