I assume you used a Part, or Part Set, ID for the master side of your eroding nodes to surface. Internally, LS-DYNA will determine segments of the specified parts.
Perhaps try defining the segment set and use MSTYP=0
You could also try *CONTROL_STRUCTURED and look at the input LS-DYNA generates from your LS=PrePost input.
--len
--
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/5dfabfd8-136c-4cac-9322-d915799f4b1bn%40googlegroups.com.
Dear Yash,
A “Contacts Checks” discussion (actually a tool developed by ANSA) that may be of help
The contacts check functionality detects various possible errors of the contact definitions.
The validity of the SETs defined as master and slave in the contact. Empty sets, sets with free nodes, and nodes used only by segments are flagged by the tool.
In case of TIED contacts, incorrect definition and definitions with prohibitive distances between the participating entities are detected. Automatic fixes are available to facilitate the correction of the model.
Common entities on slave and master areas (SETs) of a contact are identified and listed. Visibility functions can help the user to isolate and work with each identified error.
Slave nodes of connection should always be attached to a master segment. The Check>Contacts function identifies the errors and previews them on the model.
The most important contact check is the identification of contact thickness penetration. The tool identifies the violating areas per LS-DYNA requirements and presents them to the user. An automatic fix is available that fixes these penetrations fast and accurately
Sincerely,
James M. Kennedy
KBS2 Inc.
June 27, 2021
To view this discussion on the web visit https://groups.google.com/d/msgid/ls-dyna2/001601d76b5c%24d3b840b0%247b28c210%24%40schwer.net.