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. This is indeed *very* tricky... but for now I'm willing to just trust
that it's going to work ;-)
> I'd want to keep it pretty modular (e.g. ideally System shouldn't need
> to know about DTK any more than it knows about Exodus) but I'd love to
> see the support get in at the libMesh level.
>
Of course. I described as a System providing a field... but that won't be
the interface. You'll call a function like:
dtk_object.provide_field(System & sys, std::string field);
So the System won't know about this at all... but any field from any system
can be provided to the other codes through DTK.
Derek
------------------------------------------------------------------------------
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
