On Thu, Aug 16, 2012 at 8:36 AM, Roman Vetter <[email protected]> wrote:

> I'm going to need two different meshes (with different dimension) in one
> simulation. On each of them, a transient system is solved, and they
> mutually interact during each timestep. My perception is that the
> intended way to achieve this is by using two EquationSystems. Is that
> correct?
>

libMesh now supports multiple dimensional elements in the "same" mesh.  So
if you want to solve the whole problem in one solve you could use that
instead of two EquationSystems.  But yeah... generally you will want to use
two EquationSystems (just think this: Each EquationSystem can only use one
mesh... so if you want to split the problem into two meshes you need two
EquationSystems).


> An additional challenge will be parallelization. Serial execution will
> take months in some cases, so I'm going to need to parallelize as much
> as possible. Ideally, both systems should be parallelized such that of a
> total of N processors, the first system is parallelized to (and solved
> on) M processors, while the other N-M processors are handling the other
> system. What is the intended way (if any) to do this? Initialize libmesh
> twice, with different MPI communicators?
>

There probably isn't a reason to do this.  Are you literally going to call
"solve()" simultaneously on both systems?  Most likely you will solve one
then the other right?  If that's the case just let them use the same
processors.

You can initialize libMesh with different communicators on different
processors.... but you will have a hard time getting those two
"subsections" of processors to talk to each other....
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to