Automatic_Nodes_To_Surface
Samin Haeri
Hello everyone,
I want to know the details of the settings of the Automatic_Nodes_To_Surface contact keyword in LS-DYNA, but unfortunately, there is no separate title about that in LS-DYNA keyword user's manual. How can I learn about this keyword?
Thanks a lot
James Kennedy
Dear Samin,
-------------------------------------------------------
Contact between Beam and Shell Elements
In general, *CONTACT_AUTOMATIC_SINGLE_SURFACE, *CONTACT_AUTOMATIC_
GENERAL, or *CONTACT_AUTOMATIC_NODES_TO_SURFACE should handle a beam-
to-shell-surface contact situation. All of these contact types take into account thickness offsets.
The first two contact types mentioned above are single surface contacts and so both the shell
and beams parts should be included on the slave side with the master side being null. For an
automatic_nodes_to_surface contact, the beam part (or its nodes) should be slave, the shell part
(or its segments) should be master. For any of the above, a search is made for penetration of beam
nodes (or more precisely, a sphere around each beam node) through shell surfaces.
If the contact situation is beam-to-shell-EDGE, one might have a problem. In that case, one has
to stick with *CONTACT_AUTOMATIC_GENERAL AND add null beams (low density
beams utilizing *MAT_NULL) along (merged to) the outer edges of the shells. The null beam
part should be added to the slave side of the contact.
-------------------------------------------------------
A relatively new contact which has a short discussion presented here (beam to shell
edge contact with null beams/example provided is also discussed):
http://ftp.lstc.com/anonymous/outgoing/jday/faq/contact.beam-to-shell
An example is also provided here:
http://ftp.lstc.com/anonymous/outgoing/jday/beam_thru_hole.k
This small example illustrates the contact in a beam-to-solid-surface application. Unlike
*contact_automatic_nodes_to_surface, it is clearly able to detect contact anywhere along
the beam length.
-------------------------------------------------------
Be advised that *CONTACT_AUTOMATIC_BEAMS_TO_SURFACE_ID is a node
to surface type contact (b5) which means that the beam must be specified as the slave
entry:
-------------------------------------------------------
*CONTACT_AUTOMATIC_BEAMS_TO_SURFACE_ID
$# cid, title
1
$# ssid, msid, sstyp, mstyp, sboxid, mboxid, spr, mpr
$2, 1, 3, 3, 0, 0, 0, 0
1, 2, 3, 3, 0, 0, 0, 0
-------------------------------------------------------
SSTYP - ID type of SSID:
EQ.0: segment set ID for surface-to-surface contact,
EQ.1: shell element set ID for surface-to-surface contact,
EQ.2: part set ID,
EQ.3: part ID,
EQ.4: node set ID for node to surface contact,
EQ.5: include all for single surface definition.
EQ.6: part set ID for exempted parts. All non-exempted parts are included
in the contact.
For *AUTOMATIC_BEAMS_TO_SURFACE contact either a part set ID or a part ID
can be specified.
-------------------------------------------------------
A second example which illustrates null beams and type 26 contact:
http://ftp.lstc.com/anonymous/outgoing/jday/beam-to-hole-edge.k
-------------------------------------------------------
Some short notes of possible interest:
https://ftp.lstc.com/anonymous/outgoing/support/FAQ_docs/contact_shorter.pdf
https://www.dynasupport.com/tutorial/contact-modeling-in-ls-dyna/contact-types
https://www.dynasupport.com/tutorial/ls-dyna-users-guide/contact-modeling-in-ls-dyna
-------------------------------------------------------
Sincerely,
James M. Kennedy
KBS2 Inc.
August 26, 2024
--
You received this message because you are subscribed to the Google Groups "LS-DYNA2" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ls-dyna2+u...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ls-dyna2/b21936ef-a975-4a47-a7c3-3059252eb10cn%40googlegroups.com.
Samin Haeri
James Kennedy
Dear Samin,
------------------------------------------------
Interesting SPH particle spacing remarks:
Xu, J., Wang, J., and Souli, M., “SPH and ALE Formulations for Sloshing Tank Analysis”,
The International Journal of Multiphysics, Vol. 9, No. 3, pp. 209-224, September, 2015.
http://www.journal.multiphysics.org/index.php/IJM/article/view/9-3-209/251
Presentation can also be downloaded from the researchgate site,
------------------------------------------------
Some additional notes.
------------------------------------------------
Some recent comments I located.
Use contact_automatic_nodes_to_surface or contact_eroding_nodes_to surface,
depending on whether you'll ultimately be eroding solid structure or not. If
eroding_nodes_to_surface is necessary, it's advised NOT to use SMP, that is,
use MPP.
Use version R10.0 or later and set ITHK=1 on control_sph. This serves to
calculate the contact thickness automatically, based on the volume of each
SPH particle. In this case, the contact thickness of each particle is the cube
root of it's volume. (Think of the particle as a cube for purposes of contact
when ITHK=1.) SST on Card 3 of *CONTACT will override ITHK.
------------------------------------------------
Len Schwer has offered the following comments related to SPH mesh
refinement regarding a Lagrangian interface:
• I recommend a minimum of 4 (2x2) SPH particles per solid/shell segment,
with 9 (3x3) preferred for SPH to solid/shell contact, i.e. Nodes_to_Surface.
• This comment was offered with respect to tied contacts which also should
apply (see above comment) to other contacts.
------------------------------------------------
For your SPH contact, you can use either the contact_nodes_to_surface
or the contact_automatic_nodes_to_surface options.
To get the contact_automatic_nodes_to_surface to work properly, it
appears that you may need to specify a slave surface thickness, sst.
Some notes taken from Suri Bala's blog:
http://blog.d3view.com/2007/04/14/sph-contact-definitions/
http://ls-dyna-examples.blogspot.com/2009/12/sph-contact-definitions.html
Contact thickness for the SPH particles
When using automatic or non-automatic type one-way contacts, the
SPH particles have no associated contact thickness. The recommended
way to define the particle contact thickness is to use the 'SST'
parameter in the *CONTACT keyword or by using 'OPTT' parameter in
the *PART_CONTACT keyword. If the SPH particles are representing a
volume, then it may be suggested to use a resonable thickness to
avoid any nodal release due to excessive penetration. Typical values
of particle contact thickness when representing a volume is 0.8-1.0mm.
If the SPH particles are representing a shell type structure, then the
thickness of the shell can be used as the contact thickness.
It must be noted that there is no need for SINGLE_SURFACE type contacts
for defining the self interaction of SPH particles as they are accounted
for by the SPH formulation.
------------------------------------------------
Some further notes.
------------------------------------------------
Please make a simple hand check calculation of your SPH mass and make sure
that it agrees somewhat with the SPH mass calculated by LS-DYNA and given
in the "d3hsp" file.
Actually, this is advice to ALL who perform SPH simulations, especially
for 2D modeling. This should be checked to ensure correct mass modeling.
-----------------------------------------------
Perhaps the following notes on particle meshing might be of some help.
The smoothing length (h) and the mesh characteristic length (Dx) are the
two spatial parameters to determine spatial resolutions (only one spatial
discretization parameter is used in finite elements).
In LS-DYNA, the initial smoothing length is constant for each part and is
calculated as maximum value of all the minimum distance for each particle.
For example, if we have three particle, A, B, C, then first the distance to
the nearest particle is computed for all three particles. Lets assume the
shortest distances for the particles A, B, and C are AD, BD, and CD
respectively. The default smoothing length DSML is then taken as
CLSH*maximum of (AD, BD, and CD) where CLSH is a scale factor to the
initially computed smoothing length DSML can vary between HMIN * DSML
and HMAX * DSML as the simulation progresses. The computed smoothing
length at time zero is based on per part basis such that each part will have
one smoothing length for all the particles that belongs to that part. After
determining the initial smoothing length, it is recomputed every cycle
for each particle based on the divergence of the velocity and can vary
with respect to time and space.
Because of the lack of a numerical grid, care must be employed in setting
the initial particle masses and coordinates. The particle mesh needs to be
enough regular. This means that all the particles of a given neighborhood
need to have the same mass. As a consequence, the particles of a same
material, which have the same initial density, need to have the same initial
volume. To preserve this, they need to be distributed on a uniform mesh.
When two or more SPH materials are defined in the model, it is not necessary
to define a contact between SPH parts. The contact between the SPH materials
is formed through the internal forces computed from the overlapping of
smoothing lengths and the associated constitutive equations. This is
different from the conventional contact mechanism defined by the friction
model. Non-slip condition is in general not available.
However, if both SPH parts and finite elements are defined in the model, the
user needs to define a contact between the particles and the other elements.
The particles are considered as nodes. Therefore any NODES_TO_SURFACE
contact can be used. The original developer recommends the soft constraint
formulation (SOFT=1) for the contact. With the soft constraint option, the
interface stiffness is based on the nodal mass and the global time step of
the calculation.
** NOTE
The above two paragraphs are basically taken from a rather old presentation
by Lacome [2001] which may be somewhat outdated. Please review old and
new presentations!
http://www.dynalook.com/fea-newsletters/fea-newsletters-2001/fea-newsletter-november-2001.pdf
*section_sph entries do not require a thickness similar to that requested
for *section_shell entries. The thickness of the sph part will be defined
by your sph particle meshing.
------------------------------------------------
Two other comments that may be of interest, which I have seen in various
SPH notes:
1. It is usually best to keep the particle spacing constant/regular
throughout the domain.
2. For two different SPH parts, if possible, it is best to have the same
particle mass.
Please see "Chapter VII - SPH Use" in the short note by Jean Luc Lacome,
Smoothed Particle Hydrodynamics - Part II.
http://www.feapublications.com/pages/pdfnews/2001oct.pdf
http://www.feapublications.com/ (November - 2001)
------------------------------------------------
Sincerely,
James M. Kennedy
KBS2 Inc.
August 31, 2024
To view this discussion on the web visit https://groups.google.com/d/msgid/ls-dyna2/811e9385-a0d1-4860-bdd8-041a2d5f174an%40googlegroups.com.