output_control copy mrequest
Allows you to create a replica mrequest for a model. This mrequest is will be an exact copy of the original except the name. You may modify the replica without any harm done to the original.
Format:
output_control copy mrequest |
|---|
mrequest_name = | string |
new_mrequest_name = | string |
Example:
output_control copy mrequest & |
|---|
mrequest_name = | mrequest1 & |
new_mrequest_name = | mrequest2 |
Description:
Parameter | Value Type | Description |
|---|
mrequest_name | String | Specifies an existing mrequest. You may identify an mrequest by typing its name. |
new_mrequest_name | String | Specifies the name of the new mrequest. You may use this name later to refer to this mrequest. Adams View will not allow you to have two mrequests with the same name, so you must provide a unique name. |
Extended Definition:
1. The MREQUEST indicates multiple sets of data you want Adams to output. You can request sets of displacements, velocities, accelerations, or forces for system elements such as parts, joints, joint primitives, or applied forces in your system.
Except for rotational displacements, all the information types are vectors. For example, joint velocities are actually translational and rotational velocity difference vectors of the joint I marker with respect to the joint J marker. Joint accelerations are actually translational and rotational acceleration difference vectors of the joint I marker with respect to the joint J marker. In other words, if V is a translational vector quantity and W is a rotational vector quantity,
Vij = Vi - Vj,
and Wij = Wi - Wj
V'ij = V'i - V'j
and W'ij = W'i - W'j
Because two markers (I and J) define each joint, joint primitive, and applied force, Adams measures the request information for one of these at the I marker with respect to the J marker. Because a center-of-mass marker is the only marker that is necessary to define a part, Adams measures the request information for a part at its center-of-mass marker with respect to ground or with respect to an alternative marker you specify. Regardless of the system information you want, you can use a reference marker (R_MARKER_NAME) to resolve the component information into any coordinate system you wish. Note that the units for rotational displacement data in the request output of the tabular output file default to degrees. The units for all other angular output data default to radians.
2. You may identify a mrequest by typing its name. If you created the mrequest by reading an Adams data set or graphics file, the mrequest name is the letters MRE followed by the Adams data set mrequest ID number. For example, the name of Adams MREQ/101 is MRE101. If you created the mrequest during preprocessing, you will have given it a name at that time. If an mrequest is available by default, you may identify it by entering only its name. If it is not, you must enter its full name. To identify a mrequest under another analysis, for instance, you may need to enter the analysis name as well. For example, you may specify mrequest 101 from the analysis named test by entering ".test.mre101". You must separate multiple mrequest names by commas.
3. Normally, entity names are composed of alphabetic, numeric, or '_' (underscore) characters, and start with an alphabetic or '_' character. They may be of any length. For more information, see
Using Extended Names.
By enclosing the name in double quotes, you may use other printable characters, or start the name with a numeral. If a name contains characters, or starts with a numeral, you must always quote the name when entering it. Note that you can specify the parentage of an entity (e.g. what part "owns" a marker or a geometry element) when you CREATE it by changing the name. If you enter just the entity name, then the default parent will be assigned by Adams View. If you type in the full name, then you may override the default parent. In most cases, when creating an entity, Adams View will provide a default name. The default name that Adams View provides will specify the parentage that it has assumed. You may, of course, delete this name and use your own. The form of a full name is:
"...._NAME.GRAND_PARENT_NAME.PARENT_NAME.ENTITY_NAME"
The number of levels used varies from case to case and the parentage must exist before an entity can be assigned to it.
Cautions:
1. Adams View will not allow you to have two mrequests with the same name, so you must provide a unique name for the new request to be created.
Tips:
1. If you type a "?", Adams View will list the mrequests available by default.