On Mon, 26 Oct 2009, Joa Ljungvall wrote:
> What I'm trying to do is:
>
> 1) Refine the mesh
> 2) Find and store hanging nodes
> 3) Move points on boundary to the "real" boundary
> then I do a do{...}While() including
> 4) Check that Jacobian>0, if not switch node 0 and 2 (the pointers in the
> elem)
> I'm not sure this doesn't mess up something for neighbors..
This merely hides a symptom without fixing the problem. If you have
two elements ABC and CBD, and you invert one of them by moving a node
too far:
A---------C A---------C
\ /| \ .-'/
\ / | \ D /
\ / | \ | /
\ / | \|/
B----D B
Changing CBD into CDB doesn't actually make that second mesh valid;
instead of an inverted element you'd have two overlapping elements!
And I'm pretty sure you'll break some of our mesh topology assumptions
(and thereby break the find_neighbors routine, leading to that
remote_elem bug) in the process.
---
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
