Utkarsh - thanks for the info. I believe that you’re right that the build
didn’t go as intended.
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone: 410-278-6266
-Original Message-
From: Utkarsh Ayachit
Yep - we built the HPC-side with “OpenGL2” … so does that mean that the
pre-built Mac/Linux binaries were both built with OpenGL?Is there some
way to check to see which OpenGL the client was built with?
Rick Angelini
USArmy Research Laboratory
CISD/HPC
> Yep - we built the HPC-side with “OpenGL2” … so does that mean that the
> pre-built Mac/Linux binaries were both built with OpenGL?Is there some
> way to check to see which OpenGL the client was built with?
The binaries distributed by paraview.org are indeed OpenGL2. The title
bar for
Rick,
I must admit this was a major "oops" in 5.0.0 and 5.0.1 releases. We
should have handled this better and I will make sure we do for 5.1.
Basically, what you have is a mismatch in rendering configurations for
client and server. One of them is build with VTK_RENDERING_BACKEND set
to OpenGL
We’re seeing an issue with the Exodus reader in version 5.0.1. We can read
any particular Exodus dataset when running ParaView 5.0.1 locally – read the
data on the same machine where the client is running. However, when we try to
load any of the Exodus datasets in client-server mode,
Yes, this is what I want Utkarsh.
The filter does not necessary has to output the distances on the output port
(which I presumably would do by assigning a field array to the output geometry)
but I definitely would like them to display and modify in the panel widget to
affect the execution
Andrzej,
Just to make sure I understand:
vtkCpCutter calculates slices aka contours on surface and also outputs
an array of "max-distance"s. You want the user to be able to see
these values on the panel for this filter and then change them which
in turn affects some execution logic in
Hi
You probably forgot to "git submodule update --init"
Regards
Mathieu Westphal
On Fri, May 27, 2016 at 10:25 AM, Nico Schlömer
wrote:
> When configuring ParaView with
> ```
> cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON
>
When configuring ParaView with
```
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -Wno-dev -DBUILD_DOCUMENTATION=ON
-DCMAKE_INSTALL_RPATH=/usr/lib/paraview