On Mon, Oct 12, 2015 at 10:14 AM, Paul T. Bauman <ptbau...@gmail.com> wrote: > > > >> Seems counter-intuitive, but it >> works since there's no other sensible meaning for "0" to have - anyone >> who wants to enforce "no mismatch at all" should be using >> refine_uniformly(). >> > > As an aside, I'm not sure I agree with the idea of no mismatch ==> you > should do uniform refinement. In fact, we had 1 user ask for this some time > ago (don't ask me how long, I don't have any sense of time anymore). Sure, > it will force refinements of lots of nonlocal neighbors, but it may not be > so bad as you're better off just doing uniform refinement (although I'm > sure there are cases where that's true). Nevertheless, I'm not as familiar > with these code paths, so if it requires lots of changes, I don't think > it's worth our trouble (but I wouldn't turn someone away that was dead set > on implementing it for us). >
Oh wait, never mind. That's only the case if we support anisotropic refinement (and we don't). Move along, nothing to see here...
------------------------------------------------------------------------------
_______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
