Dear Ben, On Thu, 4 Sep 2008, Benjamin Kirk wrote:
> I noticed something very reminiscent of this just two days ago. > [...] > I can't quantify it at the moment but this took a lot longer than expected. > I just "seemed really long." It was somewhat acceptable in my case since I > then did a hundred time steps or so on the refined mesh, but still... Ah, so I'm not the only one having this problem. But still, since most of you guys out there seem to not have this problem, it might also be caused by some mistake on user side. So, Ben, if you find out what's going wrong, please let me know. > I only offer this as a data point and to assure you I will dig into it in > glorious detail when I get back on Monday. It should be a lot easier to > debug since I think I can reproduce it locally. You're right, debugging via email is somewhat cumbersome. Best Regards, Tim -- Dr. Tim Kroeger Phone +49-421-218-7710 [EMAIL PROTECTED], [EMAIL PROTECTED] Fax +49-421-218-4236 MeVis Research GmbH, Universitaetsallee 29, 28359 Bremen, Germany Amtsgericht Bremen HRB 16222 Geschaeftsfuehrer: Prof. Dr. H.-O. Peitgen ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
