[Paraview] Scaling cylinder glyph's radius and height individually

Dear community, When I try to scale cylindrical glyph objects by a 'Scalar', it scales both the radius and height of the glyphs. Is there a way to scale the radius by a Scalar1, and the height be a Scalar2? I have an unstructured grid, and for each point I want to create a cylinder that can

[Paraview] Glyphs and spreadsheets

Hello, I want to extract the output from a Glyph filter into a spreadsheet. I want the coordinates of the origin of each glyph and its components so I can plot the same vectors using matplotlib.quiver capability. I tried to do this using the Spreadsheet view, but I ran into some issues: -

Re: [Paraview] Glyphs and spreadsheets

Ok, I see that the Points field represent the points of the Glyph object. For instance, if we are using 2D Glyph as the Glyph type, there will be 4 entries in the Spreadsheet view with the same GlyphVector field, but different Point values. These 4 points represent the points used to draw the

Re: [Paraview] Plot selection over time for threshold

Jairaj, I’m not sure what exactly you mean by “the threshold,” but there are many ways to plot the average of a threshold-selection of cells over time. The most straightforward way is to open up the Find Data dialog box, select the cells you want to plot, and then create a Plot Selection Over

[Paraview] ParaView 5.x not showing all objects available in Pipeline Browser

Hi, I use ParaView to visualize data of our simulations using the Unstructured Grid data format. Up until ParaView 4.x everything worked fine: we typically visualize one set of data files as Surfaces and another as Wireframe. The Wireframe dataset refers to "fracture lines" in our simulations.

[Paraview] error when compiling Paraview 5.4 macOS 10.13

Hello, I am trying to compile Paraview 5.4 in MacOS 10.13.2 (High Sierra), using software from MacPorts 2.4.2. After a successful configuration, the make -j 4 command give the following error:

Re: [Paraview] error when compiling Paraview 5.4 macOS 10.13

Sergio, This problem was fixed in November 2016, so I am surprised you are running into it. Current ParaView master includes VTK that contains the commit commit 33631146a85dfa64433c3997f166cbaa96bedee9 Author: gnzlbg Date: Wed Nov 23 05:29:14 2016 -0500 [bugfix]

Re: [Paraview] Question about build paraview

It's kind of a quirk of CMake, but once CMAKE_CXX_COMPILER is set by the initial CMake configuration, you can't change it. So what should you do? The solution is to set an environment variable named CMAKE_CXX_COMPILER in your shell prior to running CMake for the first time. Set that variable to

Re: [Paraview] PV client-server: browsing remote files

Sebastien and Utkarsh, Thanks for both of your suggestions. I have now looked at them and they both look pretty good to me. I'll practice with these solutions and see which one I like best. Kind Regards, Robert -- Science personalities series: calculus and charity

Re: [Paraview] Question about build paraview

Actually I find the easiest way to do it is, assuming you have icc in your path, to set the CC and CXX environment variables on the command of the first run of cmake (or ccmake or cmake-gui, whichever one you are using). So the start of your build would be something like this: mkdir

Re: [Paraview] Question about build paraview

Ah, that's right, Ken. It has been a while since I have done this, but you are right that setting CC and CXX is the way to do it. On Mon, Jan 8, 2018 at 11:29 AM, Moreland, Kenneth wrote: > Actually I find the easiest way to do it is, assuming you have icc in your > path, to