On 12/1/10 9:31 PM, Roy Stogner wrote: > > Did you really managed to get overlapping BC IDs working with a > dozen-line patch? Egg on our faces... I don't think any of the > primary developers use multiple IDs on the same boundary right now, > but if we'd known it would be that simple to support the I/O we'd have > done it years ago. > > I don't see any obvious problems with this patch in the multiple ID > case and it looks like it degenerates to the existing behavior in the > single ID case, so I'll commit it now. We really ought to get a > test for this into the examples or unit tests too... it's the sort of > underused feature that's easy to regress.
Looking around, there are some other places in libMesh that appear not to handle multiple boundary IDs per side. In particular: fe_base.C ~ around line 2018 mesh_communication.C ~ around lines 364 and 1080 mesh_modification.C ~ around lines 840, 1224 and 1292 unstructured_mesh.C ~ around line 914 I think that in each case, it should suffice to loop over the IDs returned by BoundaryInfo::boundary_ids(). If you agree, I'm happy to send a patch. -- Boyce ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
