|
From: Kirk, B. (JSC-EG311) <ben...@na...> - 2010-03-15 17:18:12
|
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)
...
??
----- Original Message -----
From: Roy Stogner <roy...@ic...>
To: Kirk, Benjamin (JSC-EG311)
Cc: 'fri...@gm...' <fri...@gm...>; 'cod...@gm...' <cod...@gm...>; 'pet...@cf...' <pet...@cf...>; 'man...@gm...' <man...@gm...>; 'lib...@li...' <lib...@li...>
Sent: Mon Mar 15 12:09:39 2010
Subject: Re: [Libmesh-users] Visualizing libmesh ex10 results
On Mon, 15 Mar 2010, Kirk, Benjamin (JSC-EG311) wrote:
> Seems like within libmesh multiplw subdomain ids could be handled
> effectively with some bitwise & and | ??
Elaborate?
My brightest idea:
We have a potentially-hybrid subdomain of subdomain_id N, we start
writing it out with Exodus_id N. each time we see a new element type
we assign Exodus_id N+magic_max_id_number to it.
We start reading in elements; if any of them have a larger Exodus_id
than magic_max_id_number then we give them a subdomain_id of
Exodus_id%magic_max_id_number.
As long as magic_max_id_number is less than max_Exodus_id /
max_number_of_element_types then we're fine.
I think Jed recently mentioned inventing his own file format in a very
apologetic tone; at the time I was thinking that although reinventing
the wheel is a bad idea in general, it might be justified when your
selection of existing wheels is limited to a hexagonal design, an oval
design, a design made from concrete...
---
Roy
|