Hi folks,
Just to update you, I have fixed the problem by using openmpi instead of
IntelMPI-4.0.1.
I am not sure what is the cause of this as IntelMPI-4.0.1 works with
ParaView-3.10.1. I think if I get time, I will try and compile 3.12 with a
new version of IntelMPI and see if that fixes it.
I know that there were some connection issues with older versions of PV
3.14.0. This problem would be in the source for 3.14.0-RC2. Give master a
try, and see if that helps. We did find the PV_CLIENT_HOST variable problem -
it is fixed in master.
Alan
From: paraview-boun...@paraview.org
Alan, Burlen
Thanks for the prompt response - I will try with the master of 3.14.0
Burlen - We don't need to do tunnelling for this cluster (we did for other
clusters), because the compute nodes of viz cluser are visible across the
network (ie I am able to ssh from a compute node on the viz
Currently / /openmpi/intel-11.1-f064-c064/openmpi-1.4.2_oobpr on our
primary cluster.
Alan
From: Rakesh Hammond [mailto:rakesh.hamm...@googlemail.com]
Sent: Monday, February 20, 2012 11:14 AM
To: Scott, W Alan
Cc: paraview@paraview.org
Subject: Re: [EXTERNAL] [Paraview]
OK, you might want to look at the command line in the qsub script though
since it doesn't make use of the environment variables. Not sure if
that's really your issue though.
I've used PV with openmpi, mvapich2, mpich2, cray mpt, and intel mpi.
Very rarely seen any interactions between pv and
