On Wed, Apr 20, 2016 at 3:32 PM, Roy Stogner <[email protected]> wrote:
> > On Wed, 20 Apr 2016, John Peterson wrote: > > We should probably just call prepare_for_use() from >> TriangleInterface::triangulate() to avoid issues like this... >> > > Agreed. That should be safe for most old code, too; duplicate calls > to prepare_for_use() are redundant but not forbidden. > Just to close the loop on this, the issue was due to the mesh not being *partitioned* yet, and had nothing to do with active/inactive elements. The fix has been merged in 256034e, I confirmed that it worked with misc_ex6. Thanks, John ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
