View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0013769 | ParaView | (No Category) | public | 2013-01-05 19:33 | 2013-01-30 10:40 | ||||
Reporter | Russ Taylor | ||||||||
Assigned To | Andy Bauer | ||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | 3.98.0 | ||||||||
Target Version | Fixed in Version | 3.98.1 | |||||||
Summary | 0013769: Contour filter "Compute scalars" misbehaves | ||||||||
Description | After loading a data file with more than one data set in it (for example, the VTK file stored in http://www.cs.unc.edu/~taylorr/temp/Mcneil_CNTs.zip [^]), application of the contour filter does not allow me to click the "Compute Scalars" checkbox (it is grayed out). If I compute a range of values (Delete All/New Range) and Contour by "Result1", it does not carry Result1 into the output. Therefore, I cannot color the contours by the value I used to generate them. Workaround shows another problem: If I use the Calculator on the original data set and make a Result1copy data set from Result1 and then Contour the output of the calculator by Result1, then it carries through Result1 and Result2 but not Result1copy. I would have expected it to keep Result2 and Result1copy. If I contour by Result1copy, it still carries through Result1 and Result2. I'll add the workaround into my homework description for the class this semester, but it would be good if the checkbox was not grayed out so we could select the behavior that we usually want from this filter. It used to work in an older version. | ||||||||
Tags | No tags attached. | ||||||||
Project | Kitware | ||||||||
Topic Name | 13769_contour_polydata_scalars | ||||||||
Type | incorrect functionality | ||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0029994) Andy Bauer (developer) 2013-01-07 12:37 |
This fixes the issue of enabling the option to compute scalars. It does NOT fix the issue that with Compute Scalars unchecked that the arrays that are passed are independent of the array that is chosen to contour by. Although not intuitive from the GUI perspective, the behavior is proper in VTK in that SetInputArrayToProcess() is used to specify which array to use to contour while vtkDataSetAttributes separately allows a different array to be set as the active scalars which is used to determine which array to not pass through the filter. |
(0030113) Utkarsh Ayachit (administrator) 2013-01-11 14:43 |
merged into master, where applicable. |
(0030159) Alan Scott (manager) 2013-01-16 22:03 |
Linux, master, local server. I confirmed that the first error has been fixed. Behavior is as stated as correct by Andy for the second issue. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2013-01-05 19:33 | Russ Taylor | New Issue | |
2013-01-06 11:48 | Andy Bauer | Assigned To | => Andy Bauer |
2013-01-06 11:49 | Andy Bauer | Status | backlog => todo |
2013-01-06 14:49 | Andy Bauer | Status | todo => active development |
2013-01-07 12:37 | Andy Bauer | Topic Name | => 13769_contour_polydata_scalars |
2013-01-07 12:37 | Andy Bauer | Note Added: 0029994 | |
2013-01-07 12:37 | Andy Bauer | Status | active development => gatekeeper review |
2013-01-07 12:37 | Andy Bauer | Fixed in Version | => git-next |
2013-01-07 12:37 | Andy Bauer | Resolution | open => fixed |
2013-01-11 14:42 | Utkarsh Ayachit | Fixed in Version | git-next => git-master |
2013-01-11 14:43 | Utkarsh Ayachit | Status | gatekeeper review => customer review |
2013-01-11 14:43 | Utkarsh Ayachit | Note Added: 0030113 | |
2013-01-16 22:03 | Alan Scott | Note Added: 0030159 | |
2013-01-16 22:03 | Alan Scott | Status | customer review => closed |
2013-01-30 10:40 | Utkarsh Ayachit | Fixed in Version | git-master => 3.98.1 |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |