floating_marker modify
Allows modifying of a floating marker.
Floating marker specifies a site for applying forces or constraints to parts. The force or constraint dictates the location and orientation of the floating marker. Therefore, you do not specify a position for a floating marker. This allows the floating marker’s location and orientation to change with respect to its body coordinate system during the simulation, as dictated by the force or constraint.
Format:
floating_marker modify |
|---|
floating_marker_name = | an existing fmarker |
new_floating_marker_name = | a new floating marker |
adams_id = | adams_id |
node_ID = | integer |
comments = | string |
Example:
floating_marker modify & |
|---|
floating_marker_name = | .model_1.PART_3.FMARKER_12 & |
new_floating_marker_name = | .model_1.PART_3.FMARKER_13 & |
adams_id = | 12 & |
node_id = | 10 & |
comments = | floating_marker_for_part_3 |
Description:
Parameter | Value Type | Description |
|---|
floating_marker_name | An Existing Fmarker | Specifies the name of an existing floating marker |
new_floating_marker_name | A New Fmarker | Specifies a new name for an existing floating marker |
adams_id | Adams_id | Specifies an integer used to identify this element in Adams database |
node_id | Integer | Specifies an integer used to identify a node for a flexible body |
comments | String | Specifies the comments if any for the new floating marker |
Extended Definition:
1. The floating marker has no position specified. The position and orientation of the floating marker changes while simulation according to the mode of application of force or constraint or location of the force on the moving body. For example, the orientation of the force may be set as moving with the body, fixed in space or between two bodies, which decides the position and orientation of the force while simulation.
The ‘adams_id’ specifies an integer used to identify this element in the Adams data file. When you use the FILE ADAMS_DATA_SET WRITE command, Adams View writes an Adams data file for your model. Adams requires that each modeling element be identified by a unique integer identifier. If you use this parameter to specify a non-zero identifier, Adams View will use it in the corresponding statement in the Adams data file.
You may also enter zero as an identifier, either explicitly or by default. The next time you write an Adams file, Adams View will replace the zero with a unique, internally-generated identifier. Adams View will permanently store this identifier with the element just as if you had entered it yourself. Normally, you would let all identifiers default to zero, and Adams View would generate the identifiers for you. You are never required to enter a non-zero identifier. You only need to specify it if, for some reason, you wish to control the Adams file output.
2. The ‘comment’ specifies comments for the object being created or modified. When an Adams Solver data file (.adm) is read into Adams View, all comments associated with a statement (from the end of the previous statement through the end of the current statement) are stored with the object. Comments in the data file can be associated with model. These comments must follow the title statement and be followed by the comment 'END OF MODEL COMMENTS'. This string must be uppercase. When an Adams Solver data file is written, the comments for an object are written before the statement corresponding to the object. The ‘node_id’ refers to the attachement point of node on a flexible body.
3. When applied to flexible bodies, a floating marker can be either associated with a node or not (via the “node_id” argument). Because a floating marker is often moving across the body to which it belongs, it typically does not make sense to associate a flexible body’s floating marker with any particular node. Be advised, that this means the reaction loads from the force object which the floating marker supports will be applied to the rigid body motion of the flexible body and not on a modal basis deforming the part locally at the nodes near the force application point.