MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0003437ParaView(No Category)public2006-06-23 15:352016-08-12 09:57
ReporterKen Moreland 
Assigned ToBerk Geveci 
PrioritylowSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Project
Topic Name
Type
Summary0003437: SNL: D3 mishandles global ids not vtkIdType
DescriptionD3 always assumes that global ids are in a vtkIdTypeArray. If they are not, they are ignored by D3.

In some special cases, I think this is causing D3 to crash (that is, D3 is crashing and I think this is the cause). It happens when you have int global point ids and then have thresholded the data so that some processes have no data. If this is the case, D3 first does a quick distribution to make sure every process has some data (TestFixTooFewInputFiles method) and then a second distribution based on the kd-tree. During this second distribution, vtkPKdTree gets confused because some processes may be missing their global point id arrays and the number of arrays does not match up.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-12-09 14:51Berk GeveciProject@3@ => ParaView
2011-06-16 13:10Zack GalbreathCategory => (No Category)
2016-08-12 09:57Kitware RobotNote Added: 0037498
2016-08-12 09:57Kitware RobotStatusexpired => closed
2016-08-12 09:57Kitware RobotResolutionopen => moved

Notes
(0004363)
Ken Moreland   
2006-06-26 17:46   
I added a fix to vtkDistributedDataFilter that gets around the crash. Therefore I dropped both the priority and severity. This is now probably not a big enough issue to bother to resolve before ParaView 2.6.
(0037498)
Kitware Robot   
2016-08-12 09:57   
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.