[MOAB-dev] (no subject)

Hong-Jun Kim hongjun at mcs.anl.gov
Tue Jun 28 10:28:27 CDT 2011


Can you explain your problem more?
Actually, I don't understand why you should remove and make a new pcomm to remove entities....

-----------------------------
Hong-Jun Kim
Post-doc researcher
MCS, Argonne National Laboratory
9700 S. Cass Ave. B240/R2147
Argonne, IL 60439
630-252-4791
hongjun at mcs.anl.gov
-----------------------------

----- Original Message -----
From: lk58p at udcf.gla.ac.uk
To: "Iulian Grindeanu" <iulian at mcs.anl.gov>
Cc: moab-dev at mcs.anl.gov
Sent: Tuesday, June 28, 2011 9:49:20 AM
Subject: [MOAB-dev] (no subject)

On 28 Jun 2011, at 14:56, Iulian Grindeanu wrote:



----- Original Message -----
Hello,

I modelling crack propagation where some entities are created and
removed. I
work with parallel meshes and have problem how to clean remove ents
and resolve
shared entities.

When I remove entity I get error,
Reason: Entity should be shared but isn't.
Tri 62:
Adjacencies:
Vertex 56, Vertex 48, Vertex 102
Edge 103, Edge 101, Edge 104
Tet 361

Can you advise me how to solve this problem?

I am not sure I understand your problem.
If entities are in a set, you should remove them from the set, before deleting
the entities.
If this is too hard, when you create the set you should use the
MESHSET_TRACK_OWNER flag.
In that case, removing from the set is managed automatically when you delete the
entity (this takes more memory, and it is not turned on by default). Do you
create sets?

I am not sure about the sharing part, but I think that you would need to manage
that yourself; the distribution/sharing is resolved at the beginning;
Still, what is the scenario?
Best Regards,
Iulian


Thanks Iulian,

I have problem with sharing part. To make it work I had to create pcomm for
meshset after entities were removed.

Now I have to solve problem how to write parallel file and force moab to use new
pcomm (f.e. index 1 instead 0).

Regards,
Lukasz







----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


More information about the moab-dev mailing list