Yeah, I am thinking solely about the library, not exodus... A std::bitset would actually be perfect if we are willing to limit the ids to something like [0,something_not_so_big)
----- Original Message ----- From: Roy Stogner <[email protected]> To: Kirk, Benjamin (JSC-EG311) Cc: '[email protected]' <[email protected]>; '[email protected]' <[email protected]>; '[email protected]' <[email protected]>; '[email protected]' <[email protected]>; '[email protected]' <[email protected]> Sent: Mon Mar 15 12:38:28 2010 Subject: Re: [Libmesh-users] Visualizing libmesh ex10 results On Mon, 15 Mar 2010, Kirk, Benjamin (JSC-EG311) wrote: > bool elem->on_subdomain(S) const > { return (_sid & S); } > > Or something like that? Of course care must be taken to set _sid originally?? > Some kind of > > void elem->add_to_subdomain(S) > ... > > ?? I must still be misunderstanding? If S is 0b011 and _sid is the same then on_subdomain() returns true for 0b011, but also for 0b010 and 0b001. But this sounds sort of like my idea - each libMesh subdomain_id maps to max_number_of_element_types different Exodus block ids. I would like to avoid touching Elem itself if we can; this is a restriction of the Exodus format and we ought to be able to "translate" entirely in the ExodusII I/O code. --- Roy ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
