Hi Dave,
Many thanks for Your quick answer. I checked exporting the labels of selections,
where the text export works as expected (SVG attached).
For using Paraview SVG export in latex it would still be very nice to have the
same export functionality for the cube axes. Should I reopen the
Concerning the clipping of volume data when doing volume rendering is done more
precise in paraview than often necessary: even individual voxels are clipped.
With such large data this is likely not visible at all. I therefore tried to use
the vtkImplicitFunctionToImageStencil to create a
pqActiveObjects is not available on the server side. It's a construct
used by the client alone to keep track of what's active. Where is this
call being made? In a filter/reader/writer code? That's not
recommended (rather possible).
Utkarsh
On Thu, Jun 5, 2014 at 9:03 AM, Christian Andreas
On Fri, Jun 6, 2014 at 3:17 AM, Dr. Roman Grothausmann
grothausmann.ro...@mh-hannover.de wrote:
Hi Dave,
Many thanks for Your quick answer. I checked exporting the labels of
selections, where the text export works as expected (SVG attached).
For using Paraview SVG export in latex it would
Hi Praveen,
My suggestion would be to start with a build of ParaView 4.1. Build it with
MPI, Python and Catalyst enabled (Catalyst should be enabled by default but
MPI and Python need to be explicitly turned on). The Catalyst editions are
meant to be subsets of ParaView that get rid of specific
On Fri, Jun 06, 2014 at 02:18:42 -0700, Praveen Narayanan wrote:
I am examining the example code for catalyst from Andy Bauer’s git repository
(https://github.com/acbauer/CatalystExampleCode).
I am trying to learn about the catalyst workflow before using it in my own in
situ examples.
Thanks Andy. It is a bit of a pain to see the examples fail to run after the
long paraview build process.
Can’t you bundle the examples along with the paraview sources?
I will keep posted.
Thanks
Praveen.
From: Andy Bauer [mailto:andy.ba...@kitware.com]
Sent: Friday, June 06, 2014 7:10 AM
To:
Hi Felipe,
The general approach would be:
- create a VTK singleton class, say vtkPxdmfSettings
- configure your settings proxy group to use this settings class as follows:
ProxyGroup name=settings
SettingsProxy name=PxdmfSettings label=Pxdmf
processes=client|dataserver|renderserver
The FOAM reader should read the data in parallel. Try changing the CaseType
property from Reconstructed (meaning OpenFOAM did the gather) to Decomposed
(meaning OpenFOAM left the data as the parallel nodes in the simulation
wrote them) case and see if that helps.
David E DeMarle
Kitware, Inc.
RD
Here's a more expanded list of steps outlining the solution David gave in case
you are not very familiar with the contour filter and animation controls in
ParaView.
1. Create the streamlines as you normally would.
2. Add a Contour filter to the streamline (third toolbar, second button from
For structured data, prefer the Extract Subset filter to the Clip
filter. Subset works in the topological space and therefore preserves the
implicitly defined geometry and topology.
Once you reduce the size to something manageable with that, (either through
subrange or striding) then the filters
Ken and Jean, excellent idea! I liked it so much that I wrote it up in the SNL
ParaView tutorials, tips and tricks page. It is located here:
http://www.paraview.org/Wiki/Advanced_Tips_and_Tricks
Alan
From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Moreland,
Kenneth
Sent:
We are planning to develop custom application using our own GUI.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
I got a 'working' build as suggested by turning on the mpi and python flags
from within the paraview 4.1 source distribution - these were not turned on in
my earlier builds. I was able to play with the examples so that they dumped
data files. Turning on the 'Connect to Catalyst' button in the
14 matches
Mail list logo
