On Mon, 7 Apr 2008, Lorenzo Botti wrote: > Ok, I have found the problem... > ComputeHilbertKeys is calculating the same node_key for different nodes. > This is a mess because the mesh has no tears, even for higher h > refinement levels. > > Any idea? I don't know how LibHilbert works.
I'm afraid this is up to Ben; it's a library he added to help with parallel I/O, I believe. --- Roy ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
