> I noticed something very reminiscent of this just two days ago. In my case > I run a transient solution to steady-state and then stop the simulation. > > I then re-read this result, refine the mesh, project the solution, and > re-converge on the refined mesh. > > 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... > > 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.
Well, in my case the issue is not in the system projection. About 70% of the initialization time is spent refining the mesh, specifically in MeshRefinement::add_point(). I'll keep looking, though. -Ben ------------------------------------------------------------------------- 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
