Hi John, I see the problem. I guess it is hard to directly use subdomains as a direct equivalent to abaqus style elsets. Abaqus style subsets As Derek mentioned in a past email, it is probably better to have a higher order structure similar to boundary info, that is useful for checking material assignment or restricting solutions to subdomains. Thanks.
Subramanya G Sadasiva, Graduate Research Assistant, Hierarchical Design and Characterization Laboratory, School of Mechanical Engineering, Purdue University. "The art of structure is where to put the holes" Robert Le Ricolais, 1894-1977 On Sat, Jun 29, 2013 at 7:03 PM, John Peterson <[email protected]> wrote: > > > > On Sat, Jun 29, 2013 at 2:54 PM, Subramanya Sadasiva <[email protected]> > wrote: >> >> On Sat, Jun 29, 2013 at 12:13 PM, subramanya gautam >> <[email protected]> wrote: >> > >> > Why do you want your elements set names to have anything to do with >> > element >> >type? This really shouldn't be necessary with libMesh. >> >> The current version of AbaqusIO in libmesh assigns subdomain ids based >> element types. > > > Yes - and we do this because you can only have a single geometric element > type in a given block for Exodus files. Since Exodus files are used so > commonly by libmesh users, I decided to split up the elements within a given > Abaqus elset into geometric types as well, to make writing them to Exodus > files easier. > > -- > John ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
