View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004683ParaView(No Category)public2007-03-27 09:242007-04-10 13:21
ReporterDavid Karelitz 
Assigned ToUtkarsh Ayachit 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0004683: Default Composite Threshold ignored
DescriptionThe default composite threshold at startup was 3MB, gemeotry was 41MB, yet compositing was not turned on until I moved the compositing slider
TagsNo tags attached.
Project
Topic Name
Type
Attached Files

 Relationships

  Notes
(0006953)
Utkarsh Ayachit (administrator)
2007-03-27 12:06

 Could not reproduce this. Works just fine for me. Can you upload your settings file?

~/.config/Kitware/ParaView3.0.ini (on linux).
C:\Documents and Settings\<User Name>\Application Data\Kitware\ParaView3.0.ini (on Windows)
(0006976)
David Karelitz (reporter)
2007-03-28 15:50

 I'm running on 20 servers. I think the problem is it's looking at the size of geometry on a single server and not all servers when doing the comparison to the value in the UI.

i.e. the compositing slider in the UI is set to 3.6 MB, geometry is 41 MB total on 20 servers. It doesn't do compositing.

Actually I can't get compositing to turn on with any value other than 0 on the composite slider.
(0006996)
Utkarsh Ayachit (administrator)
2007-03-29 11:19

 UpdateVTKObjects() was called on the renderer before the server side object was created. Hence the default properties were pushed only to the client side renderer. Consequently, AutomaticLightCreation was disabled only on the client. Fixed that.
(0006997)
Utkarsh Ayachit (administrator)
2007-03-29 11:20

 Oops, closed the wrong bug. Ignore my previous comment.
(0006999)
Utkarsh Ayachit (administrator)
2007-03-29 11:33

 I still can't reproduce this bug. I tried server with 20 nodes. What type of data are you loading?
Can you verify that the data information tab is reporting the "Memory" size correctly.
(0007000)
David Karelitz (reporter)
2007-03-29 11:37

 I'm loading a 64 file exodus dataset, information tab says 29 MB of geometry (and so does the statistics view. The data has about 250k cells and points so that seems about right). I set the composite slider to 3.6 MB and it sends the geometry to my client. Shouldn't the slider have to be set to greater than 29MB before it moved the data? The only way to get it to do compositing is to set the slider to 0 MB
(0007001)
David Karelitz (reporter)
2007-03-29 11:39

 I'm running the client and servers on linux boxes if that helps
(0007015)
Utkarsh Ayachit (administrator)
2007-03-29 15:47

 The collection decision was made before the pipeline was updated consequently using obsolete data information. Fixed that.



/cvsroot/ParaView3/ParaView3/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx,v <-- vtkStreamingDemandDrivenPipeline.cxx
new revision: 1.52; previous revision: 1.51
/cvsroot/ParaView3/ParaView3/VTK/Filtering/vtkStreamingDemandDrivenPipeline.h,v <-- vtkStreamingDemandDrivenPipeline.h
new revision: 1.26; previous revision: 1.25
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMClientServerRenderModuleProxy.cxx,v <-- vtkSMClientServerRenderModuleProxy.cxx
new revision: 1.2; previous revision: 1.1
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMClientServerRenderModuleProxy.h,v <-- vtkSMClientServerRenderModuleProxy.h
new revision: 1.2; previous revision: 1.1
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMDataObjectDisplayProxy.cxx,v <-- vtkSMDataObjectDisplayProxy.cxx
new revision: 1.36; previous revision: 1.35
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMDataObjectDisplayProxy.h,v <-- vtkSMDataObjectDisplayProxy.h
new revision: 1.25; previous revision: 1.24
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMLODDisplayProxy.cxx,v <-- vtkSMLODDisplayProxy.cxx
new revision: 1.17; previous revision: 1.16
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMLODRenderModuleProxy.cxx,v <-- vtkSMLODRenderModuleProxy.cxx
new revision: 1.8; previous revision: 1.7
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMPVDWriterProxy.cxx,v <-- vtkSMPVDWriterProxy.cxx
new revision: 1.4; previous revision: 1.3
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMPVDWriterProxy.h,v <-- vtkSMPVDWriterProxy.h
new revision: 1.2; previous revision: 1.1
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMPWriterProxy.cxx,v <-- vtkSMPWriterProxy.cxx
new revision: 1.2; previous revision: 1.1
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMPWriterProxy.h,v <-- vtkSMPWriterProxy.h
new revision: 1.2; previous revision: 1.1
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMPart.cxx,v <-- vtkSMPart.cxx
new revision: 1.29; previous revision: 1.28
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMPart.h,v <-- vtkSMPart.h
new revision: 1.12; previous revision: 1.11
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMSourceProxy.cxx,v <-- vtkSMSourceProxy.cxx
new revision: 1.46; previous revision: 1.45
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMSourceProxy.h,v <-- vtkSMSourceProxy.h
new revision: 1.27; previous revision: 1.26
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMWriterProxy.cxx,v <-- vtkSMWriterProxy.cxx
new revision: 1.7; previous revision: 1.6
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMWriterProxy.h,v <-- vtkSMWriterProxy.h
new revision: 1.5; previous revision: 1.4
(0007045)
David Karelitz (reporter)
2007-04-02 11:54

 This still seems a little messed up. The statistics view says I have 4.535 MB, and the composite slider is set at 2.7 MB, yet it doesn't composite. Do the statistics view/information tab and the composite slider display/use different numbers?
(0007118)
Ken Moreland (manager)
2007-04-03 17:28

 I agree. This still does not seem to be working quite right. Here is a situation where it seems to fail.

1. Set the Composite Threshold to about 3 MB.
2. Set the Subsample Rate large enough to be able to tell you are in composite mode.
3. Make a Sphere with both Theta and Phi resolution of 300.

The reported size of the data is roughly 5 MB, but compositing is still off.
(0007129)
Utkarsh Ayachit (administrator)
2007-04-04 10:37

 I tried exactly what you said.

Initially there were no server view windows (since it wasn't compositing). As soon as I hit apply after creating the 300x300 sphere, server side windows poped up and I see the the composited image.

Note that sub-sampling is used only during interactive render. While interacting with this sphere, I get compositing (and consequently subsampling) only when LOD is off (or compositing threshold is very low) which makes sense.
(0007221)
Ken Moreland (manager)
2007-04-10 13:21

 Berk just brought up the fact that the problem is probably that we are looking at the full mesh size, and the composite decision is based on the surface geometry size. Thus, this is not really a bug. I will open a lower priority item to add the surface geometry size to the statistics view.

 Issue History
Date Modified Username Field Change
2011-06-16 13:10 Zack Galbreath Category => (No Category)

Copyright © 2000 - 2018 MantisBT Team