Dear all,
I re-configure libmesh with --enable-parmesh (rather than --enable-everything?)
and start from 50x50x50, things work fine.
Thank you.
Regards,
LL
-原始邮件-
发件人: "Cody Permann"
发送时间: 2015年2月9日 星期一
收件人: li@siat.ac.cn, libmesh-users
抄送:
主题: Re: [Libmesh-users] Fw: Re: Re: A pr
If you're trying to solve a different problem on each processor you'll want
to create an MPI sub-communicator for each processor and then initialize
the Mesh with that (Note the Mesh constructor that takes a
Parallel::Communicator:
http://libmesh.github.io/doxygen/classlibMesh_1_1Mesh.html ). I be
Thanks for the quick replies!
Roy - I actually do something a bit messy:
SerialMesh* rmsh = new SerialMesh(1);
GmshIO(*rmsh).read(filename.str().c_str());
rmsh->skip_partitioning(true);
rmsh->prepare_for_use();
rmsh->skip_partitioning(false);
rmsh->partition(1);
I f
On Mon, 9 Feb 2015, Peter Wijeratne wrote:
> Bit of a special (as opposed to general) problem here. I'm trying to
> create a serial mesh on each of N processors, each to be kept on its
> respective processor and solved separately.
Are you initializing each Mesh with an appropriate (in this case
There's an assumption that all the processors are working on the same
problem so each processor gets a part of the mesh. Are each of the meshes
truly independent so they don't share any DOFs? If they really are
independent have you considered just running thousands of jobs instead?
Cody
On Mon
Hello libMesh community,
Bit of a special (as opposed to general) problem here. I'm trying to
create a serial mesh on each of N processors, each to be kept on its
respective processor and solved separately. This causes problems when
initialising a given mesh's EquationSystems; I've narrowed the
Don't get too focused on just the mesh memory usage. In my experience
serial mesh works fine even for meshes of this size. You have other memory
consumers to worry about like your system matrix and solution vectors too.
Cody
On Sat Feb 07 2015 at 7:31:07 PM wrote:
>
>
> Thanks a lot.
>
> 1. I
