I've a script that used to work ok on 4.0 and 4.1,
but now something is wrong with the colours.
Has anything changed between 4.0/4.1 to 4.3 to make
DataRepresentation3.DiffuseColor = [1.0, 1.0, 0.0]
not understood?
The full script:
Scott,
Thank you very much! The documentation looks to be well written.
Cheers,
Noah
On Mon, Jun 8, 2015 at 9:41 AM, Scott Wittenburg
scott.wittenb...@kitware.com wrote:
Hi Noah,
I don't see the specific link error message in your email, but it seems
possible it could be related to
Hello
Here's a ParaView Catalyst problem that may be related to bug (0027323).
O/S is ubuntu 14.04 lts - 64 bit
I'd like to connect to a Catalyst-enabled simulation, so first I'm
running the example code.
I do this:
1) download ParaView-v4.3.1-source and build. The ccmake settings are
Hi all,
another possibility is to write your Fortran data directly into VTK files
format.
I develop a KISS library in pure Fortran for IO of Fortran data into VTK
standard: see https://github.com/szaghi/Lib_VTK_IO
The exporters are almost complete. The importers are under developing by a
power
Hi,
I have also same problem in Mac OS 10.10 + python (framework) + OpenMPI
(compiled with gnu compilers). I compiled both ParaView 4.3.1 and also
4.2.0 from the source but after running Catalyst Examples i am getting
same port error. I might help to found the source of the problem.
Regards,
On 06/06/2015 14:47, Teo Ioannis wrote:
An example output would be very helpful.
Here is an example with 10 time-steps, on a fixed triangular mesh.
?xml version=1.0?
Xdmf Version=2.0 xmlns:xi=http://www.w3.org/2001/XInclude;
Domain
Grid Name=TimeSeries GridType=Collection
Hi Paul,
as you and Dan already stated, the HDF5 format is a very good choice to
write out large datasets.
I usually write the HDF5 files directly from my simulation codes and
generate a XDMF file afterwards.
The actual XDMF file contains just the meta data in XML format [1] and
this can be
I posted some XDMF examples earlier on the mailing-list, see e.g. the
attachments in these two mails:
http://public.kitware.com/pipermail/paraview/2015-March/033566.html
http://public.kitware.com/pipermail/paraview/2015-March/033568.html
-Armin
On 06/06/2015 04:42 PM, Chris Richardson wrote:
Hi Noah,
I don't see the specific link error message in your email, but it seems
possible it could be related to your graphics environment. We often have
to compile ParaView on amazon EC2 instances when setting up ParaViewWeb,
and some of the guides for that may end up being useful to you,
