MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014414ParaView(No Category)public2013-11-18 23:372016-08-12 09:59
ReporterBen Colcord 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version4.0 
Target VersionFixed in Version 
ProjectTBD
Topic Name
Typeincorrect functionality
Summary0014414: Save data from stream trace gives errors in parallel
DescriptionI have a script that creates a streamline and saves the data to file. When run with pvbatch it produces correct results in serial but gives errors in parallel.
Output is still produced in parallel but the data is nonsensical. The errors output are:

ERROR: In /nv/hp25/bcolcord3/ParaView/VTK/Common/Core/vtkDataArray.cxx, line 474
vtkDoubleArray (0xd4058a00): The number of components do not match the number requested: 3 != 1

Warning: In /nv/hp25/bcolcord3/ParaView/VTK/Common/DataModel/vtkTable.cxx, line 421
vtkTable (0xd4634a60): Cannot assign this variant type to multi-component data array.

The same errors occur when run from python shell in the GUI, again only in parallel.

I am using Paraview 4.01, commit 98db6239f0a9d1b97a. My data is read in as a Multi-block Dataset and I apply the following filters:

CellDatatoPointData
ProgrammableFilter (removes ghost layers from blocks)
Calculator (to create velocity vector from scalars for stream trace)
StreamTracer (only one streamline)

When I try to save the data is when I get those errors, and again, only when run in parallel.

Thanks.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2013-11-18 23:37Ben ColcordNew Issue
2016-08-12 09:59Kitware RobotNote Added: 0038468
2016-08-12 09:59Kitware RobotStatusbacklog => closed
2016-08-12 09:59Kitware RobotResolutionopen => moved
2016-08-12 09:59Kitware RobotAssigned To => Kitware Robot

Notes
(0038468)
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.