ClientSideData: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
==Requirements== | ==Requirements== | ||
* Support general-purpose collection of data from one-to-many parallel servers to the client. | * Support general-purpose collection of complete data sets from one-to-many parallel servers to the client. | ||
* Support collection of time-varying data from one-to-many parallel servers to the client, e.g: retrieve the value at a specific point/cell over time. | |||
* For scalability, support special-purpose collection of data subsets from one-to-many parallel servers to the client. | * For scalability, support special-purpose collection of data subsets from one-to-many parallel servers to the client. | ||
Revision as of 16:54, 20 December 2005
Rough Draft
Requirements
- Support general-purpose collection of complete data sets from one-to-many parallel servers to the client.
- Support collection of time-varying data from one-to-many parallel servers to the client, e.g: retrieve the value at a specific point/cell over time.
- For scalability, support special-purpose collection of data subsets from one-to-many parallel servers to the client.
Implementation
- A new class, vtkSMClientSideDataProxy, has been created for general-purpose work: it collects a complete vtkDataSet from the servers. To use it, use the AddInput() method to connect it to a source proxy, then call GetCollectedData() to return a vtkDataSet. Internally, it uses vtkMPIMoveData to handle the transfer of data from server(s) to client.
Examples
An example of client side data in action: the histogram in this screenshot was generated directly from the vtkDataSet transmitted to the client:
