[Paraview] ClientDeliveryRepresentation

[Michael Jackson]

You can run a 64 bit pvserver and connect to it with a 32bit ParaView  
Client. Does that satisfy your needs?

Also, the GUI presented by ParaView is programmed in Qt 4. When Qt 4.5  
comes out then the journey to 64 bit on the client side should be  
straight forward although I am sure there will be "bumps" along the  
way. What specific "Paraview GUI Components" are you trying to avoid  
by writing your own client? (which is based on vtk/Qt itself as you  
state, which will have the _exact_ same problems that ParaView has  
with 32/b4 bit.)

_________________________________________________________
Mike Jackson                  mike.jackson at bluequartz.net
BlueQuartz Software                    www.bluequartz.net
Principal Software Engineer                  Dayton, Ohio



On Jan 7, 2009, at 2:14 PM, flymolo at gmail.com wrote:

> On Jan 7, 2009 7:21am, Utkarsh Ayachit <utkarsh.ayachit at kitware.com>  
> wrote:
> > When it comes to images there's whole lot of things to worry about
> >
> > such as extents, extent translators etc etc. Adding support for
> >
> > delivering image data in parallel may not be a trivial task.
> Thanks for letting me know. Maybe you can point me in the right  
> direction for an alternate solution then? I have a 12-16 gigabyte  
> image dataset that will be loaded by a 64 bit pvserver. I would like  
> to develop a client using paraview as a library to connect this  
> dataset to a client-side image plane widget. The rest of my client  
> is written in pure vtk/Qt so I'm avoiding paraview GUI components to  
> make my journey to 64-bit Qt/Cocoa easier.
>
> >
> >
> >
> > Utkarsh
> >
> >
> >
> > On Mon, Dec 29, 2008 at 1:04 PM, jonathan grimm flymolo at gmail.com>  
> wrote:
> >
> > > Can I write a strategy to make it support 3D Image data?
> >
> > > Would a vtkImageDataStreamer solve this problem?
> >
> > >
> >
> > > On Mon, Dec 22, 2008 at 10:05 AM, Utkarsh Ayachit
> >
> > > utkarsh.ayachit at kitware.com> wrote:
> >
> > >>
> >
> > >> Look at   
> vtkSMClientDeliveryStrategyProxy::UpdatePipelineInternal()
> >
> > >> that's where the data  type is set on the data-transfer filter.  
> BTW,
> >
> > >> ClientDeliverRepresentation cannot deliver 3D image data. It  
> can only
> >
> > >> deliver 2D slices.
> >
> > >>
> >
> > >> Utkarsh
> >
> > >>
> >
> > >> On Mon, Dec 22, 2008 at 12:17 PM, jonathan grimm flymolo at gmail.com 
> >
> >
> > >> wrote:
> >
> > >> > How does the ClientDeliveryRepresentation choose what data  
> type to send?
> >
> > >> > I have two pipelines:
> >
> > >> > Reader->ImageReslice->ClientDeliveryRepresentation- 
> >ImagePlaneWidget
> >
> > >> > and
> >
> > >> > Reader->ClientDeliveryRepresentation->hacked ImagePlaneWidget  
> that
> >
> > >> > allows
> >
> > >> > pipeline inputs
> >
> > >> > The first works beautifully, while the ImageReslice inside my  
> second
> >
> > >> > pipeline complains that it is getting polydata instead of  
> imagedata.
> >
> > >> > Any suggestions, besides producing an image plane widget that  
> uses a
> >
> > >> > server
> >
> > >> > side reslice?
> >
> > >> >
> >
> > >> > --
> >
> > >> > Sometimes it's hard to tell the dancer from the dance -  
> Corwin in CoC
> >
> > >> >
> >
> > >> > _______________________________________________
> >
> > >> > ParaView mailing list
> >
> > >> > ParaView at paraview.org
> >
> > >> > http://www.paraview.org/mailman/listinfo/paraview
> >
> > >> >
> >
> > >> >
> >
> > >
> >
> > >
> >
> > >
> >
> > > --
> >
> > > Sometimes it's hard to tell the dancer from the dance - Corwin  
> in CoC
> >
> > >
> >_______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview