It is supported... but one thing to keep in mind is that the output format we like to use (ExodusII) has a requirement that separate element types must be in separate element "blocks" (in libMesh that means they must have separate "subdomain_ids").
Note: that is NOT a requirement in libMesh. libMesh doesn't care if you mix element types in the same subdomain... it's only a limitation in that output format. With ExodusII you can still have a mixed element type mesh... just take care to put each element type in its own subdomain. Derek On Fri, Mar 25, 2016 at 8:04 PM Harshad Sahasrabudhe <[email protected]> wrote: > Thanks! That's really awesome! > > On Fri, Mar 25, 2016 at 8:01 PM, Kirk, Benjamin (JSC-EG311) < > [email protected]> wrote: > > > > > > On Mar 25, 2016, at 6:33 PM, Harshad Sahasrabudhe <[email protected] > > > > wrote: > > > > > > It is > > > supported out of box, e.g. is the point locator, partitioning etc known > > to > > > work? > > > > Yes. We may not refine pyramids at present - I'll have to check, but > > everything else just works. > > ------------------------------------------------------------------------------ > Transform Data into Opportunity. > Accelerate data analysis in your applications with > Intel Data Analytics Acceleration Library. > Click to learn more. > http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 > _______________________________________________ > Libmesh-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-users > ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
