Re: [Libmesh-devel] QBase::init()

2011-06-29 Thread Boyce Griffith
This makes sense, thanks. What I had done was to add a method to provide the element specific information, but I was performing the actual initialization in init_1D(), init_2D(), or init_3D(), which was of course not getting called. However, I wonder whether there is any case in which a quadrat

Re: [Libmesh-devel] QBase::init()

2011-06-29 Thread Roy Stogner
On Wed, 29 Jun 2011, Derek Gaston wrote: > Basically, the QBase interface doesn't have any functions that take > an Elem* for reinitialization... so you would have to do something > like this no matter what. Should we be open to changing the QBase interface so that, say, init takes a const Elem*

Re: [Libmesh-devel] QBase::init()

2011-06-29 Thread Derek Gaston
What we've done here is inherit from QBase and override shapes_need_reinit() to return true. Then, when we hit each element we call a function on our qrule ourselves (like qrule->recalculate_points(Elem * elem) ) that passes in information and allows the qrule to recalculate it's points. After

[Libmesh-devel] QBase::init()

2011-06-29 Thread Boyce Griffith
I am trying to setup an adaptive quadrature rule that will use different quadrature points/weights on different elements in the mesh. (In this particular application, the number of quadrature points depends on the size of the element.) I am not sure how to get this to work, because QBase::ini