MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014834ParaView(No Category)public2014-06-30 16:392015-01-11 08:16
ReporterBurlen 
Assigned ToUtkarsh Ayachit 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version4.2 
Target VersionFixed in Version4.2 
ProjectTBD
Topic Name14834_fix_representation_update
Typeincorrect functionality
Summary0014834: info not updated after visibility change
Descriptionafter loading state where a filter is invisible, making the filter visible causes the filter to render itself correctly however client side info (information panel) is not updated. This can cause some filters to be disabled incorrectly. Probably other weirdness as well.

see also mail list thread
http://public.kitware.com/pipermail/paraview/2014-June/031527.html [^]

steps to reproduce:

1. start client
2. create plane and sphere w/ defaults
3. make sphere invisible
4. save state
5. delete all
6. load state
7. make sphere visible
8. look at information panel.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0014888closed Utkarsh Ayachit Error output load state, visibility 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-06-30 16:39BurlenNew Issue
2014-06-30 16:40BurlenDescription Updatedbug_revision_view_page.php?rev_id=780#r780
2014-06-30 16:41BurlenDescription Updatedbug_revision_view_page.php?rev_id=781#r781
2014-06-30 16:44BurlenProduct Version => 4.1
2014-06-30 16:44BurlenDescription Updatedbug_revision_view_page.php?rev_id=782#r782
2014-07-09 16:21Utkarsh AyachitAssigned To => Utkarsh Ayachit
2014-07-09 16:21Utkarsh AyachitProduct Version4.1 => 4.2
2014-07-21 15:09Utkarsh AyachitTopic Name => 14834_fix_representation_update
2014-07-21 15:09Utkarsh AyachitNote Added: 0033047
2014-07-21 15:09Utkarsh AyachitStatusbacklog => gatekeeper review
2014-07-21 15:09Utkarsh AyachitFixed in Version => git-next
2014-07-21 15:09Utkarsh AyachitResolutionopen => fixed
2014-07-22 08:32Utkarsh AyachitFixed in Versiongit-next => git-master
2014-07-22 08:32Utkarsh AyachitStatusgatekeeper review => customer review
2014-07-22 08:32Utkarsh AyachitNote Added: 0033060
2014-07-24 21:11Alan ScottNote Added: 0033083
2014-07-25 15:50Alan ScottRelationship addedrelated to 0014888
2014-07-25 15:51Alan ScottNote Added: 0033094
2014-07-25 15:51Alan ScottStatuscustomer review => closed
2014-08-29 10:59Utkarsh AyachitFixed in Versiongit-master => 4.2
2015-01-11 08:16Utkarsh AyachitSource_changeset_attached => ParaView master 8cb28017
2015-01-11 08:16Utkarsh AyachitSource_changeset_attached => ParaView master 94fdffe4

Notes
(0033047)
Utkarsh Ayachit   
2014-07-21 15:09   
commit 94fdffe40fd1024fd9415bfee5896444f0a70252
Author: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Date: Mon Jul 21 15:04:11 2014 -0400

    BUG 0014834: Fix representation update logic.
    
    vtkSMRepresentationProxy tried to take extra precations
    when calling vtkSMProxy::PostUpdateData() to ensure that the method
    wasn't called unless the VTK-side representation truly updated. If the
    VTKRepresentation didn't update, the upstream pipeline may not be
    updated and hence telling the input proxies that they have been updated
    would be incorrect.
    
    However it missed a case when loading state files. When loading state
    files, the this->MarkedModified is false by default. Thus the first time
    PostUpdateData() was called, it always assumed the VTKRepresentation had
    updated since we used the same flag. Fixed that by adding a new flag
    VTKRepresentationUpdated to indicate that the VTK representation has
    updated.
    
    This address the bug.
    
    Change-Id: I8a74d1734e0cec6a0f17690551e9a01761791fa4
