On Thu, 19 Nov 2009, Vijay S. Mahadevan wrote:
> Ah I see. I do not use AMR extensively these days and so most of my > test problems have been working smoothly without encountering the > error you mentioned. I assumed this was a very specific bug that > occurred only after several refinements. If this is the case, can I > fall back to enabling Hilbert library ? Or would it be safer to wait > for your implementation to be checked in before I start running in > parallel ? My implementation's checked in now. Whether it's safer to trust code that hasn't been thoroughly tested or code that has been found to fail in a few hard-to-find cases is a matter of opinion. I'd appreciate it if you'd run with the new implementation, though, so that we start getting that more thoroughly tested ASAP. That seems like the fastest way to get back to "safe". The libHilbert issue appeared to be a problem in their code, which either means that we have to fix their code or that we've misunderstood the problem; either way it may take us a while to make it safe to turn that back on. --- 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
