output_control create request

Allows you to create a replica request. This replica request will be an exact copy of the original with the exception of the name.
A REQUEST indicates a set of data you want Adams to output. Using a REQUEST, you can output a set of displacements, velocities, forces, or accelerations, with respect to markers in your system; or you can use the user-written subroutine REQSUB to define nonstandard output.
Adams calculates all data in the ground reference frame, although you can specify that the data be resolved in another reference frame. This is of no importance in the case of force data, but it can be very important in the case of displacements and time derivatives, that is, velocities and accelerations.
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
Note that the units for rotational displacement data in the request output of the tabular file default to degrees. The units for all other angular output data defaults to radians.

Format:

 
output_control create &
request_name =
.model_name.request_name&
adams_id=
geom._id&
comment =
string&
component_names =
string&
component_units =
string&
component_labels =
string&
results_name =
string&
title =
string&
output_type =
displacement/velocity/acceleration/force&
i_marker_name =
marker_name&
j_marker_name =
marker_name&
r_marker_name =
marker_name&
user_function =
real number&
f1 =
run time function&
f2 =
run time function&
f3 =
run time function&
f4 =
run time function&
f5 =
run time function&
f6 =
run time function&
f7 =
run time function&
f8 =
run time function&
variable_name =
variable name&
routine =
string

