On Tue, 9 Mar 2010, Karen Lee wrote:
I don't think I can get away without using MeshData. The reason I'm
using libmesh is precisely that I have data on a given (huge) mesh
that I am using as input...
Yes, so do many of us, but what kind of data? Data like initial
conditions and forcing functions in L2/H1/H2 is easy to store with an
ExplicitSystem::solution. Data like material properties maps well to
subdomain ids.
Without running in parallel then, do you think the problem is too
large to converge within a reasonable time frame?
Impossible to say without knowing what the problem is. If you've got
the same code running on a sequence of coarser meshes you're already
in a good position to extrapolate runtimes.
---
Roy
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
