[Paraview-developers] Get data from server to client (helper?)

[Biddiscombe, John A.]

The data will be 1D/2D histograms, varying in size, but probably max of 256x256 (not really large, but. I used the IntVector property in the past and it was awful, hence the desire for something better).

the histograms are drawn in the background of the volume render transfer function widget and returned with regions overlaid where the user has selected regions, but now I remember we added the region transfer stuff back so actually I don't need to resend the histograms back, just the regions with their params for intensity and shape/fade pattern etc. No worries, all will be fine.

thanks for sorting me out

JB

> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: 24 September 2013 20:43
> To: Biddiscombe, John A.
> Cc: paraview-developers at paraview.org
> Subject: Re: [Paraview-developers] Get data from server to client (helper?)
> 
> It doesn;t change how you'd get the data from server to client. The question
> is how are you planning to send data from client to server?
> What is the modified data? Just a collection of modifications or a large
> dataset?
> 
> Utkarsh
> 
> On Tue, Sep 24, 2013 at 2:34 PM, Biddiscombe, John A. <biddisco at cscs.ch>
> wrote:
> > I've just remembered, that on some occasions, I will need to send the
> > modified data back - BUT, I need to send it back to all nodes.
> >
> > Does this change your previous answers?
> >
> > JB
> >
> >> -----Original Message-----
> >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> >> Sent: 24 September 2013 20:18
> >> To: Biddiscombe, John A.
> >> Cc: paraview-developers at paraview.org
> >> Subject: Re: [Paraview-developers] Get data from server to client
> >> (helper?)
> >>
> >> > Would there be improved efficiency doing it that way using
> >> ClientServerMoveData?
> >>
> >> I don't think so. I just different ways for doing the same thing. You
> >> might infact get better performance by using the information object
> >> since you can control what is serialized, with the
> >> ClientServerMoveData route, since the code is for any arbitrary data,
> >> it will transfer more meta-data, possibly. Also then the pipline and
> >> extents can be confusing too. So I'd recommend the vtkPVInformation
> route.
> >>
> >> Utkarsh