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.C... but > unfortunately these are geared for _reading_ sidesets and as such take an > Exodus side number and turn it into a libMesh one. > Do you guys see any way around me needing to essentially provide the inverse > maps of these face maps?
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. I would just add the inverse maps to the ExodusII_IO_Helper::ElementMaps object as static arrays. > I was able to get around this when writing out elements and nodes because > they were _all_ going to get written out anyway... but for sides you really > need to look up just one ID. > 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 holding the ID > you are looking for... and that will be the Exodus side id.... but that is > just terrible. It's n^2 yeah but that n is fixed and really small... -- John ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
