On Thu, May 19, 2016 at 1:13 PM, Paul T. Bauman <ptbau...@gmail.com> wrote:
> This all sounds fine, but I admit I'm curious about where you need this as
> opposed to just using the element normal (not elem.normal()) to use in
> applying the loads. I don't doubt that you do, but I haven't run into a
> case yet where I needed this, although I've only been playing with
> membranes and not shells proper. Regardless, thanks for taking this on.
>
The motivation for this change is to make life easier for users who are
defining loads on shell meshes.
Imagine you have a TRI3 mesh, and you want to impose surface loads in some
(possibly overlapping) regions. To do that, you'd have to use subdomain
IDs, which means you have to make the subdomain regions conform to the load
regions. This can lead to unnecessarily complicated subdomains that are a
pain for the person making the mesh.
It's much easier to use sidesets for this purpose (which is what TRISHELL3
and SHELL4 allow) because we can add multiple sidesets per side.
Another advantage is that it allows us to use subdomains to store material
properties (e.g. Young's modulus) and boundary_ids to store "surface
properties" (like loads), which leads to a clearer separation of
"volumetric" and "surface" properties.
Let me know if you agree with the comments above?
David
------------------------------------------------------------------------------
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
