On Fri, 20 Nov 2009, Vijay S. Mahadevan wrote:
> I'm still trying to understand what is broken in the xda IO. And is > this the same format as .xdr ? Is the mesh not written out properly or > is it not converging to the right solution ? I do not have two version > of libmesh enabled and disabled with Hilbert but am curious to know > what is failing in ex10 though. There's either a bug in reading or in writing - it appears that the solution on an AMR mesh is getting "scrambled" when read out and back in. With the --disable-libHilbert bug, this happens after just one or two refinement steps. With the --enable-libHilbert bug, things seem to be okay until after 10 or 11 steps. > I did a grep on the source files and Hilbert is called only for > sorting indices in Utility apart from the global_indices() routine. > That seems harmless enough to not cause any problems in the absence of > Hilbert. Or may be I missed something else here... Well, messed up indexing would certainly explain the symptoms I saw. --- Roy ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
