GEOS-DEV / GEOS-DEV/GEOS

VTK output .pvd file is missing time states for restart runs

Open
#1,775 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: bug
Dominant language
C++
Stars
287
Forks
109
Avg merge
4d 41m
Merged PRs (30d)
5

Description

Describe the bug
During jobs that are resuming from restart, the vtk .pvd file only includes time states for the current job (obviously, they should all be included). For example, note the missing timesteps before 978 s:

<?xml version="1.0"?>
<VTKFile type="Collection" version="0.1">
	<Collection>
		<DataSet timestep="978.32278442382812" file="vtkOutput/000049.vtm" />
		<DataSet timestep="1038.3227844238281" file="vtkOutput/000051.vtm" />
		<DataSet timestep="1098.3227844238281" file="vtkOutput/000053.vtm" />
		<DataSet timestep="1158.3227844238281" file="vtkOutput/000055.vtm" />
		<DataSet timestep="1218.3227844238281" file="vtkOutput/000057.vtm" />
		<DataSet timestep="1278.3227844238281" file="vtkOutput/000059.vtm" />
		<DataSet timestep="1338.3227844238281" file="vtkOutput/000061.vtm" />
	</Collection>
</VTKFile>

To Reproduce
For any run that outputs vtk format files, resume from a restart file.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with a run that outputs VTK files, then resume that run from a restart file and inspect the generated .pvd XML. The work is done when the collection includes the time states from before the restart as well as those from the resumed job.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
hpc
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.