# data out of range using pvtr file

**URL:** https://discourse.paraview.org/t/data-out-of-range-using-pvtr-file/7489
**Category:** ParaView Support
**Created:** [June 25, 2021, 3:09pm UTC](https://discourse.paraview.org/t/data-out-of-range-using-pvtr-file/7489 "2021-06-25T15:09:12Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![yannf](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/y/f17d59/32.png) [@yannf](https://discourse.paraview.org/u/yannf)
#### Post date: [June 25, 2021, 3:09pm UTC](https://discourse.paraview.org/t/data-out-of-range-using-pvtr-file/7489/1 "2021-06-25T15:09:12Z")

</div>

Hi,

I have some problem with the latest versions of Paraview (from 5.8 at least) . When I load data from a pvtr file, data are out of range (-1E+38 , 1E+38). All is right when I directly load data from vtr files (files present in the pvtr file, which are in binary format).  
The problem occurs with different OS (MacOS, Linux).  
**Loading data from my .pvtr file works well with an oldest version of Paraview (5.0.1 64).**  
Please, could you help me to understand and solve this problem ?  
Thank you for your help.

You find here the pvtr file I used. Every data features (the data type, the byte order) are identical to these defined in the .vtr files.

```auto
<?xml version='1.0' encoding='utf-8'?>
<VTKFile type="PRectilinearGrid" version="1.0" byte_order="LittleEndian" header_type="UInt32">
  <PRectilinearGrid WholeExtent="0 513 0 257 0 0 " GhostLevel="0">
    <PPointData>
      <PDataArray type="Float32" Name="Velocity" NumberOfComponents="2" format="binary"/>
      <PDataArray type="Float32" Name="T" NumberOfComponents="1" format="binary"/>
    </PPointData>
    <PCoordinates>
      <PDataArray type="Float32" Name="X" NumberOfComponents="1" format="binary"/>
      <PDataArray type="Float32" Name="Y" NumberOfComponents="1" format="binary"/>
      <PDataArray type="Float32" Name="Z" NumberOfComponents="1" format="binary"/>
    </PCoordinates>
    <Piece Extent="0 257 0 129 0 0 " Source="res_00000_0000149.vtr"/>
    <Piece Extent="0 257 128 257 0 0 " Source="res_00001_0000149.vtr"/>
    <Piece Extent="256 513 0 129 0 0 " Source="res_00002_0000149.vtr"/>
    <Piece Extent="256 513 128 257 0 0 " Source="res_00003_0000149.vtr"/>
  </PRectilinearGrid>
</VTKFile>

```

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 25, 2021, 3:19pm UTC](https://discourse.paraview.org/t/data-out-of-range-using-pvtr-file/7489/2 "2021-06-25T15:19:20Z")

</div>

please share the complete data, not only the .pvtr file.

---

<div class="post-metadata">

### Author: ![yannf](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/y/f17d59/32.png) [@yannf](https://discourse.paraview.org/u/yannf)
#### Post date: [June 25, 2021, 4:40pm UTC](https://discourse.paraview.org/t/data-out-of-range-using-pvtr-file/7489/3 "2021-06-25T16:40:28Z")

</div>

You find [here](https://transfert.u-psud.fr/5hpz) the archive test\_pvtr.tar, which contains the paraview files (.vtr + .pvtr) and a png file showing a field view of the data set (created from the version 5.0.1 64).  
Thank you for your help.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 28, 2021, 8:26am UTC](https://discourse.paraview.org/t/data-out-of-range-using-pvtr-file/7489/4 "2021-06-28T08:26:42Z")

</div>

I reproduce but your pvtr file seems fine. Deeper investigation would be necessary to understand what is going on.

---

<div class="post-metadata">

### Author: ![yannf](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/y/f17d59/32.png) [@yannf](https://discourse.paraview.org/u/yannf)
#### Post date: [June 28, 2021, 9:34am UTC](https://discourse.paraview.org/t/data-out-of-range-using-pvtr-file/7489/5 "2021-06-28T09:34:07Z")

</div>

OK, I think so. Thank you for your help.

---

<div class="post-metadata">

### Author: ![yannf](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/y/f17d59/32.png) [@yannf](https://discourse.paraview.org/u/yannf)
#### Post date: [September 2, 2021, 1:55pm UTC](https://discourse.paraview.org/t/data-out-of-range-using-pvtr-file/7489/6 "2021-09-02T13:55:39Z")

</div>

Hi,

Have you got some news about the issue ?

Thanks

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [September 2, 2021, 1:57pm UTC](https://discourse.paraview.org/t/data-out-of-range-using-pvtr-file/7489/7 "2021-09-02T13:57:03Z")

</div>

First step would be to open an issue here:

[https://gitlab.kitware.com/paraview/paraview/-/issues](https://gitlab.kitware.com/paraview/paraview/-/issues)

If it is critical for you that this issue is fixed, you may want to consider contacting Kitware for support:  
More info here:

> [@How are features and bug fixes incorporated into ParaView?](https://discourse.paraview.org/t/how-are-features-and-bug-fixes-incorporated-into-paraview/4735):
>
> As with all open source projects, adding features and fixing bugs takes developer effort. That effort may originate from volunteer community contributors, or through paid professional services offered by companies like [Kitware](https://www.kitware.com). Features and bug fixes are prioritized by the needs of contributing community members and by professional services customers. Note that contributions are vetted by a rigorous community review and testing process; therefore it is recommended that significant changes are d…