MantisBT - ParaView
View Issue Details
0015716ParaView(No Category)public2015-09-09 21:482016-08-12 09:59
Alan Scott 
Cory Quammen 
normalminorhave not tried
closedmoved 
git-master 
5.1 
Sandia
incorrect functionality
0015716: Exodus refresh button doesn't update correctly
There is a bug with the exodus refresh button.

* Windows, 4.3.1, local server.
* Rename "cylinder_run1.e" as "cylinder.e" and open it.
* Load all the variables.
* Plot Global Variables Over Time.

* Next, delete cylinder.e, and rename "cylinder_run2.e" as "cylinder.e" and hit the "refresh data" button in Paraview.
* Now, click on the PlotGlobalVariablesOverTime view and everything should vanish.
* You will not be able to plot global variables any more.

Dateset is refreshBug (note to myself, Windows, Cal kevin). Ask me for it.

No tags attached.
? UUR_cylinder_run1.e (691,412) 2015-09-11 19:34
https://www.vtk.org/Bug/file/9903/UUR_cylinder_run1.e
? UUR_cylinder_run2.e (1,189,012) 2015-09-11 19:35
https://www.vtk.org/Bug/file/9904/UUR_cylinder_run2.e
Issue History
2015-09-09 21:48Alan ScottNew Issue
2015-09-11 19:34Alan ScottFile Added: UUR_cylinder_run1.e
2015-09-11 19:35Alan ScottFile Added: UUR_cylinder_run2.e
2015-10-15 21:11Alan ScottTarget Version => 5.1
2015-10-15 21:12Alan ScottNote Added: 0035301
2015-10-27 12:05Alan ScottTarget Version5.1 => 5.0
2015-11-04 11:24Utkarsh AyachitAssigned To => Cory Quammen
2015-11-04 15:42Cory QuammenNote Added: 0035412
2015-11-04 16:01Cory QuammenNote Added: 0035413
2015-11-05 02:06Cory QuammenNote Added: 0035428
2015-11-06 10:43Cory QuammenNote Added: 0035433
2015-11-06 10:44Cory QuammenNote Edited: 0035433bug_revision_view_page.php?bugnote_id=35433#r1385
2015-11-06 11:02Joachim PouderouxNote Added: 0035434
2016-01-08 15:31Utkarsh AyachitTarget Version5.0 => 5.1
2016-08-12 09:59Kitware RobotNote Added: 0038888
2016-08-12 09:59Kitware RobotStatusbacklog => closed
2016-08-12 09:59Kitware RobotResolutionopen => moved

Notes
(0035301)
Alan Scott   
2015-10-15 21:12   
Also not working remote server. From a user:


The "Refresh" button that reads in new time steps for an existing/open data set doesn't work for me. I am connected to a paraview server on clusterName and trying to update the data in a simulation that is running. When I press the "Refresh" button, I get the following error:


ERROR: In /projects/viz/paraview/src/ParaView/4.4.0/ParaView4/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, line 134

vtkSISourceProxy (0x11888a80): Error pushing property state: Refresh
(0035412)
Cory Quammen   
2015-11-04 15:42   
I can reproduce the described behavior.
(0035413)
Cory Quammen   
2015-11-04 16:01   
This bugs back to at least ParaView 4.1.
(0035428)
Cory Quammen   
2015-11-05 02:06   
The problem is likely with the reader. Looking at the Field Data from the second file loaded when clicking Refresh, the field data is not updated properly. There are fewer entries in each column than timesteps, which is why the Plot Global Variables Over Time filter does not consider the columns to be temporal data in the second file.
(0035433)
Cory Quammen   
2015-11-06 10:43   
(edited on: 2015-11-06 10:44)
Three things seem to be going on:

1) The function invoked by the Refresh button does not mark the reader as modified, so no data is updated.

2). If you add a Modified() all to the reader that is triggered by the Refresh() button, somehow all the arrays statuses are marked as inactive.

3). If you modify the statuses manually in the GUI, the arrays can be set to active. Point and cell arrays are then updated. Global data in the field data are being set to arrays cached during the initial reading of the file.

The solution will involve invalidating the cache entries for global data arrays.

(0035434)
Joachim Pouderoux   
2015-11-06 11:02   
It would be great to think about a mechanism that could be generalized to other readers as everybody dream about a refresh button for every readers in PV!
(0038888)
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.