Hello, Roy and John,
Thank you very much for your feedback. Yes, I am working with a mesh that
is too big. Either a mesh of 1024^3 cells or a mesh of 256^3 cells that is
further refined adaptively to get a local resolution of 1024^3. It can be
opened on a single processor subject to the available
On Mon, 4 Dec 2017, John Peterson wrote:
On Mon, Dec 4, 2017 at 10:59 AM, Alam, Jahrul wrote:
Thanks for the clarification. Can you suggest a work around? If I do,
mesh0.read(lshaped_0.vtu) and mesh1.read(lshaped_1.vtu), and so on, is it
possible to end up with a DistributedMesh by combining
On Mon, Dec 4, 2017 at 10:59 AM, Alam, Jahrul wrote:
> Hi John,
>
> Thanks for the clarification. Can you suggest a work around? If I do,
> mesh0.read(lshaped_0.vtu) and mesh1.read(lshaped_1.vtu), and so on, is it
> possible to end up with a DistributedMesh by combining mesh0,
> mesh1,...
Hi John,
Thanks for the clarification. Can you suggest a work around? If I do, for
example, mesh0.read(lshaped_0.vtu) and mesh1.read(lshaped_1.vtu), and so
on, is it possible to end up with a DistributedMesh by combining mesh0,
mesh1,. at the user level?
Or, is there another format th
On Sat, Dec 2, 2017 at 6:49 PM, Jahrul Alam wrote:
> Hello,
>
> I am having a problem with reading a mesh. As a test case, I create a Mesh,
> and save the mesh:
>
> lshaped_mesh.wite("lshaped.pvtu").
>
> Running with 4 processes, I get five files: lshaped.pvtu, lshaped_0.vtu,
> lshaped_1.vtu, lsh
