Re: [Paraview] No module named paraview...

Sorry forgot to add. Yes, I am using 4.3.1. Thanks On 9 September 2015 at 11:57, Ben Boeckel wrote: > On Wed, Sep 09, 2015 at 11:32:20 +0800, Ruggiero Guida wrote: > > Fatal Python error: PyThreadState_Get: no current thread > > Abort trap: 6 > > Oof. Are you able to

Re: [Paraview] The approach of Paraview's parallel rendering

ParaView always uses iceT to sort last. Sort last means nodes don't really care at all what the others have. Each just renders whatever they have locally, communicate the color and depth buffer, and let a depth buffer decide who's color wins at each pixel. D3 is orthogonal. If you apply it, than

Re: [Paraview] Plot over Line source

Hi Richard, If you don't mind, let's keep the discussion on the list so that others may benefit from the discussion. Outputting a vtkTable is the right thing to do. What I suspect is happening with the first error message is that if you execute a programmable source with the output set to one

Re: [Paraview] Paraview 4.3.1 OSMesa build - QWidget::repaint: Recursive repaint detected

Have sent the CMakeCache.txt off list as it’s a couple hundred KB. I still get the recursive paint error on the client – it immediately precedes the warning about the 3/4 component images from the client, and the crash on the server. In the non-debug server I don’t get a segfault – but it

Re: [Paraview] Paraview 4.3.1 OSMesa build - QWidget::repaint: Recursive repaint detected

I have a feeling something's wrong with the OSMesa build. Try running pvpython/pvbatch on that build. Are you able to render/save images from the Python clients? Utkarsh On Wed, Sep 9, 2015 at 9:52 AM, David Trudgian < david.trudg...@utsouthwestern.edu> wrote: > Have sent the CMakeCache.txt off

Re: [Paraview] Isosurface and slicing with Catalyst in C++

Hi Utkarsh, I built Catalyst 4.4-RC2, pulled the examples, and compiled CxxMappedDataArrayExample. When running it, I get this: ./CxxMappedDataArrayExample SampleScripts/feslicescript.py Error: Cannot import vtkPVServerManagerDefaultPython Error: Cannot import vtkPVAnimationPython Thanks,

Re: [Paraview] Isosurface and slicing with Catalyst in C++

Matthieu, Those messages are pretty much warnings. The Catalyst editions don't have all ParaView modules and hence the Python script prompts about missing modules. The code should still be executing properly. Utkarsh On Wed, Sep 9, 2015 at 12:04 PM, Dorier, Matthieu wrote: >

Re: [Paraview] Isosurface and slicing with Catalyst in C++

Indeed, I see the outputs. Thanks! Matthieu From: Utkarsh Ayachit [utkarsh.ayac...@kitware.com] Sent: Wednesday, September 09, 2015 11:07 AM To: Dorier, Matthieu Cc: paraview@paraview.org Subject: Re: [Paraview] Isosurface and slicing with Catalyst in C++

Re: [Paraview] [EXTERNAL] Volume Rendering 17GB 8.5 billion cell volume

I have nothing to add, other than volume rendering 8 billion cells would be amazing. ParaView should grumble, but maybe you are running out of memory? Try using the View/ Memory Inspector for the datasets below that actually do work? Then, do the same for your big one? Alan -Original

Re: [Paraview] Paraview 4.3.1 OSMesa build - QWidget::repaint: Recursive repaint detected

Utkarsh, Thanks – your hunch was correct. Went back through building llvm, osmesa, libGlu and now have a working setup. Not sure where I went wrong, but it’s all good now. DT -- David Trudgian Ph.D. Computational Scientist, BioHPC UT Southwestern Medical Center Dallas, TX 75390-9039 Tel:

Re: [Paraview] Paraview 4.3.1 OSMesa build - QWidget::repaint: Recursive repaint detected

Great! Glad to know it's working. Utkarsh On Wed, Sep 9, 2015 at 3:07 PM, David Trudgian < david.trudg...@utsouthwestern.edu> wrote: > Utkarsh, > > > > Thanks – your hunch was correct. Went back through building llvm, osmesa, > libGlu and now have a working setup. Not sure where I went wrong,

[Paraview] Volume Rendering 17GB 8.5 billion cell volume

Hi, We have been experimenting with using Paraview to display very volumes from very large TIFF stacks generated by whole-brain microscopy equipment. The test stack has dimensions of 5,368x10,695x150. Stack is assembled in ImageJ from individual TIFFs, exported as a RAW and loaded into paraview.

[Paraview] External data

How do I pull or acquire the "ExternalData" from Kitware? I am trying to find ghost_cells.vtu. Thanks, Alan ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep

Re: [Paraview] External data

If you have built ParaView and let the build download the external data (the default options), then the files can be accessed from ExternalData in the build directory. -Ken From: ParaView > on behalf of Walter Scott

Re: [Paraview] External data

Thanks Ken! Since some of my LANs and clusters can't see the outside world, I always manually pull the build files. Thus, ExternalData is not in my build directory. Is there a manual way to do the pull? Alan From: Moreland, Kenneth Sent: Wednesday, September 09, 2015 2:21 PM To: Scott, W