On Mon, 18 Apr 2011, Boyce Griffith wrote:

> I need FE::reinit() to work at arbitrary locations for the side version of 
> reinit().  Attached is a patch that adds this functionality for both the side 
> version of reinit() and for edge_reinit().  I wasn't completely sure what to 
> do for the InfFE case for the side case, so in the patch, if someone calls 
> the side version of reinit or edge_reinit, an error message is printed and 
> libmesh_error is called.
>
> I also anticipate eventually wanting to be able to supply both positions and 
> quadrature weights, so I also added an optional weights argument to all of 
> the reinit functions.  If the user specifies points but not weights, then the 
> patch reverts to using the same dummy weights as usual (all 1's).

This is interesting; what's the application?  Generally when I want
FE::reinit at specified points, I've got those points in physical
space, which means I can inverse_map them and get whatever I need from
the regular reinit(vector).

But I guess if you're doing something like interfacing an 3D with a 2D
copy of its BoundaryMesh, you'd already have the points in 2D master
element space and so you'd want to avoid the map+remap, huh?  Our
application code does just that, the lazy and expensive way, and it
would be nice to fix that...

My first inclination is to put this patch in right after releasing
0.7.1 around the end of the week.  If others could look it over
beforehand that would be good.
---
Roy

------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to