Description:

 
Parameter
Value Type
Description
Request_name
String
Specifies the name of the new request to be created. You may later identify a request by typing its name.
Adams_id
Integer
Specifies an integer used to identify this element in the Adams data file.
Output_type
Displacement/velocity/acceleration/force/user
Specifies whether you want the request to output displacement, velocity, acceleration, force, or user data.
I_marker_name
An existing triad
Specifies the marker for which you wish Adams to generate data.
J_marker_name
An existing triad
Specifies the marker with respect to which you wish Adams to generate the data.
R_marker_name
An existing triad
Specifies the marker with respect to which you want Adams to resolve the data. Adams computes the data identified by the I and J markers, then reports the data as x, y, and z components in the reference frame of the reference marker. Angular displacements, which are not vectors, are not affected by reference marker. If you do not supply this parameter, Adams will resolve the data in the ground reference frame.
Comment
String
Specifies a comment for the request. The comment can contain up to 80 characters, and can be comprised of letters of the alphabet (a-z, A-Z), numbers (0-9), and underscores. You may also use spaces and special characters (*&^%$#) if you enclose the comment in quotation marks.
Examples:
comment=the_first_request
comment="Displacement of wheel center 1 wrt ground"
User_function
Real
Specifies up to 30 values for Adams to pass to a user-written subroutine. See the Adams User's Manual for information on writing user-written subroutines.
Title
String
Specifies any of the eight alphanumeric headings for columns of request output in the request file.
Note: Enter function expressions in the boxes f2, f3, f4, f6, f7, and f8. Do not use f1 and f5. Adams Solver uses them to hold magnitudes for the three functions that follow. You do not need to enter a function in every text box.
F1
Function
Specifies the function expression that is the first component of the request that is being created or modified. The f1 parameter allows you to generate user-defined output variables and have them reported by Adams to the request file.
F2
Function
Specifies the function expression that is the second component of the request that is being created or modified. The f2 parameter allows you to generate user-defined output variables and have them reported by Adams to the request file.
F3
Function
Specifies the function expression that is the third component of the request that is being created or modified. The f3 parameter allows you to generate user-defined output variables and have them reported by Adams to the request file.
F4
Function
Specifies the function expression that is the fourth component of the request that is being created or modified. The f4 parameter allows you to generate user-defined output variables and have them reported by Adams to the request file.
F5
Function
Specifies the function expression that is the fifth component of the request that is being created or modified. The f5 parameter allows you to generate user-defined output variables and have them reported by Adams to the request file.
F6
Function
Specifies the function expression that is the sixth component of the request that is being created or modified. The f6 parameter allows you to generate user-defined output variables and have them reported by Adams to the request file.
F7
Function
Specifies the function expression that is the Seventh component of the request that is being created or modified. The f7 parameter allows you to generate user-defined output variables and have them reported by Adams to the request file.
F8
Function
Specifies the function expression that is the eight component of the request that is being created or modified. The f8 parameter allows you to generate user-defined output variables and have them reported by Adams to the request file.
Routine
String
Specifies an alternative library and name for the user subroutine REQSUB.
Component_names
String
This option is available only for XML format. By default, there are eight components per results set, and they have generic names, such as X, Y, Z, and MAG. You can specify more descriptive names for them or specify a particular unit label or unit type associated with each component.
Component_units
String
This option is available only for XML format. Specify the unit dimension of the result set components. If you do not specify units, then the units of the components are predefined based upon standard request type (For example, length, velocity and acceleration)
Component_labels
String
This option is available only for XML format. Specify the labels to be used when plotting the result set components. Labels can be strings that include white space. Quotes must be used to define the string if you see special characters or white space.
Results_name
String
Specifies the name of the results set in which all result set components are placed. If there is an existing result set with this name, then the result set components are placed in that result set.
Variable_name
String
Specifies one or more variables that represent the components associates with a request. This option is only available if the format of the results files is set to XML.

Extended Definition:

1. Normally, request 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 (for example, 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.
2. 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.
3. You may choose one of the following values for the output_type.
a. DISPLACEMENT
Adams outputs the displacement of the I marker with respect to the J marker. This argument generates eight headings and eight columns of output. The columns include the time (Time), the translational magnitude (Mag), the x component (X), the y component (Y), the z component (Z), the psi angle (Psi), the theta angle (Theta), and the phi angle (Phi).
The psi, theta, and phi angles are the Euler angle displacements of the I marker with respect to the J marker. Adams calculates this displacement data in the global coordinate system. If you specify R_MARKER_NAME, Adams resolves the translational x component, the translational y component, and the translational z component in the coordinate system of the R marker. The R marker does not affect psi, theta, and phi.
If you enter the 'OUTPUT_CONTROL SET OUTPUT YPR=ON' command, psi, theta, and phi rotations become yaw, pitch, and roll rotations.
Rotational displacement information differs from all other standard output. Whether this information is in psi, theta, and phi coordinates or in yaw, pitch, and roll coordinates, the rotation sequence is not a vector. As a result, Adams outputs no magnitude column. In addition, the sequence of coordinates is independent of any frame external to the I and the J markers. Therefore, the R_MARKER_NAME parameter has no effect on the angular coordinates.
b. VELOCITY
Adams outputs the velocity of the I marker with respect to the J marker. This argument generates nine headings and nine columns of data for velocity. The nine columns include the time (Time), the translational magnitude (Vm), the translational x component (Vx), the translational y component (Vy), the translational z component (Vz), the rotational magnitude (Wm), the rotational x component (Wx), the rotational y component (Wy), and the rotational z component (Wz).
Adams calculates this velocity data (the first derivative of the displacement of the I marker with respect to the J marker) in the global coordinate system. If you specify R_MARKER_NAME, Adams resolves the translational x component, the translational y component, the translational z component, the rotational x component, the rotational y component, and the rotational z component in the coordinate system of the R marker.
c. ACCELERATION
Adams outputs the acceleration of the I marker with respect to the J marker. This argument generates nine headings and nine columns of output. The columns include the time (Time), the magnitude of translational acceleration (Accm), the translational x component (Accx), the translational y component (Accy), the translational z component (Accz), the magnitude of rotational acceleration (Wmdot), the rotational x component (Wxdot), the rotational y component (Wydot), and the rotational z component (Wzdot). Adams calculates this acceleration data (the second derivative of the displacement of the I marker with respect to the J marker) in the global coordinate system. If you specify R_MARKER_NAME, Adams resolves the translational x component, the translational y component, the translational z component, the rotational x component, the rotational y component, and the rotational z component in the coordinate system of the R marker.
d. FORCE
Adams outputs the force associated with the I and the J markers or, if only the I marker is given, outputs the action-only forces on the I marker. When both, the I and the J markers are given, Adams sums the forces on the I marker of those forces associated with the I and the J markers. These forces can include both, applied forces (such as SPRINGDAMPERs and BUSHINGs) and reaction forces from constraint elements (such as JOINTs and MOTIONs). When only the I marker is given, Adams sums all of the action-only forces that are applied to the I marker. Adams reports the components of the resulting vectors in the reference frame of the R marker if you specify R_MARKER_NAME.
If you do not specify R_MARKER_NAME, Adams reports the components in the ground reference frame. This argument generates nine columns of output. The columns include the time, the translational force magnitude, the three components of the translational force, the rotational force (torque) magnitude, and the three components of the torque.
Applied forces and torques are those generated by beams, bushings, fields, single-component forces, and spring-dampers. Adams outputs the applied forces and torques acting at the request I marker (which may be either the applied force I marker or the applied force J marker). The magnitude and point of force application on the part containing the applied force J marker varies according to the type and source of the force. For spring-dampers and action-reaction single-component forces, the forces and torques acting at the J marker are equal and opposite to the forces and torques acting at the I marker. For action-only single-component forces, there is no force or torque acting at the applied force J marker. For beams, fields, and bushings, the forces acting at the applied force J marker are equal and opposite to the forces acting at the applied force I marker. As long as the applied force I marker and the applied force J marker are coincident, the torques acting at the applied force J marker are equal and opposite to the torques acting at the applied force I marker. If there is a finite separation between the I and the J markers, the torques acting at the applied force J marker are opposite, but not equal, to the torques acting at the applied force I marker.
Reaction forces and torques are those generated by constraint-inducing elements. For revolute, spherical, and universal joints and for atpoint, orientation, parallel axes, and perpendicular joint primitives, Adams outputs the reaction forces and torques acting at the request I marker (which may be either the constraint I marker or the constraint J marker). The force and torque acting at the request J marker are equal and opposite to the force and torque acting at the request I marker. Depending on the type of constraint, some or all of the torques acting at the I marker are zero.
You must be careful when requesting a force with the I and the J markers reversed from those specified in the force-producing element. Adams reports the force as if it were applied to the J marker of the force-producing element. The translational force on the J marker of the force element will be equal and opposite to the translational force on the I marker of the force element if it is not action only. The force will be zero if it is action only. The torque on the J marker of the force element has an extra component that may have significance. The torque is the sum of two contributions. The first contribution is the opposite of the torque on the I marker. The second contribution is due to the force acting across the separation between the I and the J markers. If the force acts along the line of sight of the two markers, this extra torque will be zero. To minimize misunderstandings, attach your REQUEST markers in the same order as the markers on the force-producing element.
e. USER
Adams will output the values computed by the user-written subroutine REQSUB. If you choose a USER request type, you must also supply the USER_FUNCTION parameter to define the constants Adams will pass to the REQSUB.
4. If you are requesting displacement, velocity, or acceleration data, you must supply the J_marker. Adams will measure the displacement, velocity, or acceleration of the I marker with respect to the J marker.
If you are requesting force data for action-reaction forces, you must supply the J marker. Adams will sum the forces on the I marker of those forces associated with the I and J markers.
If you are requesting force data for action-only forces, do not supply the parameter, J_marker. Adams will sum all of the action-only forces applied to the I marker.
5. Each title heading can have as many as eight alphanumeric characters, and underscores. No leading or internal white-space characters are allowed. The first character in each heading must be alphabetic. You can use all alphanumeric characters. You cannot use the comma (,), the semicolon (;), the ampersand (&), or the exclamation point (!). These are limitations dictated by the Adams data-set parser. If you do not want to specify a title for a particular column, use two quotation marks with no characters in between the quotations marks.
If you want to unset all of the titles, use only two quotation marks with no characters in between the quotations marks ("").
Examples:
title = First, Second,"", DISP_X, Last, ANG_disp, AMAG, ""
6. To enter a function expression, you enter a series of quoted strings.
The easiest way to enter a function expression in Adams View is to use the text editor in combination with the function builder. To invoke the text editor for entering a function expression, highlight the function field and then either pick the "EDIT" button at the top of the panel or type a ^t (control-t). The Adams View "function builder" is discussed below.
The syntactical correctness of a function expression can be investigated by using the "VERIFY" button at the upper right side of the text editor. If there is a syntax error, a message is printed and the cursor is put near the problem. Proper unit consistency is not checked during function expression verification.
The remainder of this explanation will cover the components of FUNCTION expressions as summarized in the following table.
 
Components
Examples
Numbers
FUNCTION = 1E2 + 3.4 + 6
Operators
FUNCTION = 3*6/2 + 3 - 2**2
System constants
FUNCTION = PI + 20
System variables
FUNCTION = AX(1040, 2010)
Arithmetic IFs
FUNCTION = IF(DX(3, 5): -1, 0, 1)
FORTRAN-77 functions
FUNCTION = ABS(NUM) - 6
Blanks
FUNCTION = 1 + 2
Continuation commas
FUNCTION = 1 + 1 + 1 + 1 + 1 + 1, + 1 + 1 + 1 + 1 + 1 + 1 + 1
Adams functions
FUNCTION = POLY(0, 0, 6.28)
NUMBERS
FUNCTION expressions can include integers, real numbers, and exponents. In other words, any numbers that are legal in Adams are legal in a FUNCTION expression.
OPERATORS
In a FUNCTION expression, Adams allows any of the operators **, *, /, +, and -. Adams executes these operators according to the following precedence rules:
From greatest to least, the operators have the following priorities. ** then * / then + -. In other words, Adams executes exponentiation (**) before all other operators and executes multiplication (*) and division (/) before addition (+) and subtraction (-).
When a statement has operators of the same priority, Adams executes them from left to right.
You can use parentheses to alter the precedence of operators.
For example, in the equation
FUNCTION = (1-TIME)*30/PI
Adams subtracts TIME from one before it performs multiplication and division.
SYSTEM CONSTANTS
You can include the following system constants in a FUNCTION expression:
 
PI
Value of pi (to eighteen significant digits)
DTOR
Value of pi/180 for converting degrees to radians
RTOD
Value of 180/pi for converting radians to degrees
The following example of a FUNCTION with a system constant multiplies the system constant PI by the displacement of marker 10 with respect to marker 14:
FUNCTION = PI*DM(10,14)
BLANKS
A FUNCTION expression can contain any number of blank spaces. Five consecutive blank spaces in an expression do not terminate input of the expression (by indicating that what follows is a comment) as they do in an Adams statement. However, you should remember these two restrictions.
You cannot put a blank space in the middle of a number.
Adams does not accept a blank space between a function and its left bracket. (This is true for both FORTRAN-77 functions and Adams functions.)
CONTINUATION COMMAS
You can use a comma to continue FUNCTION expressions. You can break the expression anywhere except in the middle of a number, in the middle of a name, or between a function and its left bracket. Put a continuation comma in column one of the following line before the rest of the expression. If you break the expression at a comma that is part of the expression, you must use both the expression comma and the continuation comma. You may use more than one continuation comma to extend an expression over several lines.
FUNCTION BUILDER
The FUNCTIONS button at the right side of the Adams View text editor provides a means of constructing an Adams function string. These functions are briefly described below. Upon picking the FUNCTIONS button, you will be presented with the list of available functions in the "selection window". After you select the desired function, a panel will appear with fields representing the various parameters for the function. You will have full access to on-line help with this panel just like you have with regular panels. After you have completed the panel and selected the DONE button on the panel, the function string will be constructed and inserted at the current text cursor location in the text edit window.
SYSTEM VARIABLES
A FUNCTION expression may access the current value of a system variable and use the value in computations. These values are accessed through a collection of functions. The accessible system variables include the following: Time, Mode, Displacements (Translational and Rotational), Velocities (Translational and Rotational), Accelerations (Translational and Rotational), Forces (Translational and Rotational), and User-defined variables. Invoke the text edit window and pick the FUNCTIONS button to get a list of functions that can be accessed.
In general, you use a function character string (such as DM, VX, or FZ) and a list of values (e.g. i1, i2, and i3) to access a system variable in an expression. For example, the value i1 may be the name of the marker for which you want to measure a quantity (such as displacement, velocity, acceleration, or force), i2 is the name of the marker with respect to which you want to measure the quantity, and i3 is the name of the marker you want to use to resolve the components of the quantity. If you do not specify marker i3, Adams computes the result in the ground reference frame.
ARITHMETIC IFS
Arithmetic IFs allow you to conditionally define FUNCTION. The format for arithmetic IFs follows.
IF (expression 1: expression 2, expression 3, expression 4)
Adams evaluates expression 1. If expression 1 is less than zero, the arithmetic IF equals expression 2; if expression 1 equals zero, the arithmetic IF equals expression 3; and if expression 1 is greater than zero, the arithmetic IF equals expression 4.
A FUNCTION expression with an arithmetic IF and its four expressions is below.
FUNCTION = 6 * IF(VR(10,31): 0, 0, 100)
If the radial velocity between markers 10 and 31 is less than or equal to zero, the value of the FUNCTION expression is zero; but if the radial velocity between markers 10 and 31 is greater than zero, the value of the FUNCTION expression is six hundred.
In some ways, you may treat IF as a variable. For example, you can place it anywhere in the expression. In addition, you can nest arithmetic IFs nine levels deep.
FORTRAN-77 FUNCTIONS
You can use the FORTRAN functions ABS, ATAN, ATAN2, COS, EXP, LOG, LOG10, MIN, MAX, SIN, SQRT, and TAN in your expression. For more information about these functions, see a FORTRAN reference manual. Invoke the text edit window and pick the FUNCTIONS button to get a list of functions that can be accessed.
Adams FUNCTIONS
In general, an Adams function evaluates a mathematical equation and returns a value to your FUNCTION expression. he following table lists all the Adams functions and their purposes. Invoke the text edit window and pick the FUNCTIONS button to get a list of functions that can be accessed.
 
Names
Purposes
AKISPL
Accesses the data in a SPLINE statement and uses the Akima cubic method to fit a cubic curve (a spline) to the data.
BISTOP
Evaluates a force restricting displacement of a part in two opposite directions.
CHEBY
Evaluates a Chebyshev polynomial
CUBSPL
Accesses the data in a SPLINE statement and uses the traditional cubic method to fit a cubic curve (a spline) to the data.
FORCOS
Evaluates a Fourier cosine series
FORSIN
Evaluates a Fourier sine series
HAVSIN
Evaluates a haversine function.
IMPACT
Evaluates a force restricting displacement of a part in one direction.
POLY
Evaluates a polynomial.
SHF
Evaluates a simple harmonic function.
STEP
Approximates a step function with a cubic polynomial.
7. Result sets are helpful if you want to group the output from multiple requests into a single results set. For example, you might have several different requests measuring driver input for a vehicle, and you might want to place them all within a result set named Driver_Inputs for easier viewing in Adams PostProcessor.
8. Units for component_labels may be:
 
MASS
AREA
TIME
VOLUME
FORCE
TORQUE
LENGTH
PRESSURE
VELOCITY
DENSITY
ACCELERATION
ENERGY
ANGLE
TORSION_STIFFNESS
ANGULAR_VELOCITY
TORSION_DAMPING
ANGULAR_ACCELERATION
FREQUENCY
INERTIA
AREA_INERTIA
STIFFNESS
FORCE_TIME
DAMPING
TORQUE_TIME