Hi Jake,
when you talk about running in multi-processing are you talking about
the solver that produces the data or about running Paraview in mpi-mode?
Which is the error you get?
Alessandro
On Wed, Jul 12, 2017 at 5:28 PM, Jake Gerard
wrote:
> Any help here would be greatly appreciated.
>
a global variable in some module that both the batch script and
> the programmable filter script import. Since the Python interpreter is
> shared between the two, and modules don't get imported twice, you should be
> able to set the variable in one and access it in another.
>
&g
Dear all,
I'm writing a pvbatch script in which I need to perform some
calculations on paraview objects (provided by a quite complex pipeline that
starts from reading vtu files and processing through reseamplewithdataset
filter and other filter manipulations) by using a programmable filter to
Hi,
I've just compiled the Paraview-5.3.0 superbuild with EGL. I created
an EGL dir in /usr/include with egl.h, eglext.h and eglplatform.h (taken
from www.khronos.org/registry/egl/) and I created a KHR dir in /usr/include
with khrplatform.h (taken from the same site).
ccmake already recognized
Hi,
I'm trying to export from a parallel MPI CFD code a set of results using
xdmf/hdf5 format in order to be read in Paraview.
The computational domain is divided into several parts (unstructured
polyhedral grid) and the idea is to write a xdmf with a further
subdivision to be read in parallel by
09 <(518)%20881-4909>
>
> On Fri, Dec 16, 2016 at 11:11 AM, Alessandro De Maio
> wrote:
>
>> I've done some more debugging on this topic.
>>
>> The problem is not related only to windows machines: the easy example
>> that I attached at the beginning of
I've done some more debugging on this topic.
The problem is not related only to windows machines: the easy example that
I attached at the beginning of this post (polyhedron.xmf) seems to be
correctly opened on Linux machines, but if you try to reopen it several
times (for example using the new 5.2
ataset that just works fine.
>
> Here the link:
> https://drive.google.com/file/d/0B5CHY8CFeTf2V09NVUhTRkpYSE0
> /view?usp=sharing
>
> Alessandro, can you test these files and report back which ones are
> working on your PC?
>
> Thanks,
> Armin
>
>
>
>
>
&
You're right: the polyhedral cells of the cube.vtu example do not guarantee
the planarity of faces, but this is a typical case of a polyhedral mesh
automatically generated starting from a tetrahedral one (this example has
been built using the Ansys-Fluent converter) and I think it's quite a usual
s
fic code.
> Just to note though, you need to use the Xdmf3 reader/writer in ParaView
> for xdmf files with polyhedral cells.
>
> Can you check that the .xmf file you generated from the .vtu file has
> the same topology information as the original .xmf file?
>
> Cheers,
> Armin
e xmf
generated file, the behaviour is the same and Paraview crashes.
Has anyone of you experience with xdmf polyhedral files in Paraview?
Thank you in advance for any suggestion
Alessandro De Maio
polyhedron.xmf
Description: Binary data
poly
11 matches
Mail list logo