← Back to team overview

dolfin team mailing list archive

Re: Problem with numpy array indices

 

On Fri, Dec 12, 2008 at 02:41:25PM +0100, Johan Hake wrote:
> On Friday 12 December 2008 14:25:30 Anders Logg wrote:
> > I've updated the demo in
> >
> >   demo/fem/simple/python
> >
> > to the new interface but it breaks:
> >
> > Traceback (most recent call last):
> >   File "demo.py", line 31, in <module>
> >     [-1.0/6.0, 0.0, 0.0, 1.0/6.0]]), pos, pos)
> >   File
> >  
> > "/scratch/fenics/dolfin/dolfin-dev/local/lib/python2.5/site-packages/dolfin
> >/cpp.py", line 1830, in set return _cpp.GenericTensor_set(*args)
> > TypeError: in method 'GenericTensor_set', argument 4 of type
> > 'dolfin::uint const *const *'
> >
> > Does anyone know how to fix this?
> 
> I think this ability dissapeared when I went over the LA interface. 
> 
> I %ignored all FooMatrix.set and FooMatrix.get, as I thought these were not 
> used from the PyDOLFIN interface. I was apperently wrong. The only one that 
> is alive is the set from GenericTensor, and it is this that expects a double 
> * double * for the 3 (4) argument.
> 
> I suppose we want to keep the set function we use in this demo, and maybee try 
> to %ignore the one that comes from Generic Tensor, i.e., the opposite of what 
> I managed to do ;P

Yes, I guess. I rarely use this but it's nice to have and it's there
in the demo.

-- 
Anders

Attachment: signature.asc
Description: Digital signature


Follow ups

References