So... after trying to actually use my little hack to create nodesets from sidesets... I ran into an interesting problem... I really do need multiple boundary ids per node. The reason? Multiple variables. Think about two boundaries that touch... on one boundary I have Dirichlet conditions on "u" on the other I have Dirichlet conditions on "v".... at the nodes that they share I _really_ need to be able to set the conditions for both variables.... it's easy to think of this situation if you think about no penetration BCs....
So I'm thinking... why don't we just make the std::map for _boundary_node_id in BoundaryInfo into a std::multimap... just like the _boundary_side_id map for elements? There really is no reason a node can't be assigned multiple boundary ids.... or none that I can think of. Then the ordering of which BC will "win" will just be up to the order the user applies the BCs.... Any thoughts? Derek ------------------------------------------------------------------------------ _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
