On Dec 10, 2008, at 12:04 PM, Roy Stogner wrote: > Hopefully I'm just being overly paranoid, though; do Exodus/etc. > support multiple IDs per side?
The answer is yes: Exodus does support more than one side id per side. In reality it's not a side ID per say... but rather lists of sides... or sidesets that are associated with numbers. The same side can be included in multiple sidesets. That said... I don't envision ever using this capability. What we do now is associate boundary conditions with boundary ids. We can associate any number of boundary conditions with a side id... which takes care of the case that Ben was mentioning. Essentially the ID or number itself doesn't mean anything in particular... we just use it to get the list of boundary conditions active on that side. With that scheme there is never a reason to assign more than one ID to a side.... you can always just make any "overlap" region it's own boundary_id and apply both boundary conditions on that boundary id. In Sierra they _did_ utilize this capability from time to time... but it was really more of a convenience. Derek ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
