Hello,
I'll let the ParaView developpers confirm this, but this is almost
definitely a bug in OpenFoam, not ParaView.
The error message says it all: some faces are not oriented correctly. I
had already encountered this bug a few years ago when testing The
OpenFoam meshing output with another CFD
Oops, the parent class is vtkSMPropRepresentationProxy but not
vtkSMSurfaceRepresentationProxy.
Actually the program was developed by somebody else, and I wanted to
compile it with a newer version of Paraview.
It has a custom plugin which deals with volume rendering and
isosurface in one XML (via
Hi Joe,
this might be a typo, but first why did you need to inherit
vtkSMSurfaceRepresentationProxy.h to create an isosurface ?
Could you be more precise on what you use to do on 3.10 and what you
try to do in general ?
Thanks,
Seb
On Wed, Dec 14, 2011 at 1:57 PM, Joe Ping-Lin Hsiao wrote:
> H
Hi,
I used to inherit
ParaView-3.8.1\Servers\ServerManager\vtkSMSurfaceRepresentationProxy.h
to create an isosurface. But the class was gone since ParaView 3.10.
I found
ParaView-3.12.0\ParaViewCore\ServerManagervtkSMNewWidgetRepresentationProxy.h
has identical comments. Can I use the class to c
Interesting. Good to know. I cannot find those errors on the dashboard
anymore. I'll keep looking. If I can identify the machines, I'll try
to see if the Qt was binary install or built-from-source there too.
Thanks
Utkarsh
On Wed, Dec 14, 2011 at 11:38 AM, Biddiscombe, John A. wrote:
> Utkarsh
>
Utkarsh
I was using 4.7.1 - but it was a downloaded binary x64 bit from some place I
don't remember.
After much waiting, I now have a 4.7.4 compiled natively x64 on this machine
and I'm pleased to say that all the errors have disappeared. Python shell works
normally and CoProcessing Export sta
Paul,
I did so and it continued to work fine. I'm wondering whether it is related
to the TCL_LIBRARY variable not being set. Off to recompile it to find out.
Thanks,
Adriano
===
Adriano Gagliardi MEng PhD
Business Sector Leader
Computational Aerodynamics
A
The online ParaView guide has some introductory material for the Python
Programmable Filter
(http://paraview.org/Wiki/ParaView/Users_Guide/Python_Programmable_Filter). It
helps if you are familiar with programming directly with VTK.
By convention, ParaView will automatically apply a displaceme
Short answer, no.
If your surface is convex, you could threshold the surface elements you
need by first running the extract surface filter, then generating cell
normals, then using the calculator to extract the x component of the cell
normals, then thresholding all cells with the x component of th
Dominik,
we're not very high on the list of priorities for the xdmf people.
However the xdmf2 rewrite that is available from
git://public.kitware.com/Xdmf2.git
is stable (and active it seems) - I assume this is not the one you are
referring to (wrt paraview), and I am hoping soon to start using i
That's very fishy. But this is good start. I kept on seeing these
errors on some random dashboards and never was sure why. At least we
now have a starting point. Guessing this is a windows machine? What
version of Qt?
Utkarsh
On Wed, Dec 14, 2011 at 5:18 AM, Biddiscombe, John A. wrote:
> PS. And
Does the system python also crash if you set the library path to have the
paraview directories? If this is the case you probably gave a conflicting
lib in paraview.
On 14 Dec 2011 14:32, "Adriano Gagliardi" wrote:
> **
> System version is identical. The environment variables are identical with
>
System version is identical. The environment variables are identical with
the exception of those relating to window ids. LD_LIBRARY_PATH has changed,
but when running ParaView two directories, the paths to the ParaView root
and lib directories, have been added to the start. Nothing else is
differen
Hi Utkarsh,
No, there was no feedback on many of my latest bug reports, neither
were they fixed in the official branch... so I thought it was dead and
switched to the PV branch. I can not even find anymore where the
official repo is, the one found by google on
http://www.xdmf.org/index.php/Get_Xdm
Dominik,
Are these issues already fixed on Xdmf's official branch? The plan is
to sync up ParaView's branch with Xdmf's periodically. Feel free to
report bugs and patches on the ParaView bug tracker. However, if the
issues have not been addressed in the official Xdmf branch, they will
have to be a
PS. And python stuff gives errors like this when I try anything
libprotobuf ERROR
..\..\..\..\..\Code\pv-meshless\Utilities\protobuf\src\google\protobuf\wire_format.cc:1059]
Encountered string containing invalid UT
F-8 data while serializing protocol buffer. Strings must contain only UTF-8;
use
using pv 3.12 I cannot save state files correctly, and generation of
coprocessing scripts also fails because somehow - non ascii (UTF-8) --
characters are getting into strings.
.
The index 3 should re
I'm new to the Python Programmable Filter, so would you mind pointing me to
a tutorial or maybe sending an example file?
Is it possible to write the magnifying factor(applying displ.) and tick the
"Has Mode Shape" directly to the exodusII file from my fortran program?
And can I find any documentat
Another good file format for writing topology and data to different files,
is the Ensight Gold format. See this post
http://www.paraview.org/pipermail/paraview/2010-February/015708.html
You can write both acsii and binary files. I can send you a simple fortran
routine, which writes topology(quads)
you can use xdmf, with a .xmdf file for the light data (meta data), and
2 files or more (hdf5 or binary) for the heavy data (field data, point
data, connectivity...).
more info in http://www.xdmf.org
On 13/12/2011 21:01, Robert Maynard wrote:
I am pretty sure that both the Legacy VTK and t
20 matches
Mail list logo
