MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0015925ParaView(No Category)public2016-01-11 11:472016-08-12 09:59
ReporterDan Ibanez 
Assigned ToKitware Robot 
PriorityhighSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version5.0 
Target VersionFixed in Version 
ProjectTBD
Topic Name
Typecrash
Summary0015925: can't parse valid Float64 ASCII values
DescriptionUsing Paraview 5.0.0-RC3 binary distribution for Mac,
but also reproduced on Linux with older Paraview versions.
The VTK UnstructuredGrid XML Parser fails to read ASCII DataArrays containing values like this:

-8.89836e-313

Even when we explicitly state type="Float64". The current workaround is to cast our "double" values to "float" before output. A stand-alone C++ program using "std::cin >> float" accepts these values just fine. Actually, this may have more to do with that value being a sub-normal double precision value. I've confirmed that Paraview accepts the file if the values are changed to this:

-8.89836e-300

Which is just above the sub-normal cutoff.

An example UnstructuredGrid file is attached.
Steps To ReproduceOpen the attached file with Paraview.
Additional Information
TagsNo tags attached.
Relationships
Attached Files? bug.vtu (1,037) 2016-01-11 11:47
https://www.vtk.org/Bug/file/9993/bug.vtu
Issue History
Date ModifiedUsernameFieldChange
2016-01-11 11:47Dan IbanezNew Issue
2016-01-11 11:47Dan IbanezFile Added: bug.vtu
2016-01-11 11:59Dan IbanezDescription Updatedbug_revision_view_page.php?rev_id=1452#r1452
2016-01-11 11:59Dan IbanezSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=1454#r1454
2016-08-12 09:59Kitware RobotNote Added: 0038969
2016-08-12 09:59Kitware RobotStatusbacklog => closed
2016-08-12 09:59Kitware RobotResolutionopen => moved
2016-08-12 09:59Kitware RobotAssigned To => Kitware Robot

Notes
(0038969)
Kitware Robot   
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.