On May 18, 2011, at 1:48 PM, Roy Stogner wrote: > Good to hear. The one aspect to that support that I'd feared might be > lacking is I/O. > > Does that work for visualizing boundary ids as well?
Visualizing boundary ids is simple... just use Paraview or Ensight. Ensight is great... it colors your boundaries by the boundary ids... and you can see where they overlap. In Paraview just turn off all the blocks and turn on sidesets (usually one at a time so you can see what each one contains). Both programs also allow you to draw the sidesets and paint solution variables on them (and displace them, etc.). No reason to do the whole BoundaryMesh thing at all for visualization. >> It would be cruel... BUT, I had a user in my office just yesterday >> that wanted to have overlapping subdomains. I think for now we're >> going to deal with it using an external file that defines the >> overlaps and deal with it manually... but there could be a better >> way. > > We could do fancy things with copy-on-write here (more easily if we > replaced the non-const subdomain_id() with a straightforward setter > method) to keep the costs from getting too out of hand. I'd be > willing to write the guts if you'd handle the Exodus/Nemesis support. I'm not exactly following you here... > I think whatever we do would at least have to replace that _sbd_id > char with a full pointer... > > On the other hand, if we're really worried about every 8 bytes, > there's a handful of little optimizations that we could do but > haven't yet. Consolidating _children and _parent pointers into the > same array as _neighbors would free up at least 16 bytes per element > right off the bat. >> The trouble is that this won't be very compatible with >> Paraview/Ensight/Visit.......... and that's a big gotcha. > > Define incompatible for me? They won't be able to visualize the > subdomains? Or they won't be able to open the files as all? Wouldn't be able to visualize the subdomains. In particular you wouldn't be able to "turn off" or "hide" subdomains. That is a VERY important feature that we use ALL the time (because we have models with multiple "layers" in subdomains that are surrounding each other... so it is great to be able to turn off an outside "layer" to see an inside layer.... and no, a slice doesn't always cut it (pun!). >> I don't think there is any great answer here... > > For the original problem, I think I'm settling on "boundary element > subdomain id == interior element boundary condition id". That'll at > least avoid breaking anyone's bcid viz, and there's no real downside > other than that it rubs my nose in an existing problem. Sounds fine... but like I say there are better ways to do boundary visualization these days.... Derek ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
