Animating Live Data: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
No edit summary
 
No edit summary
Line 27: Line 27:
Please supply additional sub-features if needed.<br><br>
Please supply additional sub-features if needed.<br><br>


Kent Eschenberg  eschenbe@psc.edu<br>
This page was created by
Pittsburgh Supercomputing Center<br>
Kent Eschenberg  eschenbe@psc.edu
Pittsburgh Supercomputing Center
but I cannot be responsible for contributes by others.

Revision as of 17:32, 23 October 2006

The general idea of this feature is to have ParaView automatically update its visualization as new data becomes available.

Usage Scenarios

It will help if we clarify the way this feature would be used.

  • A simulation produces transient (time varying) data where each time step is written to a different file.
  • A simulation refines its result where each refinement is written to a different file.
  • A data acquision system recording transient data writes each new set of measurements to a different file.
  • Greg's Case

Variations:

  • A file could instead be a set of files such as is produced by a parallel application. PV should not update until all files in the set are present.
  • Should there be support for the new data being in the same file as the old? That seems dangerous, if PV and the source get out of sync, but maybe its useful in some cases.

Please supply additional use cases if the above doesn't cover yours. If you add a **long** description please make your entry here a link to a new page where you can provide as much detail as desired.


Sub Features

It might help if this feature is broken down into sub-features. Here are some possible items:

Please supply additional sub-features if needed.

This page was created by
Kent Eschenberg   eschenbe@psc.edu
Pittsburgh Supercomputing Center
but I cannot be responsible for contributes by others.