MantisBT - ParaView
View Issue Details
0010601ParaViewBugpublic2010-04-23 09:142016-08-12 09:58
Eric Monson 
Marcus D. Hanwell 
normalminoralways
closedmoved 
Development 
 
0010601: Charts: Parallel Coords Global IDs selection problem
I was playing with the parallel coordinates chart in ParaView and came across a strange problem: Selections work fine if I'm doing it by ID (set in Selection Inspector panel Selection Type), but if I have the Selection Type set to Global Node IDs the list of Global IDs is twice as long as it should be, and alternates -1 values with the correct IDs.
Here's the pipeline to reproduce with built-in functions (2010-04-09 CVS PV):

Point Source (I did 100 pts, 10 rad)
Generate Ids
Elevation
Programmable filter:
from paraview.vtk import vtkAssignAttribute
pdi = self.GetInputDataObject(0,0)
pdo = self.GetOutputDataObject(0)
aa = vtkAssignAttribute()
aa.SetInput(pdi)
# aa.Assign()
# Second arg: 5=GlobalIds, 6=PedigreeIds
# Third arg: 0=Point, 1=Cell data
aa.Assign('Ids',5,0)
aa.Update()
pdo.ShallowCopy(aa.GetOutputDataObject(0))
PlotData

Make a selection in the PC chart with the Selection Inspector visible. The SI Selection Type will show IDs. Switch this to Global Node IDs, and the list will still look fine. Then, make a different selection in the PC chart with Global Node IDs still as the Type. I get lists like this:

-1
5
-1
72
-1
73
-1
81
-1
83

where the values that aren't -1 are correct. If you switch Type back to IDs, then back to Global IDs without changing the selection it looks fine again, until you make a new selection with Global IDs set as the Type.
No tags attached.
Issue History
2010-04-23 09:14Eric MonsonNew Issue
2010-04-23 09:36Marcus D. HanwellStatusbacklog => tabled
2010-04-23 09:36Marcus D. HanwellAssigned To => Marcus D. Hanwell
2016-08-12 09:58Kitware RobotNote Added: 0037813
2016-08-12 09:58Kitware RobotStatusexpired => closed
2016-08-12 09:58Kitware RobotResolutionopen => moved

Notes
(0037813)
Kitware Robot   
2016-08-12 09:58   
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.