On Fri, Oct 17, 2008 at 1:20 PM, Derek Gaston <[EMAIL PROTECTED]> wrote:
> So I did end up implementing the inverse maps it just felt wrong to do
> it any other way.
>
> My changes are all tested and committed (along with a few other bugs in
> exodus_io getting fixed...)... so now you will get
So I did end up implementing the inverse maps it just felt wrong
to do it any other way.
My changes are all tested and committed (along with a few other bugs
in exodus_io getting fixed...)... so now you will get sidesets in
exodus output from libMesh...
Derek
--
On Oct 16, 2008, at 2:09 PM, John Peterson wrote:
> It shouldn't be too bad, right? Several of the maps are identity
> maps, so that's easy. The rest are just C style arrays with less than
> 10 entries in most cases.
No it's not bad and I don't mind doing it... I just wanted to make
sure
John Peterson wrote:
> On Thu, Oct 16, 2008 at 3:09 PM, John Peterson <[EMAIL PROTECTED]> wrote:
>> On Thu, Oct 16, 2008 at 2:38 PM, Derek Gaston <[EMAIL PROTECTED]> wrote:
>>> Without providing the inverse maps the only thing I can think to do is loop
>>> over the face maps that are there until yo
On Thu, Oct 16, 2008 at 3:09 PM, John Peterson <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 16, 2008 at 2:38 PM, Derek Gaston <[EMAIL PROTECTED]> wrote:
>> Without providing the inverse maps the only thing I can think to do is loop
>> over the face maps that are there until you find the position holdin
On Thu, Oct 16, 2008 at 2:38 PM, Derek Gaston <[EMAIL PROTECTED]> wrote:
> Guys,
> I'm working on writing sideset info back out into the Exodus file (right
> now the sideset information is completely lost) and I wanted some opinions.
> There are currently face_maps at the top of exodusII_io_helper
Guys,
I'm working on writing sideset info back out into the Exodus file (right
now the sideset information is completely lost) and I wanted some opinions.
There are currently face_maps at the top of exodusII_io_helper.C... but
unfortunately these are geared for _reading_ sidesets and as such take
