Thanks for pointing me to the discussions, Roy. So if I understand correctly, the current implementation of DistributedMesh::add_extra_ghost_elem() only provides the G() version of your new API without an “evaluable” entity? If my interest is in the E() entity, would it be best to wait for your API, or is there a way to get it to work in current libMesh? Perhaps follow the implementation in MOOSE?
-Manav > On Aug 10, 2016, at 6:54 PM, Roy Stogner <[email protected]> wrote: > > > On Wed, 10 Aug 2016, Manav Bhatia wrote: > >> will do. Thanks! > > If you want to chime in or just read my thoughts on the design > questions, the issue where I've been documenting them is > https://github.com/libMesh/libmesh/issues/1028 > > The first third of the design got merged in > https://github.com/libMesh/libmesh/pull/1057 > and I hope to have the next third by the end of the week. > > This is going to have libmesh_experimental() all over it for a while; > I think the design overview is solid but API arguments, return values, > etc. aren't set in stone yet. > --- > Roy ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
