dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Wed, Jun 01, 2011 at 03:52:43PM -0000, Johan Hake wrote:
> I have long thought of creating a C++ wrapper of Viper. It should be possible,
> with passing just NumPy arrays of coordinates, connectivities and data, from
> DOLFIN to Viper. But I have never got my but around to code it up. To put it
> clear, it is not one of my highest priorities...

I think a rewrite of Viper would be a better option...

> Have you tried letting Viper read parallel vtk files, or would it still be a
> problem to call Viper using system?

Any call to Viper (even from just one process) fails.

> Does xterm work on Mac, and Linux, but not on Windos? Maybe you can "fix" it
> using xterm and then dissable parallel C++ plotting on Windows?

Xterm won't help here... :-) What I meant was that it's perfectly
possible to do

  system("xterm")

in parallel (even when MPI is initialized). The problem is that will
only fire up a bunch of Xterms, no plots... :-P

--
Anders

> Johan
>
>
> On Wednesday June 1 2011 07:59:28 Anders Logg wrote:
> > I tried to work around this bug but without luck. For some reason, the
> > combination of MPI, VTK (Viper) and system() leads to errors like
> >
> > routed:binomial: Connection to lifeline [[27229,0],0] lost
> >
> > The error does not show up if the call to viper is replaced by a call to
> > for example xterm.
> >
> > The error does not show up if MPI::Init() is not called.
> >
> >
> > ** Changed in: dolfin
> >        Status: Confirmed => Won't Fix
>

-- 
You received this bug notification because you are a member of DOLFIN
Team, which is subscribed to DOLFIN.
https://bugs.launchpad.net/bugs/427534

Title:
  Viper plotting does not work in parallel from C++

Status in DOLFIN:
  Won't Fix

Bug description:
  Plotting fails in parallel. To reproduce this bug, uncomment the call
  to not_working_in_parallel in plot.cpp and run the Poisson demo with

    mpirun -n 2 ./demo

  Exits with a message about a lost lifeline.