dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #15666
Re: MPI problem with python demos
On Fri, Sep 25, 2009 at 11:21 AM, Ola Skavhaug <skavhaug@xxxxxxxxx> wrote:
> The problem is 1.3.37. Pitty since karmic uses it. Easy to build new
> swig, though.
I think Karmic still has 1.3.36. If you have 1.3.37 it is probably my
package that I built for Hardy. I would remove it and install the
original one from the Ubuntu repository.
Johannes
> 2009/9/25, Johannes Ring <johannr@xxxxxxxxx>:
>> On Fri, Sep 25, 2009 at 9:18 AM, Anders Logg <logg@xxxxxxxxx> wrote:
>>> On Fri, Sep 25, 2009 at 09:15:57AM +0200, Johannes Ring wrote:
>>>> On Fri, Sep 25, 2009 at 9:09 AM, Johan Hake <hake@xxxxxxxxx> wrote:
>>>> > On Friday 25 September 2009 09:03:20 Harish Narayanan wrote:
>>>> >> Has anyone seen the following problem when trying to run python demos?
>>>> >> The C++ demos work, both in serial and in parallel. When I try to run
>>>> >> python demos (either in serial or in parallel), I receive the
>>>> >> following
>>>> >> (on a hardy machine):
>>>> >>
>>>> >>
>>>> >> $ python demo.py
>>>> >>
>>>> >> Traceback (most recent call last):
>>>> >> File "demo.py", line 16, in <module>
>>>> >> V = VectorFunctionSpace(mesh, "CG", 1)
>>>> >> File
>>>> >> "/home/harish/Work/FEniCS/build/lib/python2.5/site-packages/dolfin/function
>>>> >> space.py", line 271, in __init__
>>>> >> spaces = dim*[FunctionSpace(mesh, family, degree, restriction)]
>>>> >> File
>>>> >> "/home/harish/Work/FEniCS/build/lib/python2.5/site-packages/dolfin/function
>>>> >> space.py", line 194, in __init__
>>>> >> FunctionSpaceBase.__init__(self, mesh, element)
>>>> >> File
>>>> >> "/home/harish/Work/FEniCS/build/lib/python2.5/site-packages/dolfin/function
>>>> >> space.py", line 43, in __init__
>>>> >> ufc_element, ufc_dofmap = jit(self._element)
>>>> >> File
>>>> >> "/home/harish/Work/FEniCS/build/lib/python2.5/site-packages/dolfin/jit.py",
>>>> >> line 43, in mpi_jit
>>>> >> if MPI.num_processes() == 1:
>>>> >> TypeError: num_processes() takes exactly 1 argument (0 given)
>>>> >
>>>> > I guess you have SWIG version 1.3.37?
>>>> >
>>>> > A regression bug was introduced in this release for static methods.
>>>> >
>>>> > You should probably upgrade your SWIG. SWIG is now at 1.3.40.
>>>> >
>>>> > Should we require SWIG version larger than 1.3.37 in our build system?
>>>> > Would
>>>> > this work for the different ubuntu packages?
>>>>
>>>> If 1.3.36 works I think we should allow that. If not, I'll have to
>>>> build SWIG packages for hardy, intrepid, jaunty, and even karmic. I
>>>> would like to avoid that :-)
>>>
>>> I have 1.3.36. Strange since I'm running on Karmic and biglue has 1.3.37.
>>
>> Bigblue runs Hardy and I made the 1.3.37 package because the 1.3.33
>> package from the Ubuntu repository was to old (we require >= 1.3.35).
>> I will update SWIG on Hardy (and bigblue) after the upcoming DOLFIN
>> release.
>>
>> Johannes
>> _______________________________________________
>> DOLFIN-dev mailing list
>> DOLFIN-dev@xxxxxxxxxx
>> http://www.fenics.org/mailman/listinfo/dolfin-dev
>>
>
> --
> Sendt fra min mobile enhet
>
> Ola Skavhaug
>
References