On Tue, 13 Oct 2009, John Peterson wrote:
> On Tue, Oct 13, 2009 at 11:40 AM, Joa Ljungvall <[email protected]> wrote: >> It is quite possible that I move the wrong nodes the wrong way, but is my >> problem ;). The general question is, is this a possible route to take? I call >> this routine after refinement and coursening, before >> equation_systems.reinit(). > > I seem to remember there being some restriction when doing > refinement/coarsening and mesh redistribution, i.e. all mesh movement > had to be performed before any refinement/coarsening. I think it had > to do with the coarsening step, but the way we handle constraints also > assumes some level of parent is conforming with the neighbor... and I > don't think this is the case with mesh movement. The parent can always be made conforming with the neighbor in the case of a hanging node constraint - you just need to note that the hanging node's location is constrained as well, and keep that constraint satisfied. But failure to do that would just lead to potentially inaccurate projections and constraint equations. I'm not sure how someone would run into an inverted Jacobian... unless the coarse mesh was so far from the real boundary that snapping nodes to the boundary resulted in a completely twisted-around element. --- Roy ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
