[Paraview] Import a four-dimensional array and "slice" one dimension to plot in 3D

Hi all, Is there a way to import (any format) a 4D array in paraview, then to slice one of the dimensions (i.e. use only one 3D hyperplane), and plot the remaining 3D array with paraview's volume rendering? I know I could manipulate the data to make it 3D before using it in Paraview, but I was

Re: [Paraview] Superbuild repo change?

> I did a fresh pull of the ParaView superbuild repository, and now I can’t do > a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). > > First, I had to remove the entries for “qt” and “scipy“ in the CMakeLists.txt: .. > After removing those entries, the cmake completes and the build starts

Re: [Paraview] paraview compilation issue

Your PYTHON_LIBRARY is invalid. Please make sure it points to a libpython2.7.so. On Wed, Feb 15, 2017 at 2:25 PM, Bishwajit Dutta wrote: > Hi Utkarsh, > > Pls find it attached. > > Thank you so much. > > -Bishwajit > > On Wed, Feb 15, 2017 at 8:26 AM, Utkarsh Ayachit < >

Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

Duh. “git submodule update” seems to fix things related to the qt and scipy issue. My Mac has Xcode version 6.2 Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -Original Message- From: Ben Boeckel

Re: [Paraview] Superbuild repo change?

On Wed, Feb 15, 2017 at 13:50:13 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > I did a fresh pull of the ParaView superbuild repository, and now I can’t do > a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). > > First, I had to remove the entries for “qt” and “scipy" in

Re: [Paraview] volume vs volume

As a side note, the Mesh Quality filter does not work on all 3D cell types. I think prisms and pyramids are not supported. On Wed, Feb 15, 2017 at 9:07 AM, Dennis Conklin wrote: > Oops – meant Mesh Quality filter > > > > *From:* Dennis Conklin > *Sent:* Wednesday,

Re: [Paraview] One render view on Paraview Catalyst

Hi, In the ParaView GUI you can set the Remote Render Threshold (under Edit->Settings...->Render View) to a very large number to ensure that all rendered data gets delivered to the client for rendering. In general this is a bad way to do things though since that can use a lot of bandwidth and

[Paraview] Examples of Field Variables Manipulation for Exodus Multi-block datasets

All, I can't find a good example of manipulating Field Variables (Global Variables) in Exodus Multi-block datasets. For instance, I wrote a filter to calculate the total_volume of a mesh. Currently I print this out to the screen. I would like to add a Field variable of Total_volume but I

Re: [Paraview] volume vs volume

Oops - meant Mesh Quality filter From: Dennis Conklin Sent: Wednesday, February 15, 2017 7:56 AM To: Paraview (paraview@paraview.org) Subject: Re: [Paraview] volume vs volume Alan, A quick and dirty way to get individual element volumes is to use the mesh refinement

[Paraview] Superbuild repo change?

I did a fresh pull of the ParaView superbuild repository, and now I can’t do a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). First, I had to remove the entries for “qt” and “scipy" in the CMakeLists.txt: -- Determined source version for paraview: 5.2.0 CMake Error at

Re: [Paraview] paraview compilation issue

Can you attach your CMakeCache.txt please? Thanks Utkarsh On Wed, Feb 15, 2017 at 7:26 AM, Bishwajit Dutta wrote: > Hi All, > > I configured paraview to compile for CPU rendering with the below option > on ubuntu 14.04 and Python 2.7.6: > > cmake ../ -DBUILD_TESTING=OFF

Re: [Paraview] volume vs volume

Alan, A quick and dirty way to get individual element volumes is to use the mesh refinement filter and set the Quality measure to volume. Then the "Quality" variable in the elements is actually volume. Dennis ___ Powered by www.kitware.com Visit

[Paraview] paraview compilation issue

Hi All, I configured paraview to compile for CPU rendering with the below option on ubuntu 14.04 and Python 2.7.6: cmake ../ -DBUILD_TESTING=OFF -DCMAKE_BUILD_TYPE=Release -DPARAVIEW_ENABLE_CATALYST=ON -DPARAVIEW_ENABLE_PYTHON=ON -DPYTHON_LIBRARY=$PYTHON_LIBRARY

[Paraview] Problem testing PV 5.3.0 RC1

Hello, I am testing ParaView-5.3.0-RC1-Qt5-OpenGL2-Windows-64bit. I run into a problem when using PV with a script. When I launch a simple script with the command D:\ParaView-5.3.0-RC1-Qt5-OpenGL2-Windows-64bit\bin\paraview.exe --script=testSphere.py I have the following error message in the

[Paraview] One render view on Paraview Catalyst

I generated python script for Catalyst from Paraview. When I run my code with MPI, I get render window for every MPI process. But i want to have only one window for all MPI processes. I already tried have script for view only on root and on another only script for live visualization (without