(0033060)
Utkarsh Ayachit   
2014-07-22 08:32   
---------------------------------------------
Topics merged into master:
        0014874_fix_scalar_opacity_unit_distance
        14834_fix_representation_update
        dashboard-warnings-20140721
        refactor_python_tracing_2
(0033083)
Alan Scott   
2014-07-24 21:11   
Although the bug itself is fixed, there is now an error message put out by this test. Please fix the error before we close this bug.

Linux, master, local server.
Do steps above.
When you turn visibility on for the sphere, you get the following error prints:

ERROR: In /projects/viz/paraview/src/ParaView/4.2.0-alan2/ParaView4/ParaViewCore/ServerManager/Core/vtkSMArrayListDomain.cxx, line 324
vtkSMRepresentedArrayListDomain (0x3472220): Index out of range: 0


ERROR: In /projects/viz/paraview/src/ParaView/4.2.0-alan2/ParaView4/ParaViewCore/ServerManager/Core/vtkSMArrayListDomain.cxx, line 336
vtkSMRepresentedArrayListDomain (0x3472220): Index out of range: 0


ERROR: In /projects/viz/paraview/src/ParaView/4.2.0-alan2/ParaView4/ParaViewCore/ServerManager/Core/vtkSMArrayListDomain.cxx, line 312
vtkSMRepresentedArrayListDomain (0x3472220): Index out of range: 0


ERROR: In /projects/viz/paraview/src/ParaView/4.2.0-alan2/ParaView4/ParaViewCore/ServerManager/Core/vtkSMArrayListDomain.cxx, line 324
vtkSMRepresentedArrayListDomain (0x3472220): Index out of range: 1


ERROR: In /projects/viz/paraview/src/ParaView/4.2.0-alan2/ParaView4/ParaViewCore/ServerManager/Core/vtkSMArrayListDomain.cxx, line 336
vtkSMRepresentedArrayListDomain (0x3472220): Index out of range: 1


ERROR: In /projects/viz/paraview/src/ParaView/4.2.0-alan2/ParaView4/ParaViewCore/ServerManager/Core/vtkSMArrayListDomain.cxx, line 312
vtkSMRepresentedArrayListDomain (0x3472220): Index out of range: 1


ERROR: In /projects/viz/paraview/src/ParaView/4.2.0-alan2/ParaView4/ParaViewCore/ServerManager/Core/vtkSMArrayListDomain.cxx, line 324
vtkSMRepresentedArrayListDomain (0x3472220): Index out of range: 0


ERROR: In /projects/viz/paraview/src/ParaView/4.2.0-alan2/ParaView4/ParaViewCore/ServerManager/Core/vtkSMArrayListDomain.cxx, line 336
vtkSMRepresentedArrayListDomain (0x3472220): Index out of range: 0


ERROR: In /projects/viz/paraview/src/ParaView/4.2.0-alan2/ParaView4/ParaViewCore/ServerManager/Core/vtkSMArrayListDomain.cxx, line 312
vtkSMRepresentedArrayListDomain (0x3472220): Index out of range: 0


ERROR: In /projects/viz/paraview/src/ParaView/4.2.0-alan2/ParaView4/ParaViewCore/ServerManager/Core/vtkSMArrayListDomain.cxx, line 324
vtkSMRepresentedArrayListDomain (0x3472220): Index out of range: 1


ERROR: In /projects/viz/paraview/src/ParaView/4.2.0-alan2/ParaView4/ParaViewCore/ServerManager/Core/vtkSMArrayListDomain.cxx, line 336
vtkSMRepresentedArrayListDomain (0x3472220): Index out of range: 1


ERROR: In /projects/viz/paraview/src/ParaView/4.2.0-alan2/ParaView4/ParaViewCore/ServerManager/Core/vtkSMArrayListDomain.cxx, line 312
vtkSMRepresentedArrayListDomain (0x3472220): Index out of range: 1
(0033094)
Alan Scott   
2014-07-25 15:51   
This bug is fixed. Tested Linux, local server, master.

Moved the error listed in the notes to another bug.

Closing this one.