MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013248ParaView(No Category)public2012-06-18 08:272016-08-12 09:59
ReporterPhilippe Pébay 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target Versiongit-nextFixed in Version 
ProjectTBD
Topic Name
Typeusability
Summary0013248: Default behaviour for volume rendering between image and unstructured data
DescriptionPV does not support client-side volume rendering.

As a result, when running on parallel, the behaviour of volume rendering is not consistent between image and unstructured data: if the data set is small enough not make the server-side threshold, then the client only renders the outline.

From a user's perspective this is bad for at least 2 reasons:
1. The inconsistency between image and unstructured data cannot be easily figure out, and is counter-intuitive, as one would expect that the easiest case (regular grid) is handled when the hard one is not--but the opposite occurs.
2. The way to fix this behaviour requires relatively advanced knowledge of PV, and is a bad fix because it forces server-side rendering even for small data sets when this is not warranted.

Therefore I suggest that client-side VR be either never, or always (i.e., for both image and unstructured data) permitted.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-06-18 08:27Philippe PébayNew Issue
2012-06-18 09:07Philippe PébayTypeincorrect functionality => usability
2012-06-18 09:07Philippe PébayReproducibilityhave not tried => always
2012-06-18 09:07Philippe PébayTarget Version => git-next
2016-08-12 09:59Kitware RobotNote Added: 0038229
2016-08-12 09:59Kitware RobotStatusbacklog => closed
2016-08-12 09:59Kitware RobotResolutionopen => moved
2016-08-12 09:59Kitware RobotAssigned To => Kitware Robot

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