Re: [Paraview] OSPRay, scaled spheres

Beauty. Thanks!! (I really need to take time to read the entire PV Guide) > On Oct 25, 2017, at 5:14 PM, David E DeMarle wrote: > > click the gear to show advanced properties, or use search field for glyph > type. > > > > David E DeMarle > Kitware, Inc. > Principal

Re: [Paraview] OSPRay, scaled spheres

click the gear to show advanced properties, or use search field for glyph type. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Oct 25, 2017 at 5:11 PM, Heiland, Randy wrote: > You lost me - in the

Re: [Paraview] OSPRay, scaled spheres

You lost me - in the Glyph Source block,I select Glyph Type = 2D Glyph. Then where is VERTEX? In the Display block, I choose Representation = Points which produces a blobby mess. But a very *smooth* blobby mess :) > On Oct 25, 2017, at 4:46 PM, David E DeMarle wrote:

Re: [Paraview] OSPRay, scaled spheres

That control is only available if the representation type is surface, this could explain why you don't see it on the ProgrammableSource. In the glyph filter, use 2D glyph, VERTEX. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone:

Re: [Paraview] OSPRay, scaled spheres

I only see the “OSPRay Use Scale Array” on the Properties for Glyph, not the Props for the ProgrammableSource. Expected? And so, OSPRay is rendering the chunky polygonalized spherical glyphs (Representation = Surface). If I could independently scale the implicit spheres and use OSPRay, I’d

Re: [Paraview] OSPRay, scaled spheres

To change the size based on values: check "OSPRay Use Scale Array" on "Display" section or "Properties" Tab Choose the array name you want to scale by with "OSPRay Scale Array" pulldown. Define your value to radius transfer function via the "OSPRay Scale Function" popup editor. Note 1: the

[Paraview] OSPRay, scaled spheres

Just want to make sure I’m not missing something. In my Pgmable Source PolyData, I render Points and love the OSPRay-rendered spheres. However, is there any mechanism for (independently) scaling these, i.e., other than the fixed Point Size? Or is the only way to get scalar-value scaled spheres

Re: [Paraview] LiveInsituLink proxy in pvpython client

Thank you, Andy, unfortunately your answer has shown me how little I understand about Catalyst. But maybe it leads in the right direction after some work from my side. Just to make sure that we are talking about the same thing: My pvpython client is supposed to automate some of the visualization

Re: [Paraview] multiple scalar fields

Give each array a name (vtkDataArray::SetName()) and use AddArray (vtkFieldData:AddArray()) instead of using the atttibutes based API (vtkDataSetAttributes::Set{Scalars/Tensors/Vectors}) ParaView uses named array access almost exclusively anyway. David E DeMarle Kitware, Inc. Principal

[Paraview] multiple scalar fields

How does one use 2 (or more) scalar fields in a dataset, e.g. one for a colormap, one to scale glyphs? E.g., Pgmable Source: pdo = self.GetPolyDataOutput() num_pts = 2 newPts = vtk.vtkPoints() cell_color_ID = vtk.vtkFloatArray() cell_radius = vtk.vtkFloatArray()

Re: [Paraview] Python Scripting - Acess vtkOpenGL cameras from .pvx files information

Leo, To handle 90-degree pitch or elevation, do the following: camera.Pitch(90) camera.OrthogonalizeViewUp() Render() Utkarsh On Tue, Oct 24, 2017 at 2:50 PM, Léo Pessanha wrote: > Thanks Utkarsh! > > This change would take a build right? Can't do it right now

Re: [Paraview] LiveInsituLink proxy in pvpython client

Hi Kolja, I can't recall if anyone tried the Catalyst Live connection through pvpython but I don't think anyone has done that yet. The design was meant to go through the GUI. My suggestion would be to start looking at the DoLiveVisualization() method in coprocessing.py. Cheers, Andy On Tue, Oct

Re: [Paraview] superbuild: fontconfig too old to compile (current does)

On Wed, Oct 25, 2017 at 13:35:51 +0200, Fabian Wein wrote: > thank you! So the current master will have the upgrade within a few days? It's not so simple :( . There's a build failure with older compilers: https://open.cdash.org/viewNotes.php?buildid=5114526 --Ben

Re: [Paraview] Programmable filter VTK/numpy

You should change 'array_name' to 'MetaImage'. Sorry I didn't make it clear that 'array_name' is just a placeholder for whatever name your array has. Cory On Wed, Oct 25, 2017 at 7:46 AM, Edoardo Pasca wrote: > Hallo Cory and all, > > I've spent a few minutes trying to

Re: [Paraview] superbuild: fontconfig too old to compile (current does)

On Wed, Oct 25, 2017 at 13:35:51 +0200, Fabian Wein wrote: > thank you! So the current master will have the upgrade within a few days? Hopefully. I need to get `gperf` onto the build machine since it is a new build dependency of fontconfig. --Ben ___

Re: [Paraview] Programmable filter VTK/numpy

Hallo Cory and all, I've spent a few minutes trying to find out where my script crashes: 1) I load a MetaImage and the scalars are named 'MetaImage' 2) Paraview crashes if I use inData = dsa.WrapDataObject(inputs[0]) B = inData.PointData['array_name'] # best practice is to name the array 3)

Re: [Paraview] superbuild: fontconfig too old to compile (current does)

I've pushed an MR for the common-superbuild here: Ben, thank you! So the current master will have the upgrade within a few days? Cheers, Fabian ___ Powered by www.kitware.com Visit other Kitware open-source projects at

Re: [Paraview] Equally spaced points on a slice (for the streamlines)

Hello, sorry for being late. The slice may be oriented arbitrary, it may be not a flat but cylinder slice e.t.c. But often I need just axis-aligned slices. Thanks for suggestion about sources. 2017-10-23 18:03 GMT+03:00 Utkarsh Ayachit : > Is the slice axis aligned?