| View Issue Details [ Jump to Notes ] | [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0006693 | ParaView | (No Category) | public | 2008-04-01 10:21 | 2009-05-13 13:59 |
|
| Reporter | Ken Moreland | |
| Assigned To | Berk Geveci | |
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | | |
| Target Version | 3.4 | Fixed in Version | 3.4 | |
|
| Summary | 0006693: Add result array name feature to gradient and gradient magnitude filters |
| Description | The gradient and gradient magnitude filters replace the input array with an array of the same name with the gradient vector or magnitude. This is problematic for two reasons. First, it is misleading; the name no longer reflects the nature of the data. Second, it makes working with the data. If I want to do any operation on both the scalar and its gradient I have to jump through a bunch of hoops to get both arrays because they are attached to different data objects with the same name.
The unstructured gradient filter has a much better way around this. It has a result array name parameter that will be used to name the output. This way, a user may add an appropriate name for the data. |
| Additional Information | The change should be made in a backward compatible way. The VTK filter should replicate the previous behavior if a result array name is not given. I guess the ParaView defaults should also have this backward compatible behavior so that saved states and scripts still work. |
| Tags | No tags attached. |
|
| Project | |
| Topic Name | |
| Type | |
|
| Attached Files | |
|