Dear All
I am trying to visualise a series of VTK files using pvbatch and I get an error.
I write VTK files with a header as ascii, and then data as a 32 bit int binary.
I can visualise individual files. As there are many files, I would like to
automate this process. To do so, I produce a pvsm
I am having problems using pvbatch on the LANL machines. It works fine on
paraview/5.2.0, but can’t find pvbatch with paraview/5.4.0. I contacted the
consultants at LANL, and they suggested that I send this problem to you.
Any help or suggestions would be appreciated!
Thanks –
Judy White
(505)
What are the magic cmake switches, for superbuild, that are used to build a non
MPI, Mesa version of pvbatch? Where is this documented?
Thanks,
Alan
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/op
>
> FindSource("h0001.vtk").FileNames ='h%04d.vtk' % (i)
>
...
> AttributeError: 'NoneType' object has no attribute 'FileNames'
Means that FindSource("h0001.vtk") returned none.
Do a print GetSources() to see what it might be instead of "h0001.vtk".
> Can you comment?
>
> thanks
> Sanjay
>
>
Subject: Re: [Paraview] PVBatch
FindSource("h0001.vtk").FileNames ='h%04d.vtk' % (i)
...
AttributeError: 'NoneType' object has no attribute 'FileNames'
Means that FindSource("h0001.vtk") returned none.
Do a print GetSources() to see what it
Seems like pvbatch is not in the path. Can you confirm that `module load
paraview/5.4.0-osmesa` is indeed pointing to a valid PATH and that
contains a `pvbatch` executable?
Utkarsh
On Mon, Oct 30, 2017 at 8:14 PM, White, Judy wrote:
> I am having problems using pvbatch on the LANL machines. I
Alan,
pvbatch and pvpython are both built as long as PARAVIEW_ENABLE_PYTHON is
turned ON in its CMake.
So for the superbuild, it is just requires to enable Python.
For Mesa, you are supposed to enable Mesa (only supported on Linux for
sure).
To summarize:
$ cmake -DENABLE_python=ON -DENABLE_mpi
On Sun, Nov 12, 2017 at 22:42:29 +, Scott, W Alan wrote:
> What are the magic cmake switches, for superbuild, that are used to
> build a non MPI, Mesa version of pvbatch? Where is this documented?
pvpython is the non-MPI version of pvbatch. The superbuild docs could
probably be improved here.
Is there a way to set the default view to include all the data in batch
mode? I can get this to work by calling Render() before writing an image,
but I imagine there is a direct way to do this (perhaps with vtkCamera??).
Thanks
___
Powered by www.kitware
Hi folks
when running pvbatch on time-dependent data and on many processors, the
output becomes very verbatim since every proc writes messages similar to
vtkCutter : [...] x 100 million times
I end up with files of millions of lines which I do not read. I just
look at the movies...
Is t
hi!
I recently installed paraview 3.12 with offscreen mesa on a SGI cluster
with intel compilers and SGI MPT. Using the same version of paraview on my
local computer I recorded a script in the qt version using python trace. I
was able to execute the same script just fine on the cluster on a simi
Hello,
I try to use paraview 3.98 (Linux 64b, binary package) in batch mode with
pvbatch (or pvpython) to load a .pvsm file, render it and write a png image.
The problem is that the png image does not match the expected one. Rotation and
zoom are not applied. In the render window, the image app
This script:
from paraview.simple import *
#Connect()
reader=ImageReader(FilePrefix="z.raw")
reader.DataByteOrder=1
reader.DataExtent=[1,40,1,40,1,40]
reader.DataScalarType=6
view = GetActiveView()
if not view:
view = CreateRenderView()
view.ViewSize=[600,600]
Show()
dp = GetDisplayProperties(
Hello,
I need to load a heavy pvsm state with pvbatch and render multiple
output views for my regression tests. The python script which I use is
quite straightforward:
import paraview.simple as ParaViewSimple
import os
...
ParaViewSimple.servermanager.LoadState(pvsm_file)
for view in ParaViewSimp
Burlen,
How are you setting the view size in your python script for pvbatch?
Utkarsh
On Fri, Jun 22, 2012 at 4:27 PM, burlen wrote:
> Hi all,
>
> When I'm using pvbatch the rendering gets "clipped" (see attached images)
> when I set the view size to values greater than ~1024 in either direction
cc'ing list
On 06/23/2012 01:38 PM, Burlen Loring wrote:
hi Utkarsh, i'm setting as follows:
view = GetRenderView()
view.ViewSize = [width, height]
On Jun 23, 2012 6:35 AM, "Utkarsh Ayachit"
mailto:utkarsh.ayac...@kitware.com>> wrote:
Burlen,
How are you setting the view size in y
Thanks Utkarsh,
I'm using 3.14.1 now but this also happens with 3.10.0. Setting the
window position didn't help.
Burlen
On 06/24/2012 06:13 AM, Utkarsh Ayachit wrote:
Burlen,
This is with 3.14 or greater right?
Another thing to try is setting teh window position (maybe it's being
shown up
Is it at all possible to view the batch render windows on the
processes? I am not sure, but maybe looking at the actual size/pos of
the windows can provide some clues. Theoretically, I don't see why
there should be any difference between pvbatch and pvserver (which I
assume is what you mean by "in
unfortunately I'm running this on a vis cluster, I don't see the
windows. I guess I can move one slice of the dataset to my workstation
and see if the issue remains...
On 06/25/2012 04:36 PM, Utkarsh Ayachit wrote:
Is it at all possible to view the batch render windows on the
processes? I am
Sorry I don't have any insight. The 1024 limit sounds very fishy. In
the end, it has to be something with X/OpenGL context or something
like that, but what is confusing is that it works with pvserver
(remote-rendering, right?).
Utkarsh
On Tue, Jun 26, 2012 at 10:40 AM, Burlen Loring wrote:
> unf
O another thing, try turning off
"UseOffscreenRenderingForScreenshots" property on the view.
> view.UseOffscreenRenderingForScreenshots = 0
That's one difference between the client-server and pvbatch workflows.
Utkarsh
On Tue, Jun 26, 2012 at 10:40 AM, Utkarsh Ayachit
wrote:
> Sorry I don't ha
No luck there. I have had it set to 0 all along, but setting to 1
doesn't help. I initially suspected the xorg config, but xrandr command
confirms that the display supports the higher resolutions. Yes, it works
with pvserver remote rendering.
On 06/26/2012 07:41 AM, Utkarsh Ayachit wrote:
O a
Indeed use:
servermanager.ToggleProgressPrinting()
On Thu, Apr 30, 2009 at 4:08 PM, Jean Favre wrote:
> Hi folks
>
> when running pvbatch on time-dependent data and on many processors, the
> output becomes very verbatim since every proc writes messages similar to
>
> vtkCutter : [...] x 100
Good Morning,
I am currently having issues with paraview-3.8.0 and paraview-3.9.0 when
trying to use pvbatch and offscreen rendering. When I run with my
DISPLAY variable set, I don't have any issues, when the DISPLAY variable
is not set it fails with the "cannot connect to X server error". I h
Hi all,
I have written a python-script to interpolate data from one geometry to
another and save the result. Running it in serial works fine with pvbatch.
In parallel I have no working writer so far. I tried it with vtk, pvd
(mpi errors) and ensight (data written half, no blocks found). Is there
s
Hi Ganesh,
Sig 9 usually means your job was killed by the system. Is it possible
that you have exhausted the available ram or hit some artificial limit
that is imposed by your batch system?
Burlen
On 08/08/2012 01:15 PM, Ganesh Vijayakumar wrote:
hi!
I recently installed paraview 3.12 wi
On Wed, Aug 8, 2012 at 5:02 PM, Burlen Loring wrote:
> **
> Hi Ganesh,
>
> Sig 9 usually means your job was killed by the system. Is it possible that
> you have exhausted the available ram or hit some artificial limit that is
> imposed by your batch system?
>
>
I can't think of any right away. Th
assuming that you've already examined all the output, and there's no
other info, you could do a couple of things: put some print statements
in your python script to see how far it makes it. Also you could use MPT
specific environment variables that tell mpt to print a stack trace, see
man mpi.
On Wed, Aug 8, 2012 at 5:25 PM, Burlen Loring wrote:
> **
> assuming that you've already examined all the output, and there's no other
> info, you could do a couple of things: put some print statements in your
> python script to see how far it makes it. Also you could use MPT specific
> environme
On Thu, Aug 9, 2012 at 10:47 AM, Ganesh Vijayakumar
wrote:
>
snip
> But in the meanwhile can I force a debug compilation? How can I do that?
> Just add "-g" to CMAKE_C_FLAGS and CMAKE_CXX_FLAGS?
CMAKE_BUILD_TYPE = Debug
___
Powered by www.kitware.com
this sounds more and more external to pv. For example if you compiled
your program with one version of mpi but tried to run it with another,
you'd very likely see exactly what you are seeing here. A few of things
you could look at to boost your confidence: "module list", "which
mpirun", "echo $
attached an example of how we configure the environment and launch
pvbatch on nautilus sgi uv 1000.
On 08/09/2012 09:20 AM, Burlen Loring wrote:
this sounds more and more external to pv. For example if you compiled
your program with one version of mpi but tried to run it with another,
you'd ve
Try calling the following at the start of the script:
from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()
Utkarsh
On Tue, Jan 15, 2013 at 4:57 PM, Glockner Stéphane
wrote:
> Hello,
>
> I try to use paraview 3.98 (Linux 64b, binary package) in batch mode with
> pvbatc
Hi!
I'm trying to get a current process id from within a pvbatch script.
I found a solution here
(http://www.paraview.org/pipermail/paraview/2010-April/016759.html)
but this trick doesn't work for me.
I wrote a very simple script:
from paraview.simple import *
sm = servermanager
print 'parts = ',
What is the version of ParaView on the "other" Linux box? How are you
running the script? Is the mpi used to build and run the executable
same?
Utkarsh
On Mon, Mar 18, 2013 at 7:28 PM, Anton Shterenlikht wrote:
> This script:
>
> from paraview.simple import *
> #Connect()
> reader=ImageReader(Fi
From utkarsh.ayac...@kitware.com Tue Mar 19 03:30:31 2013
What is the version of ParaView on the "other" Linux box?
3.12:
mexas@hector-xe6-8:~> pvpython
Python 2.7.2 (default, Nov 9 2011, 15:37:53)
[GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)] on linux2
Type "help", "copyr
From me...@bristol.ac.uk Tue Mar 19 09:10:58 2013
From utkarsh.ayac...@kitware.com Tue Mar 19 03:30:31 2013
What is the version of ParaView on the "other" Linux box?
3.12:
mexas@hector-xe6-8:~> pvpython
Python 2.7.2 (default, Nov
Maxim,
Can you try passing `--use-offscreen-rendering` flag to pvbatch. Does
that help? I am not sure how you're getting incorrect sizes with
osmesa too, but let's focus of the X error to begin with.
Utkarsh
On Mon, Jul 3, 2017 at 11:36 AM, Maxim Torgonskiy wrote:
> Hello,
>
> I need to load a
I am attempting to setup a pvbatch process for a large number of exodus files
using WriteAnimation for images. However, I appear to have a memory leak and
the number of images continues to grow. I've been trying to delete all the
variables to find an offending variable that is carrying over time
Hi All,
i'm writing here because i would understand better the functionality of
pvbatch in Paraview.
At moment i'm able to run Paraview in batch launching a python script,
and it works good.
Here the line command i launch:
_//software/Paraview/ParaView-3.12.0-Linux-x86_64/lib/paraview-3.12/
That sounds fishy, let me take a look. I'll get back to you.
Utkarsh
On Wed, Apr 7, 2010 at 8:06 AM, Carrie E. Spear (Cont, CISD/ARL)
wrote:
> Good Morning,
>
> I am currently having issues with paraview-3.8.0 and paraview-3.9.0 when
> trying to use pvbatch and offscreen rendering. When I run wi
Carrie,
I just tried it with CVS ParaView and I could not reproduce it. Can
you reproduce this when running on a single node? Try running ldd on
pvbatch, is it getting the right OpenGL libraries?
Utkarsh
On Wed, Apr 7, 2010 at 9:40 AM, Utkarsh Ayachit
wrote:
> That sounds fishy, let me take a l
Utkarsh,
When I do an ldd pvbatch appears to be using the correct libraries GL
libraries (I am building agains mesa-7.0.4, could it be that my version
of mesa is too old). I ran the following test:
bash-3.2$ echo $DISPLAY
:0.0
bash-3.2$ unset DISPLAY
bash-3.2$ echo $DISPLAY
bash-3.2$ mpirun
That's exactly what I am doing as well ("unset DISPLAY" that is), and
seems to work well. Is this a debug build. Can you track down where
the error message is coming from? I am not sure where this error
message is coming from since it doesn't look like a paraview message
and a quick "grep" didn't
So, we're really stumped.
- Paraview (pvbatch) 3.6.2 works exactly as we'd expect.
- pvbatch 3.8.0/3.9.0 fail with the "can't open display" error. If we
set a display variable, pvbatch works, but that's not really a solution.
- All three are using the same exact
elini wrote:
> So, we're really stumped.
>
> - Paraview (pvbatch) 3.6.2 works exactly as we'd expect.
> - pvbatch 3.8.0/3.9.0 fail with the "can't open display" error. If we set a
> display variable, pvbatch works, but that's not really a solution.
>
ni
> wrote:
>> So, we're really stumped.
>>
>> - Paraview (pvbatch) 3.6.2 works exactly as we'd expect.
>> - pvbatch 3.8.0/3.9.0 fail with the "can't open display" error. If we set a
>> display variable, pvbatch works, but that's not re
>> PARAVIEW_BUILD_QT_GUI ON? That's possible the only difference between
>> your build and mine. I am going to turn on PARAVIEW_BUILD_QT_GUI and
>> try to reproduce the problem.
>>
>> Utkarsh
>>
>>
>>
>>
>>
>> On Wed, Apr 7, 2010
> >> Utkarsh
> >>
> >>
> >>
> >>
> >>
> >> On Wed, Apr 7, 2010 at 2:06 PM, Rick Angelini <
> rick.angel...@us.army.mil> wrote:
> >>> So, we're really stumped.
> >>>
> >>> - Paraview (pvba
e:
So, we're really stumped.
- Paraview (pvbatch) 3.6.2 works exactly as we'd expect.
- pvbatch 3.8.0/3.9.0 fail with the "can't open display" error. If we set a
display variable, pvbatch works, but that's not really a solution.
- All three are using the same
Hi,
I try to use pvbatch to render a whole bunch of screenshots using a
script. pvbatch works fine if I simply create a sphere and write that
image to disk.
But loading a predefined pipeline using LoadState('pstate.pvsm') which
includes a datset in XDMF file format fails.
Any idea what I am doin
Hi anybody,
I am trying to run a very simple python script:
from paraview.simple import *
servermanager.LoadState("state.pvsm")
view = servermanager.GetRenderView()
view.StillRender()
image="aux.png"
view.WriteImage(image,"vtkPNGWriter",1)
using pvbatch:
mpirun -np 8 pvbatch script.py
to obtai
Is there anyway to turn this off?
Regards,
Joseph David Borġ
http://www.jdborg.com
___
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 th
Hi Gena,
You'll need to run pvbatch with the --symmetric option. Otherwise process 0
is the only one that reads the script and tells all of the other processes
what to do.
Andy
On Mon, Feb 4, 2013 at 9:35 AM, Gena Bug wrote:
> Hi!
>
> I'm trying to get a current process id from within a pvbatc
Hello,
I've compiled Paraview 5.1 with multithreaded mpi and ospray (with OpenMP)
support using the next modules:
1) gcc/4.8.25) xalt/0.5.3 9) szip/2.1
13) boost/1.61.0
2) openmpi/1.8.4_mtm6) DefApps 10) hdf5/1.8.11
14) libtool/2.4.2
3) PE-gnu/4.8.2-1
This sounds like the mesa issue I was having. Does it work if you add this
to the start pdf your script?
# turn off display lists
g = servermanager.misc.GlobalMapperProperties()
g.GlobalImmediateModeRendering = 1
Regards,
Paul
On 24 Jan 2012 19:07, "Houskamp, Joshua R CTR (US)" <
joshua.r.houska
Hi Daniele,
can you share what your script look like?
Seb
On Thu, Jun 5, 2014 at 1:56 AM, Daniele Obiso <
daniele.ob...@phitecingegneria.it> wrote:
> Hi All,
>
> i'm writing here because i would understand better the functionality of
> pvbatch in Paraview.
>
> At moment i'm able to run Parav
Hi Sebastien,
thanks for the reply!
The script is about creating slice and sweep animation. But it's working
fine, i think there is no problem in it.
Do you need the script to understand something about the parallelization?
Let me know!
Daniele
On 06/05/2014 04:17 PM, Sebastien Jourdain w
Is it using the VTK classes or the paraview Proxy?
Moreover, the reader/source is responsible to distribute the data to
properly handle parallelism.
If it does not, then you right, everything will happen on the root node.
Hense a quick look at the script can help us determine which part need to
c
Hi Sebastien,
here you can find the main parts of the script.
/try: paraview.simple//
//except: from paraview.simple import *//
//paraview.simple._DisableFirstRenderC
Ok, so you are correctly using everything.
The question is now on the *OpenFOAMReader and if it properly use MPI to
read and distribute the data.*
*Which unfortunately I don't know.*
*If you want to force a redistribution of your data across your nodes, you
can use the D3 filter just after your re
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.
R&D
Jens
Here's an updated script:
=
from paraview.simple import *
# reload state
servermanager.LoadState('/tmp/state.pvsm')
view = GetRenderViews()[0]
## render png
view.ResetCamera()
view.StillRender()
view.WriteImage( "/tmp/Test1.png", "vtkPNGWriter" )
==
The pr
Hi Utkarsh,
thank you for that hint.
I can see the bounding box now ...
But somehow it does not refresh the whole pipeline.
What do I have to do, that all parts of pipeline are updated before I
write the image. Any idea?
Greetings
Jens
Utkarsh Ayachit schrieb:
> Jens
>
> Here's an updated scri
Jens,
Is the non-refreshed part of the pipeline visible in the view?
Utkarsh
On Fri, May 28, 2010 at 3:23 AM, Jens wrote:
> Hi Utkarsh,
>
> thank you for that hint.
> I can see the bounding box now ...
>
> But somehow it does not refresh the whole pipeline.
> What do I have to do, that all part
Hi Utkarsh,
if I reload the state in paraview-gui it does not refresh ether.
I have to walk through the pipeline (bottom to top) and call "Apply".
Greetings
Jens
Utkarsh Ayachit schrieb:
> Jens,
>
> Is the non-refreshed part of the pipeline visible in the view?
>
> Utkarsh
>
> On Fri, May 28
Jens,
It would be great if you could post a state to reproduce this issue.
Utkarsh
On Fri, May 28, 2010 at 1:31 PM, Jens wrote:
> Hi Utkarsh,
>
> if I reload the state in paraview-gui it does not refresh ether.
> I have to walk through the pipeline (bottom to top) and call "Apply".
>
> Greeting
Hi Utkarsh,
The problem is related to bug 10775
(http://public.kitware.com/Bug/view.php?id=10775) and hyperslabs in XDMF.
I attached an example which should reproduce the problems I discribe now:
hyperslab on its own:
pv 3.6.2: loading test.xmf->dataset u_without_hyperslab works fine
pv 3.8.0: lo
Jens,
I'd recommend not relying on Xdmf state loading or Python API in 3.6
(or before) since that was broken. It has since been fixed for 3.8. I
have requested the ARL/Xdmf folks to take a look at the hyperslab
issue. I'll keep you posted. Once that segfault is fixed, state
loading should not be a
Dear Ken, and dear Utkarsh,
I sent an email for the bug fix. But Kenneth applied it to different location.
Instead of line 148 (which is in UpdateInformationFunction), it was
applied to 172 (which is in UpdateInformationUniform).
So I would like to inform you this again. I believe this issue is a
Hi Ken, Kenji and Jens,
I pulled the fix to UpdateInformationUniform that Ken committed into
ParaView a few weeks ago. I just now also applied the fix to
UpdateInformationFunction and pulled the change into ParaView as well.
I apologize for some of the confusion. Since the transition to Git, Xdmf
Hi,
Miguel Fosas send an other patch assigne to the related bug
http://www.itk.org/Bug/view.php?id=10775#c20932
Instead of "XdmfConstString Value=0;", he moves the variable in the
case-section.
Greetings
Jens
--- XdmfDataItem.cxx2010-06-07 18:11:50.954700131 +0200
+++ XdmfDataItem-patched.
Hi All, I have applied the new fix to Xdmf in
commit cd802a3e4c0c13b4697518363535562f758a6d48 and updated ParaView to
point to the latest Xdmf. Let me know if there are more problems.
On Mon, Jun 14, 2010 at 9:13 AM, Jens wrote:
> Hi,
>
> Miguel Fosas send an other patch assigne to the related b
i am having difficulty with pvbatch - compiled with Mesa 7.6 - running in
parallel and hanging after the first WriteImage in my python scripts.
I have tested several compilations on different clusters, several MPI (mvapich
and openmpi) and still cannot make this work. It writes the first image
Please, is it possible for someone to try to reproduce the behavior of
which I am talking about with the example files submitted here:
http://www.paraview.org/Bug/view.php?id=10702 ?
If I try to open for example the file unsteady_output_probe_1.xdmf
passing 1, 2, 4, 8 or 16 cpu's to mpirun when st
Hi Jorge,
Can you please provide the CMakeCache.txt and the system information of the
computer that has this problem?
On Wed, Mar 9, 2011 at 11:44 AM, Jorge Chiva Segura wrote:
> Please, is it possible for someone to try to reproduce the behavior of
> which I am talking about with the example fi
Only way is to recompile PAraView with OSMesa
(http://paraview.org/Wiki/ParaView_And_Mesa_3D)
Utkarsh
On Fri, Aug 24, 2012 at 12:08 PM, Joe Borġ wrote:
> Is there anyway to turn this off?
>
>
> Regards,
> Joseph David Borġ
> http://www.jdborg.com
>
> _
Hello,
I'm trying to parallelize a process using pvbatch and MPI, with
MultiBlock data set; thus using the vtk composite pipeline.
I made a sample python program that is representative of what I have to do :
--
Hi,
I have a custom reader plugin which has multiple outputs. From the GUI I can
load up a data file, and can see the two outputs in the pipeline viewer. I can
hide or show them independently, choose different representations, apply
different filters, etc. I've saved a python state file, and
Ben,
I am not able to reproduce this locally. Can you file an issue to help me
keep track of it on ParaView's new gitlab issue tracker?
https://gitlab.kitware.com/paraview/paraview/issues
David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-49
Sure Dave,
I forget to mention I found no problems when running paraview GUI and
ospray renderer in an interactive session in the cluster.
Regards,
On Wed, Sep 21, 2016 at 2:42 PM, David E DeMarle
wrote:
> Ben,
>
> I am not able to reproduce this locally. Can you file an issue to help me
> ke
I am trying to volume render an unstructured grid of points using pvbatch
but I am getting an error:
ERROR: In
/home/user/Programs/ParaView-3.11.1-git/ParaView/VTK/VolumeRendering/vtkUnstructuredGridVolumeRayCastMapper.cxx,
line 211
vtkUnstructuredGridVolumeRayCastMapper (0x2473a40): Can't use the
I omitted that line before because I was getting the following error.
Readding it gives this error:
Traceback (most recent call last):
File "/home/user/DNS/volume.py", line 40, in
DataRepresentation2.ColorArrayName = 'volume_scalars'
File
"/home/user/Programs/ParaView-3.11.1-git/bin/Utilit
I've recorded this python script with PV Trace.
However, the resulting animation window is small.
What do I need to edit to make the window, e.g. 1000x1000 pixels?
Thanks
Anton
# use defined variables, no indent allowed, start at col 1
infile = "z.xdmf" # name of XDMF file
picfile = "z.png"
Hi everybody,
I am trying to run pvbatch in parallel to render an animation, with a very
easy script that looks like
* import sys
* from paraview.simple import *
*
* # read pvsm file from command line and load it
* stateFile = sys.argv[1]
* simulation = state
Hi all,
I have a pvbatch script from which I would like to get the output data
set of the second output port of a filter which has 2 output ports. How
can I do this?
--
Burlen Loring
Kitware, Inc.
R&D Engineer
28 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-371-3971 x137
__
Hi:
I'm just starting to try to learn the python scripting interface to
ParaView 3.6.1, taking bits and pieces from various tutorial slides
scattered over the web. I've managed to put together something that
works fine in the python shell on the client side, but when I try using
the same sc
Hey Jean,
I am getting the same behavior on my Mac OS X 10.6 compiled with OpenMPI (but
no OSMesa). I can run scripts like yours from the ParaView Python shell when
connected to a four-process pvserver just fine, and it works from the same
build of pvbatch run in serial (without mpirun), but wh
I can repeat this. Believe it or not, WriteImage does an mpi broadcast. In
the 3.8 release and some time afterward it worked fine, but it doesn't seem
to work now.
Pat
On Thu, Aug 19, 2010 at 5:09 PM, Eric E. Monson wrote:
> Hey Jean,
>
> I am getting the same behavior on my Mac OS X 10.6 com
I think it may have been buggy ever since the mpi broadcast was added, but a
month and a half ago Utkarsh added a debugging call to Barrier to expose to
help expose these issues. I'll fix.
Pat
On Thu, Aug 19, 2010 at 5:12 PM, pat marion wrote:
> I can repeat this. Believe it or not, WriteImag
In the meantime, you can fix it by replacing the body of
vtkSMUtilities::SaveImageOnProcessZero with:
return SaveImage(image, filename, writerName);
Pat
On Thu, Aug 19, 2010 at 5:22 PM, pat marion wrote:
> I think it may have been buggy ever since the mpi broadcast was added, but
> a month a
Attached is a patch that fixes the problem. I'm cc'ing Ken because he is
the one who originally introduced the mpi broadcast in commit e9096f4 (then
I moved the routine to vtkSMUtilities in commit 514322c) I want to make
sure this new patch continues to work for his use case.
Pat
On Thu, Aug 19
This show be fixed now.
commit e13270b7468f7fcdea21a7e350c3ce65a9cde872
Author: Utkarsh Ayachit
Date: Mon Oct 18 10:11:34 2010 -0400
BUG #11327. Fixed freeze after WriteImage in parallel pvbatch.
vtkSMUtilities::SaveImageOnProcessZero has a broadcast to ensure that all
processes h
Just to make sure, your ParaView is built with MPI support enabled,
right? XMLMultiBlockDataReader does distribute the blocks to read
among the processes. Try apply a "ProcessIdScalars" filter in the
middle and then look at the ProcessId assigned to the blocks in the
data. They should show how the
Any idea on this problem ?
Thanks,
Yves Rogez
*IPAG*
/Institut de Planétologie et d'Astrophysique de Grenoble /
Bat D de Physique - BP. 53 - 38041 Grenoble - FRANCE
tel : +33 (0)4 76 63 52 80
lab : +33 (0)4 76 63 52 89
Le 15/01/2013 17:25, Yves Rogez a écrit :
And also the output file for MPI
Yves,
1. I don't see the oddity with the block number and BlockID when
running in parallel, as you describe. For me, the BlockID in indeed
Index for block + 1 whether I run in parlalel or not.
2. Running your python script as a single process, I get 1:18 minutes,
while in parallel (2 procs), I get
Hi,
I found a solution to this problem. I had to insert an UpdatePipeline()
call just before the writer update :
/myLastFilter.UpdatePipeline()
writer.UpdatePipeline()/
This is a strange behavior. Maybe due to MPICH2 usage ? I don't know...
However it runs well like that.
Thanks for
Actually this was bug that fix just a couple of days ago:
http://paraview.org/Bug/view.php?id=13850
It should be fixed in the upcoming release (3.98.2).
Utkarsh
On Mon, Feb 4, 2013 at 4:05 PM, Yves Rogez
wrote:
> Hi,
>
> I found a solution to this problem. I had to insert an UpdatePipeline() cal
Joe,
Something like following should do the trick:
from paraview.simple import *
> port = servermanager.OutputPort(reader, 1)
> Show(port)
On Mon, Feb 10, 2014 at 4:37 PM, Insley, Joseph A. wrote:
> Hi,
>
> I have a custom reader plugin which has multiple outputs. From the GUI I can
>
Try adding:
DataRepresentation2.ColorArrayName = 'volume_scalars'
Utkarsh
On Wed, Aug 24, 2011 at 7:02 PM, Jesus Pulido wrote:
> I am trying to volume render an unstructured grid of points using pvbatch
> but I am getting an error:
>
> ERROR: In
> /home/user/Programs/ParaView-3.11.1-git/ParaVie
1 - 100 of 145 matches
Mail list logo
