On Wed, 12 Nov 2008, Benjamin Kirk wrote: >> Run your changes by me? find_neighbors() is probably where we need >> to fix the outstanding bug in ParallelMesh adaptive coarsening, too. > > I'm not sure what that bug is, but here's what I've got planned...
What you've got planned should fix ParallelMesh. As my favorite debugging strategies go, asserts and gdb have now been supplanted by "wait for Ben to touch the code again". > I don't want to throw away the information from 1, just to update it with > the new elements. (I was just thinking about an optional bool > remove_existing_neighbor_info = true or something like that... That would work. > (7) after all this, by my estimation any *local* element that has a NULL > neighbor truly does live on the boundary. Hmmm... yes, at least if we handle subactive neighbors correctly; IIRC we may be ignoring them in the current code. > There is a final step to add RemoteElem's where needed to the ghost > element neighbor list, but that is doable by asking their owning > processor. Yes; on the owning processor the element will know all it's neighbors by this point. --- Roy ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
