Dear paraviewers,
I am trying render in parallel a scene + text. Unfortunately: the
TextSourceRepresentation of the text does not work in parallel (is works in
serial)
If I do
sm=servermanager
sm.Connect()
RenderView1 = sm.CreateRenderView()
t=sm.sources.Text(Text=HELLO)
Not sure about 3.8.1, but it's definitely fixed in the development
version and will be for the upcoming release 3.10.0. The release
candidate binaries should be available for download in the next few
days.
Utkarsh
On Mon, Jan 24, 2011 at 9:43 AM, Eelco van Vliet eelc...@gmail.com wrote:
Dear
Hi,
I just found this page and wonder, if this will be a new approach for
python scripting:
http://www.paraview.org/ParaView3/index.php/Visualization_Script_Examples#Paraview_Python_Script_with_PVFWrap
In addition, there are comments about the VisIt way... do you plan
something like this!?
No. PVFWrap was a prototype interface that has been substantially improved to
become the current paraview.simple. Most people use the python trace to
establish their initial python scripts and then modify them, but if you know
the names of the filters and only want to specify changes from
That page is ancient.
I think PVFWrap was the predecessor to paraview.simple which since 3.6
is the standard way to do ParaView python scripting (see python
trace).
The comments about paraview state files being too verbose have been
addressed since then as well.
Or did you mean something else?
Hello,
thanks for the info!
Is my impression correct, that in version 3.8.1 the python trace state
process is not as 'complete' as using the old state file approach?
For my case setup, e.g. there is not always the correct camera position
and the correct slices...
Best Regards!
Fabian
On
Hi Fabian,
Regarding your issue of python trace state not replicating your paraview
state exactly, I believe both issues you quote (camera position and cut
filter's slice property) have been addressed in the latest version of
paraview. If not, can you list the steps required to repeat the
You are using 3.8.0, not 3.8.1. If you use 3.8.1 to generate the trace
script you will not receive these errors.
Your script can also be fixed by hand- editing test_trace.py and move the
lines at the very bottom modifying Slice1, Slice2 and Slice3. Moving the
lines up so they appear after
Utkarsh,
Thanks for your quick reply. I am running an own build paraview 3.8.1
version (with MESA and mpi, so pvbatch only). So the problem has been solved
in the git version. Is the source release of a stable 3.10 version also to
be expected within a few date ? Then I would wait for that release
Hi Mike,
There is now an advanced option PARAVIEW_FIXUP_BUNDLE_SEARCH_PATHS that you
can append directories for fixup bundle to search.
On Thu, Dec 30, 2010 at 3:28 PM, Michael Jackson
mike.jack...@bluequartz.net wrote:
#2 I think would add the most flexibility as I have other libraries that
Almost forgot about this.
PARAVIEW_EXTRA_INSTALL_RULES_FILE now can be set to multiple semicolon
separated files that will be looped over and included. Please let me know if
you experience any issues.
On Tue, Nov 30, 2010 at 9:55 AM, Dave Partyka dave.part...@kitware.comwrote:
Can do!
On
11 matches
Mail list logo
