Snapshot output from a restarted run produces a valid BP5 file containing all field variables, but without the vtk.xml attribute. ParaView's VTX reader then fails to open it. Fresh runs of the same case write the attribute correctly.
Suggested fix: define the vtk.xml attribute unconditionally at IO setup, independent of the restart flag. Since it's derived from grid dimensions and mesh spacing, both known at initialisation in either case, there should be no ordering constraint.
Workaround: writing the schema by hand into the .bp directory as a vtk.xml file restores loading - the reader checks for the file as well as the attribute
Snapshot output from a restarted run produces a valid BP5 file containing all field variables, but without the vtk.xml attribute. ParaView's VTX reader then fails to open it. Fresh runs of the same case write the attribute correctly.
Suggested fix: define the vtk.xml attribute unconditionally at IO setup, independent of the restart flag. Since it's derived from grid dimensions and mesh spacing, both known at initialisation in either case, there should be no ordering constraint.
Workaround: writing the schema by hand into the .bp directory as a vtk.xml file restores loading - the reader checks for the file as well as the attribute