# Bug in v5.5.0-v5.5.2 reading multi-time pv\_%t.vtm data

**URL:** https://discourse.paraview.org/t/bug-in-v5-5-0-v5-5-2-reading-multi-time-pv-t-vtm-data/361
**Category:** In Situ Support
**Created:** [July 26, 2018, 2:00pm UTC](https://discourse.paraview.org/t/bug-in-v5-5-0-v5-5-2-reading-multi-time-pv-t-vtm-data/361 "2018-07-26T14:00:13Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![ka5855](https://discourse.paraview.org/user_avatar/discourse.paraview.org/ka5855/32/166_2.png) [@ka5855](https://discourse.paraview.org/u/ka5855)
#### Post date: [July 26, 2018, 2:00pm UTC](https://discourse.paraview.org/t/bug-in-v5-5-0-v5-5-2-reading-multi-time-pv-t-vtm-data/361/1 "2018-07-26T14:00:13Z")

</div>

In the recent versions, the multi-time reader fails to read all of the times on datafiles pv\_%t.vtm, written with the ParaView XMLMultiBlockDataWriter. (Which pv\_%t.vtm files are missing are repeatable for a fixed dataset, but vary with differing number of times and size of the datafiles.)

The multi-time reader successfully reads all of the times for datafile pv\_%.vth written with the ParaView XMLHierarchicalBoxDataWriter.

In all previous versions going back to v3.98.1 these multi-time file types were both read in correctly. The bug appears to be present in the standard linux binaries at the ParaView download site, as well as in all of our local superbuilds.

Would it be possible to fix the bug prior to the v5.6.0 release?

---

<div class="post-metadata">

### Author: ![patchett2002](https://discourse.paraview.org/user_avatar/discourse.paraview.org/patchett2002/32/235_2.png) [@patchett2002](https://discourse.paraview.org/u/patchett2002)
#### Post date: [August 15, 2018, 7:58pm UTC](https://discourse.paraview.org/t/bug-in-v5-5-0-v5-5-2-reading-multi-time-pv-t-vtm-data/361/2 "2018-08-15T19:58:51Z")

</div>

Bucky, please write this up as an issue at [gitlab.kitware.com](http://gitlab.kitware.com) and tag me @patchett2002  
thanks,–John. Ethan Stam can help get this written up as well.

---

<div class="post-metadata">

### Author: ![ka5855](https://discourse.paraview.org/user_avatar/discourse.paraview.org/ka5855/32/166_2.png) [@ka5855](https://discourse.paraview.org/u/ka5855)
#### Post date: [June 12, 2020, 12:02pm UTC](https://discourse.paraview.org/t/bug-in-v5-5-0-v5-5-2-reading-multi-time-pv-t-vtm-data/361/3 "2020-06-12T12:02:49Z")

</div>

John: In our recent debugging work we have discovered some clues on why this reader failure occurs with “Group” (multi-time) filesets: There exists an extra block in the XML file headers involving . . . . This extra block appears after version 5.4.1. By removing this block, the readers after v5.4.1 seem to work just fine.

And I can’t recall if the issue got addressed at [gitlab.kitware.com](http://gitlab.kitware.com), or not. But it is still an issue.

---

<div class="post-metadata">

### Author: ![ka5855](https://discourse.paraview.org/user_avatar/discourse.paraview.org/ka5855/32/166_2.png) [@ka5855](https://discourse.paraview.org/u/ka5855)
#### Post date: [June 12, 2020, 12:21pm UTC](https://discourse.paraview.org/t/bug-in-v5-5-0-v5-5-2-reading-multi-time-pv-t-vtm-data/361/4 "2020-06-12T12:21:17Z")

</div>

The extraneous XML header lines did not appear in the previous msg. They are here:  
“\<“FieldData”\>” . . . " \<"/FieldData"\>"

This file has an example with the faulty headers, as written in v5.6.2,  
[WithFieldData.tar.gz](https://discourse.paraview.org/uploads/short-url/pmMinQIM1C47LIkzoysMuTKxg6j.gz) (2.5 MB)  
and this file has the headers repaired by hand editing  
[NoFieldData.tar.gz](https://discourse.paraview.org/uploads/short-url/c6Jx2WZdBdMSlysCns5fopkwZwC.gz) (2.6 MB)  
so the you can observe the difference in the behavior in all versions 5.5.0 and greater.

(Oddly, version 5.4.1 will read the faulty files correctly.)
