On Thu, May 19, 2016 at 10:19 AM, David Knezevic <david.kneze...@akselos.com
> wrote:

> I would like to add support for Exodus's SHELL elements to libMesh, e.g.
> TRISHELL3 and SHELL4. See the attached figure from the Exodus standard for
> a picture of a SHELL4 element.
>
> As you can see from the figure, the only difference here is that this
> element has sidesets associated with the 2D faces as well as with the 1D
> sides. This is useful when imposing loads on shell models, e.g. it allows
> one to use Exodus sidesets (i.e. boundary_ids in libMesh) to impose surface
> loads instead of Exodus blocks (i.e. subdomain_ids in libMesh).
>
> In order to support this, I think we'd need to change BoundaryInfo so that
> we can get boundary_ids from an element (as opposed to only a side or node
> of an element). Before I dive into working on this, I wanted to check if
> others agree if this is the right approach, and if it makes sense to add it
> to libMesh?
>

So once the elements are in libmesh, they will just be treated as TRI3 and
QUAD4 types?

You will have to look at and possibly take out the hacks I put in to work
around the issue where Cubit 14+ automatically writes TRISHELL elements for
TRI3 elements when dim==3 (search for "is_cubit14_plus" in
exodusII_io_helper.C).  Actually, I don't know how you will differentiate
between the case where someone legitimately wanted a TRISHELL3 element and
where one was incorrectly written to the file by Cubit...

-- 
John
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to