MantisBT - ParaView
View Issue Details
0007323ParaViewBugpublic2008-07-09 16:342009-09-09 21:47
Chris Cameron 
Utkarsh Ayachit 
highmajoralways
closedfixed 
 
3.6.23.6.2 
0007323: First Cell Property (Data Array) Not Accessible By Filters Until Choosing Another Property First
Steps to reproduce the problem:

1) Create a Box
2) Apply the Box
3) Create a Calculator on Box
4) Create a Cell property (I used 4*5 as my calculation test)
5) Apply the Calculator
6) Create any filter (I'll use Threshold for a good example) on the Calculator that needs to use the Cell property
7) The Threshold filter thinks that the data range for the property is 0 to 0, and both sliders are locked against the left
8) Click Apply, you will get nothing (since a range of 0 to 0 gives nothing)
This problem can be avoided in the case of threshold only if there are other properties. You can pick one of the other properties in the drop down, then re-pick the first cell property; its range will now be correct.

However, you won't always have another cell property to flip around with, and in those cases your filter in #6 will fail when clicking apply. We have tested this with other filters than Calculator and Threshold and get the error message:

ERROR: In ..\..\..\VTK\Filtering\vtkAlgorithm.cxx, line 306
vtkMapAttributesFromGrid (0D42F4A8): Attempt to get an input array for an index that has not been specified

Notes:
Tested on Windows XP 32-bit with development paraview. Single-process mode.
No tags attached.
related to 0010128closed Utkarsh Ayachit Threshold filter shows point data as cell data 
Issue History
2008-07-09 16:34Chris CameronNew Issue
2008-07-14 10:59Chris CameronNote Added: 0012696
2008-07-22 22:05Alan ScottNote Added: 0012802
2008-07-22 22:05Alan ScottPrioritynormal => high
2008-07-25 12:27Alan ScottStatusbacklog => tabled
2008-07-25 12:27Alan ScottAssigned To => Utkarsh Ayachit
2009-02-18 09:30Utkarsh AyachitCategoryDevelopment => 3.6
2009-05-13 13:46Utkarsh AyachitTarget Version => 3.6
2009-08-25 11:53Ken MorelandCategory => Bug
2009-08-25 11:53Ken MorelandTarget Version3.6 => 3.6.2
2009-09-01 11:26Utkarsh AyachitNote Added: 0017276
2009-09-01 12:58Utkarsh AyachitNote Added: 0017279
2009-09-01 12:58Utkarsh AyachitStatustabled => @80@
2009-09-01 12:58Utkarsh AyachitFixed in Version => 3.6.2
2009-09-01 12:58Utkarsh AyachitResolutionopen => fixed
2009-09-09 21:47Alan ScottNote Added: 0017363
2009-09-09 21:47Alan ScottStatus@80@ => closed
2010-01-20 11:37Utkarsh AyachitRelationship addedrelated to 0010128

Notes
(0012696)
Chris Cameron   
2008-07-14 10:59   
the second sentence in Additional Information above should read:

"...and in those cases your filter in Step 6 above will fail when clicking apply."

instead of
"...and in those cases your filter in 0000006 will fail when clicking apply"
(0012802)
Alan Scott   
2008-07-22 22:05   
I am changing this to high priority, since 1) it severely impacts the reporter and 2) it can potentially cause misleading results. Should be fixed for 3.4, not a show stopper.
(0017276)
Utkarsh Ayachit   
2009-09-01 11:26   
When the input data didn't have point data, while the
input domain indeed allowed any attribute type, the vtkSMArrayListDomain still
would end up ignoring the arrays since the attribute type would get set to
point-data by default. Fixed that.


/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMArrayListDomain.cxx,v <-- Servers/ServerManager/vtkSMArrayListDomain.cxx
new revision: 1.22; previous revision: 1.21

Pending 3.6 commit.
(0017279)
Utkarsh Ayachit   
2009-09-01 12:58   
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMArrayListDomain.cxx,v <-- Servers/ServerManager/vtkSMArrayListDomain.cxx
new revision: 1.21.2.1; previous revision: 1.21
(0017363)
Alan Scott   
2009-09-09 21:47   
Tested client/remote server.