Excitations in cloned or copied events

When you clone or copy an event from one Response Dynamics solution process to another, all excitations that are consistent with the modal solution are copied along with the event. Results are not copied.

Excitations are considered inconsistent when:

• The excitation was defined on an enforced motion or distributed load, and the target solution process does not include enforced motion modes or distributed modes.

• The degrees of freedom for the excitation are missing or are no longer valid.

• The finite element mesh has been changed and the excitation is defined on nodes that no longer exist.Caution: If the mesh has changed, an excitation may be applied to an incorrect location in the model. For example, suppose you applied an excitation to node 10 at the corner of the model. After you change the mesh, node 10 is now in the center of the model. In this case, the excitation will be preserved; however, it is no longer applied to the same physical location on the model. You must ensure that excitations are correct after you change the mesh.

How do I

Create an event

Clone an event

Copy an event from one Response Dynamics solution process to another

Set up sequential transient events

DDAM reference acceleration and velocity

Define multipliers to adjust the standard DDAM shock coefficients

Define custom DDAM shock coefficients

Learn more

Events

Data recovery

Required modes for each event type

Sequential transient events (continuation restart)

Quasi-Static events

Quick links

Command reference

Pre/Post video examples

Bulk Entry Descriptions

Simcenter 3D tutorials

Browse Simcenter 3D help by product area

Excitations in cloned or copied events, 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 } });