dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Sun, Apr 29, 2007 at 01:36:05PM +0200, Ola Skavhaug wrote:
> Anders Logg skrev den 29/04-2007 følgende:
> > On Sat, Apr 28, 2007 at 11:46:16PM +0200, Ola Skavhaug wrote:
> > > Anders Logg skrev den 28/04-2007 følgende:
> > > 
> > > [snip]
> > > 
> > > > > Thanks, that fixed the first error. The second seems to be a missing file.
> > > > > 
> > > > > Ola
> > > > 
> > > > Fixed. Sorry about this.
> > > 
> > > Thanks, now, pydolfin does not compile:
> > > 
> > > dolfin_wrap.cpp: In function 'PyObject* _wrap_new_Function__SWIG_5(PyObject*,
> > > PyObject*)':
> > > dolfin_wrap.cpp:16769: error: no matching function for call to
> > > 'dolfin::SubFunction::SubFunction()'
> > > ../../src/kernel/function/dolfin/SubFunction.h:33: note: candidates are:
> > > dolfin::SubFunction::SubFunction(dolfin::DiscreteFunction*, dolfin::uint)
> > > ../../src/kernel/function/dolfin/SubFunction.h:29: note:
> > > dolfin::SubFunction::SubFunction(const dolfin::SubFunction&)
> > > make[1]: *** [_dolfin_la-dolfin_wrap.lo] Error 1
> > > 
> > > Ola
> > 
> > It's the old touch dolfin.i problem as usual... This should be fixed
> > now.
> 
> Great, both dolfin and pydolfin compile and install now.
> 
> I'll have a look at viper for vectorfields. A question; if you prefer
> mode="vectorfield", the displacement switch should be called
> "displacementfield"? Or should be stick to displacement and vector as viper uses
> today?
> 
> Ola

I just thought it was called "vectorfield", but "displacement" and
"vector" sounds good to me, with "vector" as default.

/Anders