View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0014892ParaView(No Category)public2014-07-28 07:272016-08-12 09:59
ReporterVadim SANDLER 
Assigned ToTristan Coulange 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version4.1 
Target VersionFixed in Version 
Summary0014892: Different behavior between ASCII and BIN
DescriptionThe two associated Paraview files came from the same computation, performed using an application based on the VTK library. There is a difference only in the format: one is binary and the other one is ASCII. The animation is good with the binary file, but not good with the ASCII file:

1) Load file from the meppen4_proj_sb_asci.tgz archive
2) Color a presentation by the ECRO field
3) Start animation
   => Animation is played until the 41 step, after this step the following error message is displayed:

ERROR: In /dn20/salome/rnv/PRODUCTS_BUILD/PARAVIEW_DEV/ParaView-4.1.0_SRC/VTK/IO/XML/vtkXMLDataReader.cxx, line 484
vtkXMLUnstructuredGridReader (0x443bb60): Cannot read cell data array "ECRO" from PointData in piece 0. The data array in the element may be too short.

But seems this problem can be reproduced also in the ParaView-4.1 application, for that load the file from the meppen4_proj_sb_bin.tgz archive, export it in the VTK Unstructured Grid (VTU) format in the ASCII Data Mode, load obtained file in the ParaView and perform steps (1)-(3), the result is the same.

About a data to reproduce a problem: unfortunately files to reproduce the problem too big and I can’t attach files in the mantis. To obtain these files please send request to the bugmaster.salome@opencascade.com and I’ll send you link and password to the FTP server, or alternatively I can upload these files to the any provided server.
TagsNo tags attached.
ProjectParaViS
Topic Name
Typeincorrect functionality
Attached Files

 Relationships

  Notes
(0033149)
Tristan Coulange (developer)
2014-07-30 13:41

 Hello,

The problem comes from the binary file: it contains infinite values in the ECRO field, and ParaView does not support it. You can see that there are infinite values by looking at the ECRO ranges in ParaView (the step 43 for example, in the "Information" panel). As a consequence, the generated ascii file contains the word "Infinity" instead of regular values, and it is not supported by the ascii reader.

We enhanced the vtk ascii reader to support infinite values, so the ascii file will be read like the binary one, but other issues will remain like the one you mentionned in the issue 0014893 because ParaView does not support infinite values.
To support your ascii file a little better, we can read infinite values as "NaN" instead of "Infinity" so that ParaView will ignore them sometimes. What do you think about this?

Tristan
(0038608)
Kitware Robot (administrator)
2016-08-12 09:59

 Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.

 Issue History
Date Modified Username Field Change
2014-07-28 07:27 Vadim SANDLER New Issue
2014-07-28 07:27 Vadim SANDLER Assigned To => Tristan Coulange
2014-07-30 13:41 Tristan Coulange Note Added: 0033149
2016-08-12 09:59 Kitware Robot Note Added: 0038608
2016-08-12 09:59 Kitware Robot Status backlog => closed
2016-08-12 09:59 Kitware Robot Resolution open => moved

Copyright © 2000 - 2018 MantisBT Team