View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0007314ParaViewBugpublic2008-07-09 09:452016-08-12 09:57
ReporterDaniel Goldstein 
Assigned ToBerk Geveci 
PrioritynormalSeverityfeatureReproducibilityhave not tried
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0007314: reload button wold be really nice for watching simulations
DescriptionIn V2.6 a trick that existed was to build a visualization, and then as new time steps (more vtk files)
became available from a simulation one could delete the input file name, reload, then repast the file name
and reload and the visualization would then be reloaded with more time steps.

This no longer works with PV3. It would be great to have a reload button that would reload the whole pipe line based on the current pvd input file. This should be universal enough that it would work with other file formats. For me pvd files would cover it.

Just to be clear. I run a simulation. After n steps I build a pvd file and load it into PV. THen I build a pipeline to look at an interesting feature. After n+x steps I rebuild a pvd file with more time steps
(same name). With this new feature I would then hit reload and the pipeline would re-build based on the updated pvd file.

Thanks for all the great work on PV!

Dan (
TagsNo tags attached.
Topic Name
Attached Files

has duplicate 0007298closedKen Moreland reloading (ensight) case files 
has duplicate 0007306closedKen Moreland reloading file is not possible - bad usability 
has duplicate 0012100closedKitware Robot A "Reload data" button would be nice. 

olesen (reporter)
2008-08-06 10:34

As suggest by Utkarsh on the mailing list:

One possibility is that we use the "immediate_update" attribute
specified on the property to indicate to the auto-generated GUI that the
property needs to be pushed immediately when the GUI changes, without
waiting for (or affecting) "Apply".

Adding this single feature would provide a means to solve many problems.
olesen (reporter)
2008-08-13 00:40

Example usage case:

Using the ParaView reader module included as part of the OpenFOAM distribution. The GUI has a number of provisions (checkboxes) for altering the reader's behaviour that should ideally be modifiable without requiring the reader to re-execute.

These are the switches
1. Include Sets
2. Include Zones
These two include cell/face/point sets/zones in the list of mesh parts
that can be selected. Once the OpenFOAM mesh is loaded, the zones
information is available and can be included in the list, depending on
whether the user considers it useful or just clutter. Displaying these
on the mesh-parts list leaves the reader output unaltered until the user
explicitly selects a particular set or zone.

3. Show Patch Names
Adds or removes a bunch of vtkTextActors to label the patch (boundary)
region. This can be useful for finding which boundary is where, but
otherwise clutters up the display. Does not affect the reader output.

4. Cache Mesh
Select if the OpenFOAM mesh information should be cached between
time-steps. This skips reading from disk for the geometry, but
unfortunately until the VTK time handling improves, we cannot exploit
this as much as desired. Does not affect the reader output.

Perhaps rather than a simple 'immediate' property, the checkboxes should
receive even more attributes. AFAIK it is currently not possible for the
reader to change the GUI defaults or values. With vtkDataArray, it is
possible to add a listener, but that causes the GUI state to change and
'Apply' lights up green.

A simple example of wishing to push integer information to the GUI:
In the EnSight reader, the modified version has the default ByteOrder as
"auto detect" (UNKNOWN byte-order). After the Ensight binary files have
been read, the byte-order is known and it could be nice to change the
GUI display to reflect this information.
However, the main motivation is the desire to add a local configuration
file that the reader could parse and dynamically set particular reader
Kitware Robot (administrator)
2016-08-12 09:57

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.

 Issue History
Date Modified Username Field Change
2008-07-09 09:45 Daniel Goldstein New Issue
2008-07-09 10:50 Utkarsh Ayachit Category 3.4 => 3.6
2008-08-06 10:34 olesen Note Added: 0012946
2008-08-12 11:39 Berk Geveci Assigned To => Berk Geveci
2008-08-12 11:39 Berk Geveci Status backlog => tabled
2008-08-13 00:40 olesen Note Added: 0012996
2009-02-17 19:09 Ken Moreland Relationship added has duplicate 0007298
2009-02-17 19:10 Ken Moreland Relationship added has duplicate 0007306
2009-02-17 19:10 Ken Moreland Category 3.6 => Pending
2009-02-20 11:13 Ken Moreland Category Pending => 3.8
2009-05-13 13:40 Utkarsh Ayachit Target Version => 3.8
2010-07-12 09:45 Utkarsh Ayachit Category => Bug
2010-07-12 09:45 Utkarsh Ayachit Target Version 3.8 => 3.10
2011-04-18 08:41 Utkarsh Ayachit Relationship added has duplicate 0012100
2016-08-12 09:57 Kitware Robot Note Added: 0037582
2016-08-12 09:57 Kitware Robot Status expired => closed
2016-08-12 09:57 Kitware Robot Resolution open => moved

Copyright © 2000 - 2018 MantisBT Team