Re: [Libmesh-users] Small question about AbaqusIO

[John P. <jwp...@gm...>]

On Thu, Jun 13, 2013 at 10:20 PM, Subramanya Sadasiva
<ssa...@pu...>wrote:

> HI,
> I am trying to use AbaqusIO in my work and I came across this doubt.. If I
> have sidesets defined through *SURFACE, and boundary nodes also defined ..
> then can't the same boundary_id be assigned to domains that might have been
> intended to be separate?
>

Sorry, I saw this email a few days ago, but it got buried.

The AbaqusIO reader reads the *NSET, *ELSET, and *SURFACE sections and
assigns numerical IDs to them in alphabetical order.

So if you have 1 nodeset and one sideset defined in a file, they will both
receive boundary ID "0", although they may be completely unrelated.  Abaqus
does not provide a numbering, otherwise we would just use that...

Since nodes and sides are stored separately in the BoundaryInfo object,
there's not really a danger of "the same boundary_id [being] assigned to
domains ... intended to be separate".  It's up to the user to know what the
difference is, and handle it accordingly.

That said, BoundaryInfo now supports assigning names to given side and
nodeset IDs:

 std::string& sideset_name(boundary_id_type id);
 std::string& nodeset_name(boundary_id_type id);

and the AbaqusIO reader should probably make use of this functionality.
 It's on my TODO list, but it's way at the bottom.

-- 
John