Re: [Paraview] Problem reading a numpy NPZ file in ParaView 5.2.0 on Windows

On Fri, Jan 06, 2017 at 14:36:53 -0500, Cory Quammen wrote: > Thanks for the report. I looked into this and I think I know what is going on. > > In ParaView 5.2.0, we reduced the number of Python modules that > shipped with the ParaView binaries. One of the modules not included > was the "compiler

Re: [Paraview] Problem reading a numpy NPZ file in ParaView 5.2.0 on Windows

Guillaume, Thanks for the report. I looked into this and I think I know what is going on. In ParaView 5.2.0, we reduced the number of Python modules that shipped with the ParaView binaries. One of the modules not included was the "compiler" module. Now, Numpy checks to see if the "compiler" modul

Re: [Paraview] ParaView Catalyst: export point data

Ah, then you can skip the filter and directly make a vtkUnstructuredGrid containing only points and VTK_VERTEX cell that index them. See section 3 of the users guide for details. Somewhere in your adaptor you will have something like the following: output = vtk.vtkUnstructuredGrid() pts = output

[Paraview] ParaView Catalyst: export point data

Hello, thank you, but I mean how to pass these point data computed by a simulation code to ParaView in order to visualize them insitu. The Catalyst examples (https://gitlab.kitware.com/paraview/paraview/tree/master/Examples/Catalyst) usually use some type of a grid and data are then attached on

Re: [Paraview] ParaView Catalyst: export point data

Glyph Filter, type=2D subtype=points will create 1D cells (VTK_POINTS type) for every point (those that are attached to cells and those that are not used by any cell). To get only those points that are not used by cells, you may need the programmable filter. David E DeMarle Kitware, Inc. R&D Engi

[Paraview] ParaView Catalyst: export point data

Hello, is there any way how to export data using Catalyst which are not attached to any grid (like particles that are characterized only by the vector of their location)?  Thank you! Petr Valenta ___ Powered by www.kitware.com Visit other Kitware

Re: [Paraview] [EXTERNAL] OSRay and shadows

Thanks David, The Python code works well enough for my use. I see what you mean about 5.1, it almost does what I want, but is messes up the light directions. Regards, Bob On 6 January 2017 at 13:49, David E DeMarle wrote: > Bob, > > There is no control for that just yet. Work is in progress t

Re: [Paraview] [EXTERNAL] Re: Find Data bug

Hi, I've created a gitlab issue at https://gitlab.kitware.com/paraview/paraview/issues/17098. Alan, note that the both Select Through Points may be too fast to notice the difference. On my machine the first one seemed instantaneous while the second one took about 3 seconds or so. Thanks, Andy p

Re: [Paraview] [EXTERNAL] OSRay and shadows

Bob, There is no control for that just yet. Work is in progress to provide the full complement of light controls. If you are working in builting mode, you can resort to python as follows. lights = GetActiveView().GetRenderer().GetLights() for i in range(0, lights.GetNumberOfItems()): lights.Ge

Re: [Paraview] [EXTERNAL] OSRay and shadows

Hi, I'm using version 5.2 of ParaView. Thanks, Bob On 6 January 2017 at 00:17, Scott, W Alan wrote: > Bob, > > What version of ParaView are you using? 5.1.2 is known to have issues. > > > > Alan > > > > *From:* ParaView [mailto:paraview-boun...@paraview.org] *On Behalf Of *Bob > Flandard > *S