MantisBT - VTK
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0007305VTK(No Category)public2008-07-08 10:252016-08-12 09:55
ReporterBerk Geveci 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Project
Type
Summary0007305: XML reader producing wrong output
DescriptionWhen the attached file is loaded, the XML reader produces wrong output. It looks like the parser has some issues parsing ASCII data. If all arrays are enabled, the reader fails with an error. If all arrays are disabled, the file loads but the output is wrong. Although the number of points is 503 in the file, the output has 581 points. Although the number of cells is 2592 in the file, the output has 2880 cells.
The original message from the user (ufnoise .at. gmail .dot. com) that reported it is as follows:

I am writing an ascii xml file for an unstructured mesh. I have
scalar and vector data on lines. If I have any vector data listed
before scalar data, I get a crash upon hitting the apply button in
paraview:
ERROR: In /home/berk/Work/ReleaseBuilds/ParaView3/VTK/IO/vtkXMLDataReader.cxx,
line 532
vtkXMLUnstructuredGridReader (0x8aeed88): Cannot read cell data array
"ElectricField" from PointData in piece 1. The data array in the
element may be too short.

This is how I am declaring data to be vector data.
<DataArray Name="ElectricField" type="Float64" NumberOfComponents="3"
format="ascii">

However, if I ensure that the vector data are listed after the scalar
data in the cell data section, everything is cool.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-07-08 10:25Berk GeveciNew Issue
2011-06-16 13:11Zack GalbreathCategory => (No Category)
2016-08-12 09:55Kitware RobotNote Added: 0036998
2016-08-12 09:55Kitware RobotStatusexpired => closed
2016-08-12 09:55Kitware RobotResolutionopen => moved
2016-08-12 09:55Kitware RobotAssigned To => Kitware Robot

Notes
(0036998)
Kitware Robot   
2016-08-12 09:55   
Resolving issue as `moved`.

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