On 04/08/2013 11:51 AM, Kirk, Benjamin (JSC-EG311) 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?
What do you have in mind with the user-code here? The scenario I have in mind is that I have a large mesh, which is built up of "components" where each component is marked with a subdomain_id (since we need to be able to know which "component" we're on during matrix assembly). But within each component we also need another subdomain_ids to indicate different material properties etc. So I need an "intersection" of subdomain IDs in order to do the matrix assembly. ------------------------------------------------------------------------------ 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
