MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012185ParaViewBugpublic2011-05-11 18:292013-02-12 20:29
ReporterKen Moreland 
Assigned ToUtkarsh Ayachit 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionno change required 
PlatformOSOS Version
Product Version 
Target Version3.98.1Fixed in Version3.98.1 
ProjectSandia
Topic Name
Typeincorrect functionality
Summary0012185: Unnecessary collection when rendering bounding box LOD
DescriptionWhen in client/server mode, there is a special LOD that renders a bounding box on the client rather than rendering real geometry. The intention is that regardless of latencies, bandwidths, and data size you should be able to render this bounding box with no problem.

However, I have noticed that the first time you do an interactive render with the bounding box, there is still an odd pause. To replicate, do the following.

1. Start ParaView client/server (or multi-core mode).
2. Check settings Render View -> Server -> Client Outline Threshold is on and about 100 MBytes (the default).
3. Create a Wavelet source, whole extent [-100,100] along each axis (yeah, big). Apply.
4. Add contour. Delete default isosurface value, click New Range, Click OK for defaults, Apply. The resulting surface is about 110 MB.
5. Drag in the 3D view to render. You will notice a pause before the bounding box is rendered at a new camera angle.

If you monitor the Timer Log carefully, you will notice that during the interactive render there is some gathering of information that occurs. There is no reason to collect any information when rendering the bounding box.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-05-11 18:29Ken MorelandNew Issue
2011-06-19 18:44Utkarsh AyachitAssigned To => Utkarsh Ayachit
2011-06-19 18:44Utkarsh AyachitStatusbacklog => todo
2011-06-22 15:34Utkarsh AyachitStatustodo => backlog
2013-01-08 21:29Alan ScottProject => Sandia
2013-01-08 21:29Alan ScottType => incorrect functionality
2013-01-24 22:39Utkarsh AyachitTarget Version => 3.98.1
2013-01-24 22:39Utkarsh AyachitSticky IssueNo => Yes
2013-01-28 10:52Utkarsh AyachitNote Added: 0030266
2013-01-28 10:52Utkarsh AyachitStatusbacklog => gatekeeper review
2013-01-28 10:52Utkarsh AyachitResolutionopen => no change required
2013-01-28 10:59Utkarsh AyachitStatusgatekeeper review => customer review
2013-01-28 10:59Utkarsh AyachitFixed in Version => git-master
2013-01-30 10:40Utkarsh AyachitFixed in Versiongit-master => 3.98.1
2013-02-12 20:29Alan ScottNote Added: 0030334
2013-02-12 20:29Alan ScottStatuscustomer review => closed

Notes
(0030266)
Utkarsh Ayachit   
2013-01-28 10:52   
This seems to be have been fixed. I no longer see any pause when I start interacting. Looking at the timer log, the first "Interactive Render" takes (with a debug build):

- 0.003s for updating representations. (LOD Geometry filter executes and generated outline).
- 0.02s for delivery (outlines are delivered to client)
- 0.008s for rendering (the actual rendering on the client side).

Which sounds reasonable.

Alan, note that the "Settings" dialog has under go some changes since when Ken reported this bug. "Client Outline Threshold" option has now been removed and is replaced by a check box on the "Render View | General" page saying "Use outline for LOD rendering".
(0030334)
Alan Scott   
2013-02-12 20:29   
Thanks for the note on "Use outline for LOD rendering". I hadn't seen that.

Seems to be very, very fast for me. Tested 8 remote servers, Linux, 3.98.1.