> Assume that a multi-physics problem or a problem with single system on > a staggerred grid (velocity, pressure on different meshes) needs to be > solved. Since the Mesh is always associated with EquationSystems and > the association of a LinearImplicitSystem or NonlinearImplicitSystem > to the EquationSystems is how the description of the problem mesh is > made, you can quickly see that without a constructor for the System > class to take its own mesh object, there is an inherent difficulty in > associating 2 meshes to the same problem. I hope that wasn't > confusing.
Splitting the discrete operator into two systems will force you to solve them iteratively in a decoupled fashion -- so long as you are OK with this then you could effectively accomplish the same thing with two EquationSystems objects, each one containing its own distinct mesh and System. I have not tried it, but I would think that should work fine. If it does not work then that should probably be considered a bug and get fixed. -Ben ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
