On Thu, 17 Jan 2013, Derek Gaston wrote:
On Thu, Jan 17, 2013 at 10:39 AM, Roy Stogner <royst...@ices.utexas.edu> wrote:
This is the right way to do things in general, but the details get
*real* tricky - does the union mesh end up being made of
nearly-arbitrary polyhedra when the input meshes aren't aligned?
The meshes they showed us didn't end up as polyhedra... but I guess we'll see.
For unions of linear simplicial meshes you can just turn each
polyhedron into more simplices; not a great idea if it was going to
effect basis conditioning but just fine if it's only used for
integration.
But that's not even the real tricky case: For unions of higher order
simplices (or *any*-order hexes/prisms/pyramids) the geometric union
can include *lenses* and even nastier shapes; I can't even imagine the
right way to handle that.
This is indeed *very* tricky... but for now I'm willing to just
trust that it's going to work ;-)
Well, trust but code-verify, anyway. ;-) I wonder if I should just
add an optional "configure --enable-masa" to libMesh now that our MASA
MMS library is officially public and LGPL2'ed.
Of course. I described as a System providing a field... but that
won't be the interface.
Okay; glad that's obvious to you. I wish it had always been more
obvious to *me* - e.g. in hindsight we probably should have had a
"class ElemTools" for many of the methods that are currently
ballooning "class Elem" up to a thousand lines.
---
Roy
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
