Examples of enabling or disabling contact and glue simulation objects in subcases (Simcenter Samcef)

Example 1: enabling and disabling

Objects in the Simulation Navigator:

Ramps effect details:

Simcenter Samcef input file:

.MCT I 1 $ NAME "Face Contact(1)" $....SUB I 0 DISABLE "MCT" I 1 I 1 NAME "Subcase - Nonlinear 1"     TIMP 0 10 I 2 NAME "Subcase - Nonlinear 2"     TIMP 10 20     ENABLE "MCT" I 1 I 3 NAME "Subcase - Nonlinear 3"     TIMP 20 30 I 4 NAME "Subcase - Nonlinear 4"     TIMP 30 40 I 5 NAME "Subcase - Nonlinear 5"     TIMP 40 50     DISABLE "MCT" I 1

Note:

Because the contact is enabled only in the second subcase, we need to disabled it from the beginning of the computation (Samcef SUBCASE 0).

Because the disabled state remains active until a change, there is no need for Simcenter Samcef solvers to repeat the disabled state in the subcase 1.

Note:

Because by default, a simulation object that is enabled remains enabled, either until being disabled or until the end of the computation, there is no need for Simcenter Samcef solvers to repeat the ENABLE "MCT" I 1 sequence in the subcases 3 and 4.

Example 2: disabling only

Objects in the Simulation Navigator tree:

Ramps effect details:

Simcenter Samcef input file:

.STICK I 1 $ NAME "Surface-to-Surface Gluing(1)" $ GROUP "STICK_Surface-to-Surface Gluing(1)_1_NODE" "2d_mesh(1)_0"....SUB I 1 NAME "Subcase - Nonlinear 1"     TIMP 0 10 I 2 NAME "Subcase - Nonlinear 2"     TIMP 10 20 I 3 NAME "Subcase - Nonlinear 3"     TIMP 20 30 I 4 NAME "Subcase - Nonlinear 4"     DISABLE “STI” I 1     TIMP 30 40 I 5 NAME "Subcase - Nonlinear 5"     TIMP 40 50

Note:

The Surface-to-Surface Gluing(1) gluing is enabled since the first subcase by default, so there is no need for Simcenter Samcef solvers to mention its enabled state in all the subcases prior to the disable action.

Note:

Because the disabled state remains active until a change, there is no need for Simcenter Samcef solvers to repeat the disabled state in the subcase 5.

Example 3: adding a final subcase to a solution

Objects in the Simulation Navigator:

Ramps effect details:

Simcenter Samcef input file:

.MCT I 1 $ NAME "Face Contact(1)" $....SUB I 0 DISABLE "MCT" I 1 I 1 NAME "Subcase - Nonlinear 1"     TIMP 0 10 I 2 NAME "Subcase - Nonlinear 2"     TIMP 10 20     ENABLE "MCT" I 1 I 3 NAME "Subcase - Nonlinear 3"     TIMP 20 30 I 4 NAME "Subcase - Nonlinear 4"     TIMP 30 40

Now, we simply add an extra subcase 5 to the solution.

Objects in the Simulation Navigator:

Due to the new empty subcase 5 (1), the ramp effects appear:

Simcenter Samcef input file:

.MCT I 1 $ NAME "Face Contact(1)" $....SUB I 0 DISABLE "MCT" I 1 I 1 NAME "Subcase - Nonlinear 1"     TIMP 0 10 I 2 NAME "Subcase - Nonlinear 2"     TIMP 10 20     ENABLE "MCT" I 1 I 3 NAME "Subcase - Nonlinear 3"     TIMP 20 30 I 4 NAME "Subcase - Nonlinear 4"     TIMP 30 40 I 5 NAME "Subcase - Nonlinear 5"     TIMP 40 50     DISABLE "MCT" I 1

Learn more

Enabling or disabling elements in subcases (Simcenter Samcef)

Controlling the birth and death times of elements in nonlinear and thermal analyses (Simcenter Samcef)

Enabling or disabling contact and glue simulation objects in subcases (Simcenter Samcef)

Global remarks and limitations when enabling or disabling entities (Simcenter Samcef)

Quick links

Command reference

Pre/Post video examples

Bulk Entry Descriptions

Simcenter 3D tutorials

Browse Simcenter 3D help by product area

Examples of enabling or disabling contact and glue simulation objects in subcases (Simcenter Samcef), Simcenter 3D 2021.1 Series

© 2020 Siemens

window.mainLanguage="en_US"

window.delivId=""

window.projectId=""

MathJax.Hub.Config({ TeX: { extensions: ["autoload-all.js"] }, tex2jax: { displayMath: [ ] }, "SVG": { scale: 125 } });