Re: [Paraview] pvbatch vs. pvpython

2012-08-09 Thread Ganesh Vijayakumar
On Wed, Aug 8, 2012 at 5:25 PM, Burlen Loring blor...@lbl.gov 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

Re: [Paraview] pvbatch vs. pvpython

2012-08-09 Thread David E DeMarle
On Thu, Aug 9, 2012 at 10:47 AM, Ganesh Vijayakumar ganesh.i...@gmail.com 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

Re: [Paraview] pvbatch vs. pvpython

2012-08-09 Thread Burlen Loring
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

Re: [Paraview] pvbatch vs. pvpython

2012-08-09 Thread Burlen Loring
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

[Paraview] pvbatch vs. pvpython

2012-08-08 Thread Ganesh Vijayakumar
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

Re: [Paraview] pvbatch vs. pvpython

2012-08-08 Thread Burlen Loring
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

Re: [Paraview] pvbatch vs. pvpython

2012-08-08 Thread Ganesh Vijayakumar
On Wed, Aug 8, 2012 at 5:02 PM, Burlen Loring blor...@lbl.gov 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

Re: [Paraview] pvbatch vs. pvpython

2012-08-08 Thread Burlen Loring
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.