On 08/28/2012 02:52 PM, Roy Stogner wrote: > > On Tue, 28 Aug 2012, David Knezevic wrote: > >> OK, well I'd be happy to add the complete API, as long as we're >> happy to assume that the meshes are conforming on the interfaces, >> and that the user provides all the necessary connectivity info >> (essentially a "meta-mesh" data structure) > > Should it require a complicated data structure? User specifies two > boundary condition ids, library stitches together points from the one > that equal points from the other; user repeats with different ids as > necessary, then makes sure to prepare_for_use() before finishing.
Yep, that's what I had in mind. The boundary IDs act as neighbor connectivity. So we just leave points on a boundary that don't match up untouched? Works for me. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
