On Mon, Apr 8, 2013 at 9:51 AM, Kirk, Benjamin (JSC-EG311) <benjamin.kir...@nasa.gov> wrote: > On Apr 8, 2013, at 10:43 AM, David Knezevic <dkneze...@seas.harvard.edu> > wrote: > >> The first thing that comes to mind is changing Elem to store a >> std::set<subdomain_id_type>, would that be of interest in general? > > Provided it's only conditionally enabled with > > ./configure --enable-multiple-subdomain-ids > > or something - that sounds like it would be memory-expensive for the general > case. > > then a > > typedef subdomain_id_type SubdomainIDContainer; > typedef std::set<subdomain_id_type> SubdomainIDContainer; > > conditional. > > But really, the other option is user-code that recognizes multiple subdomain > ids as belonging to a single material, and that may be just as convenient?
Yeah, I'd favor this option...IIRC we have had similar discussions in the past and always come down on the side of saving memory per elem. -- John ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
