View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0011918ParaViewBugpublic2011-03-02 15:462012-04-12 20:57
ReporterGreg Weirs 
Assigned ToRobert Maynard 
PriorityhighSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product VersionDevelopment 
Target VersionFixed in Version3.12 
Summary0011918: Prism Filter does not accept point data as input
DescriptionThe prism filter expects cell data as pipeline input, but this should not be a requirement. A significant capability that relies on the input being cell data is linked selection - selection in the prism view is associated by GlobalElementID to the data in the other view(s).
Additional InformationGreg,

There are a two things that would need to be modified in Prism to handle both point and cell data seamlessly. Prism would need to be modified to handle point data at the lowest level. When I say point data I mean that the entities of interest are the points regardless of the cell type. A VTK point can be in multiple VTK cells. Handling point data is more straight forward than what is currently done for cells in Prism. However there are some questions about that would need to be worked out to help Prism know when to process the input as point data versus cell data.

The second thing that would need to be worked out is the linked selection. Prism uses the GlobalElementID to link selection. I believe there is a GlobalPointID that it could use with point data. So it may just be a matter of modifying the existing code to look for GlobalPointID as well as GlobalElementIDs.


I wish that we could have tackled use case sooner. It wouldn't have taken very long to make the necessary changes.


Corey.






On Mon, Feb 28, 2011 at 4:49 PM, Weirs, V Gregory <vgweirs@sandia.gov> wrote:
Hi Corey,
I think I understand the distinction between ParaView/VTK terminology and analysis terminology. The main point is that the analysis data may be point data or cell data; it just turns out that for exodus and spcth it is cell data. For many similar codes it is point data. Tracer data (hscth) is really point data. Prism should not care which it is, as long as the cells or points have the thermodynamic variables matching the SESAME data.

So the question is, what features of Prism rely on the simulation data being cell data? Is it more than linked selection?

Thanks,
Greg
TagsNo tags attached.
ProjectSandia
Topic Namemore-prism-support
Type
Attached Files

 Relationships

  Notes
(0027028)
Robert Maynard (developer)
2011-07-19 17:21

 Only support for reading point based properties have been completed. The selection issue with global point ids is in bug 0012380.
(0027051)
Utkarsh Ayachit (administrator)
2011-07-21 19:18

 Scheduled for gatekeeper review on Jul 22, 2011 at 2 pm EDT.
(0027066)
Utkarsh Ayachit (administrator)
2011-07-22 14:13

 Merged to git-master.
(0028472)
Alan Scott (manager)
2012-04-12 20:57

 Assuming fixed.

 Issue History
Date Modified Username Field Change
2011-03-02 15:46 Greg Weirs New Issue
2011-03-25 15:28 Robert Maynard Assigned To => Robert Maynard
2011-03-25 15:28 Robert Maynard Status backlog => tabled
2011-06-23 10:36 Robert Maynard Status backlog => todo
2011-06-23 10:36 Robert Maynard Status todo => active development
2011-06-23 15:26 Utkarsh Ayachit Project => Sandia
2011-07-19 17:21 Robert Maynard Topic Name => more-prism-support
2011-07-19 17:21 Robert Maynard Note Added: 0027028
2011-07-19 17:21 Robert Maynard Status active development => gatekeeper review
2011-07-19 17:21 Robert Maynard Resolution open => fixed
2011-07-21 19:18 Utkarsh Ayachit Note Added: 0027051
2011-07-22 14:13 Utkarsh Ayachit Status gatekeeper review => customer review
2011-07-22 14:13 Utkarsh Ayachit Note Added: 0027066
2011-07-29 16:18 Utkarsh Ayachit Fixed in Version => 3.12
2012-04-12 20:57 Alan Scott Note Added: 0028472
2012-04-12 20:57 Alan Scott Status customer review => closed

Copyright © 2000 - 2018 MantisBT Team