Sent from my iPad On Jul 10, 2013, at 11:05 PM, Roy Stogner <royst...@ices.utexas.edu> wrote:
> Or does this need to work in the moving mesh case too? Yep, moving mesh... and in fact I need it to give the exact same numbering to two meshes, where one is simply a distortion of the other one (element IDs currently do this fine BTW - even with adaptivity). > I admit, it > would be nice to have a way to prevent the trickier FE types (those > which choose basis sign based on some global ordering of points) from > breaking when the mesh gets distorted. That does sound handy. > > I'd rather avoid adding a mandatory extra 8 bytes to every DofObject, > but I don't see any insuperable obstacle to adding an optional 8 > bytes; this could even be run-time optional since we already have to > have that variable-size _idx_buf in there. The only practical > obstacle is that the _idx_buf code is *already* scary complicated. At this point I would just prefer a compile time option. We are going to have code connected to this thing in quite a few places in MOOSE so I would really like to be able to do elem->unique_id or some such. Are we at the point where I can gin something up and put in a pull request and we can discuss from there? I really don't think it's going to be much code to get started with. Derek ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
