I finally tried to follow up on this, and since I am downloading binary
releases, there is no such directory for me of course.
Where can I find a reference or generate one for the python interface? How do
people learn this stuff or explore it?
-- Rich
On Oct 30, 2013, at 11:36 PM, Sebastien
I think Utkarsh pushed some stuff to generate some documentation related to
that.
This should start showing up in couple of days here:
http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/index.html
Seb
On Fri, Nov 1, 2013 at 10:15 AM, Cook, Rich coo...@llnl.gov wrote:
I finally tried
Thanks, I'll check back next week at that URL to see what shows up.
I do have working what I needed for now. Time to xplore blender scripting
-- Rich
On Nov 1, 2013, at 1:57 PM, Sebastien Jourdain
sebastien.jourd...@kitware.commailto:sebastien.jourd...@kitware.com wrote:
I think Utkarsh pushed
Hi Rich,
Maybe the active view is not the one that has your rendering.
You may need to call SetView(RenderView2).
Seb
On Wed, Oct 30, 2013 at 6:41 PM, Cook, Rich coo...@llnl.gov wrote:
Arrgh!
I tried the following and the resulting file did not contain my isosurface
as created by the
All the Proxy/Python informations are stored in the XML files under
src/ParaViewCore/ServerManager/SMApplication/Resources/*
That's the way I do it... ;-)
Seb
On Thu, Oct 31, 2013 at 12:33 AM, Sebastien Jourdain
sebastien.jourd...@kitware.com wrote:
Hi Rich,
Maybe the active view is not
Good tip
On Oct 30, 2013, at 11:36 PM, Sebastien Jourdain
sebastien.jourd...@kitware.commailto:sebastien.jourd...@kitware.com
wrote:
All the Proxy/Python informations are stored in the XML files under
src/ParaViewCore/ServerManager/SMApplication/Resources/*
That's the way I do it... ;-)
Seb
SetView(RenderView2)
Traceback (most recent call last):
File console, line 1, in module
NameError: name 'SetView' is not defined
On Oct 30, 2013, at 11:33 PM, Sebastien Jourdain
sebastien.jourd...@kitware.commailto:sebastien.jourd...@kitware.com
wrote:
Hi Rich,
Maybe the active view is not
Oops, sorry about that.
So when I called
x3dExporter.SetView(RenderView2)
x3dExporter.Write()
the viewport turned green!
It looks like this means that the exporter's view is its output in some sense.
I need to plumb things up so the view goes into the exporter and out comes an
x3dExporter.
On
Hum I'm getting confuse.
the RenderView2 was the name of the var in your stack trace.
It is not a magic command.
Seb
On Thu, Oct 31, 2013 at 10:27 AM, Cook, Rich coo...@llnl.gov wrote:
Oops, sorry about that.
So when I called
x3dExporter.SetView(RenderView2)
x3dExporter.Write()
the
You should also have said you had a remote server that was doing remote
rendering.
This is the reason why your x3d is empty.
You need to do local rendering in order to get geometry locally so the
export will have something to export.
Seb
On Thu, Oct 31, 2013 at 3:09 PM, Cook, Rich
I recorded a script to try to understand how to export a time series of an
isosurface as .x3d files so I can muck with them using blender. But when I
look at the script, the crucial bit of exporting the .x3d did not get captured.
Is that part not scriptable? How can I go about finding out
… and immediately got the answer from google:
http://www.paraview.org/pipermail/paraview/2012-May/024921.html
However, I'm still curious as to how the person in question discovered how to
do it. Where is all the good python documentation/lore stored? The wiki
wasn't too helpful to me in
Arrgh!
I tried the following and the resulting file did not contain my isosurface as
created by the below script. What am I doing wrong here? Sorry for the
stream-of-consciousness posts here…
exporters=servermanager.createModule(exporters)
13 matches
Mail list logo
