On Feb 9, 2012, at 9:28 AM, Roy Stogner wrote: > There are lots of places where we build an FEBase object of > mesh_dimension() and then assume that we can use it on every element, > for starters.
Well… of course the user doing this would have to be aware of what they are doing and do the right thing. > This is a great idea but would almost certainly break on > find_neighbors(). Interesting - I hadn't thought of that. Well, if find_neighbors() breaks you should still be able to have a separate piece of the mesh that is 1D and copy values back and forth between the two pieces. You can even add more entries to the sparsity pattern and send_list so that it "ties" the two pieces of the mesh together. The reason I'm in this discussion is that we're going to be doing something similar soon. Derek ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
