Ah! I missed the info about ssh -X from different machines. Try doing a simple Wavelet source and slice that. Does that work?
On Thu, Jul 23, 2015 at 5:52 PM Kate Fissell <fiss...@pitt.edu> wrote: > Hi Utkarsh, > > Thanks for your super fast response. > Using a slice filter I also get no slice image. > I downloaded nightly build ParaView-4.3.1-882-gbdceec7-Linux-64bit > and I still have the problem. Is that the most recent git/master ? > > When you say you think the problem is related to the fix you list, > do you mean that the 15457 fix you needed to do for parallel > slice had the side effect of causing this remote connection issue, or, > do you mean that the parallel slice fix would hopefully solve > the remote connection issue ? > > I tried to take a look at the code changes in the fix. > I saw some stuff with extents. Do you think that the > problem is that the extent is computed incorrectly, eg > way too small, eg 0 ? Why would that happen only > on the Centos->Ubuntu remote connection ? > > thanks very much, > Kate > > On 07/22/2015 03:35 PM, Utkarsh Ayachit wrote: > > Kate, > > > > I suspect it's related to this fix: > > https://gitlab.kitware.com/paraview/paraview/merge_requests/92 > > > > I tested with the latest git/master and it does render correctly in > > client-server mode too. > > > > A workaround would be to use the Slice filter instead. It will be a > > little slower and more memory intensive than "Slice" representation, > > however. > > > > Utkarsh > > > > On Wed, Jul 22, 2015 at 3:08 PM, Kate Fissell <fiss...@pitt.edu> wrote: > >> Hi, > >> > >> On Paraview versions 4.1 and greater if I ssh -X from a Centos machine > into > >> an Ubuntu > >> graphics server to run Paraview I have a problem with viewing images. > >> > >> I load the AnalyzeNifTIIO plugin, and load a nifti image, and I believe > it > >> loads correctly. > >> I get the wireframe, the Information panel gives the correct > cells/point. > >> If I change to > >> Slice representation the view window stays blank. Volume > representation is > >> fine, I get the > >> 3D rendering. > >> Same thing if I load a vti format of the data, no slice view. > >> > >> This happens when I ssh from a Centos machine, it does not happen when > I ssh > >> from > >> an Ubuntu machine. In both cases I believe I am using glx to do the > >> rendering locally, > >> not doing a setenv DISPLAY to ship the rendered picture over the net. > >> It is the same glx version on the Ubuntu and Centos machine, but they > have > >> different > >> graphics cards. > >> > >> Ubuntu server running Paraview (console graphics): > >> OpenGL vendor string: NVIDIA Corporation > >> OpenGL renderer string: Quadro K4000/PCIe/SSE2 > >> OpenGL core profile version string: 4.3.0 NVIDIA 331.113 > >> OpenGL core profile shading language version string: 4.30 NVIDIA via Cg > >> compiler > >> OpenGL core profile context flags: (none) > >> OpenGL core profile profile mask: core profile > >> OpenGL core profile extensions: > >> OpenGL version string: 4.4.0 NVIDIA 331.113 > >> OpenGL shading language version string: 4.40 NVIDIA via Cg compiler > >> OpenGL context flags: (none) > >> OpenGL profile mask: (none) > >> OpenGL extensions: > >> > >> > >> Centos machine ssh'd to Ubuntu server: > >> OpenGL vendor string: NVIDIA Corporation > >> OpenGL renderer string: Quadro FX 580/PCIe/SSE2 > >> OpenGL version string: 2.1.2 NVIDIA 340.76 > >> OpenGL shading language version string: 1.20 NVIDIA via Cg compiler > >> OpenGL extensions: > >> > >> > >> Ubuntu machine ssh'd to Ubuntu server: > >> OpenGL vendor string: NVIDIA Corporation > >> OpenGL renderer string: Quadro K4000/PCIe/SSE2 > >> OpenGL version string: 2.1.2 NVIDIA 304.125 > >> OpenGL shading language version string: 1.20 NVIDIA via Cg compiler > >> OpenGL extensions: > >> > >> > >> In Paraview ParaView-v4.0.1 I do not have this problem. > >> I have the problem in Paraview-4.1, 4.2, 4.3. > >> > >> I am using your pre-compiled binaries as test, but I have the same > problem > >> with my compilation. > >> > >> Do you know what changed from ParaView-v4.0.1 to ParaView-v4.1 that > would > >> cause > >> this or what the workaround is ? > >> > >> thanks > >> Kate > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Please keep messages on-topic and check the ParaView Wiki at: > >> http://paraview.org/Wiki/ParaView > >> > >> Search the list archives at: http://markmail.org/search/?q=ParaView > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview > >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview