numeric_results create differentiation
Allows you to calculate the derivative function of an existing result set component.
Format:
numeric_results create differentiation |
|---|
result_set_component_names = | 2 existing components |
new_result_set_component_name = | a new component |
units = | units_type_with_calc |
Example:
numeric_results create differentiation & |
|---|
result_set_component_names = | rsc1,rsc2 & |
new_result_set_component_name = | rsc__3 & |
units = | time |
Description:
Parameter | Value Type | Description |
|---|
result_set_component_names | An Existing Component | Identifies two result-set components to perform the operation on. |
new_result_set_component_name | A New Component | Allows you to identify where the new data components are to be stored. |
units | Units_Type_With_Calc | Allows you to specify the type of units to be used for the new result set component. |
Extended Definition:
5. This operation numerically differentiates the result set component data over the closed interval represented by its finite set of data points.
The derivative is evaluated by fitting a cubic spline to the result set component data and analytically forming the derivative. In other words, the cubic spline fit gives a polynomial representation of the segments that represent the data. This polynomial in then analytically differentiated over the closed interval of the data.
6. The components must be in an existing result set and reference to the component must include the result set name. For example, assume you have read a request file called "SHIFT.REQ", and this request file contains the result set REQ1. If you wish to refer to the X component in the result set REQ1, enter .SHIFT.REQ1.X (the .SHIFT. may be omitted if shift is the current analysis_name). SHIFT refers to the analysis name that result set came from (or is stored under).
Result Sets are associated with an analysis run and can be identified as such. A result set associated with request 101 from an analysis named "test" is referred to as .test.req101.
Several predefined result set types are created when Adams request and result files are read into Adams View. For example, assume you have read a request file called "SHIFT.REQ", and this request file contains the result information for the Adams statement REQUEST/1. The result set will be named REQ1, and may also be referred to as being relative to the analysis name .shift.req1. If you wish to refer to a component in the same result set the full name for the X component would be .SHIFT.REQ1.X.
The following table illustrates the default names assigned to result sets and result set components read from request (.REQ) and results (.RES) files.
Result set type | Result set name | Component names | File that result is from |
|---|
part | PARxxx... | x y z e1 e2 e3 e4 mag vx vy vz wx wy wz accx accy accz wdx wdy wdz | results file |
diff | DIFxxx... | q dq | results file |
joint | JOIxxx... | fx fy fz tx ty tz fmag tmag | results file |
jprim | JPRxxx... | fx fy fz tx ty tz fmag tmag | results file |
motion | MOTxxx... | fx fy fz tx ty tz fmag tmag | results file |
gear | GEAxxx... | fx fy fz | results file |
coupler | COUxxx... | fx1 fy1 fz1 tx1 ty1 tz1 fmag1 tmag1 fx2 fy2 fz2 tx2 ty2 tz2 fmag2 tmag2 fx3 fy3 fz3 tx3 ty3 tz3 fmag3 tmag3 | results file |
sforce | SFOxxx... | fx fy fz tx ty tz fmag tmag | results file |
spring damp | SPRxxx... | fx fy fz tx ty tz fmag tmag | results file |
bushing | BUSxxx... | fx fy fz tx ty tz fmag tmag | results file |
beam | BEAxxx... | fx fy fz tx ty tz fmag tmag | results file |
field | FIExxx... | fx fy fz tx ty tz fmag tmag | results file |
user request | UREQxxx... | u1 u2 u3 u4 u5 u6 u7 u8 | results file |
request | REQxxx... | x y z r1 r2 r3 mag amag | request file |
ucon | (not implemented) | | |
If one component is complex, and the other is real, the real component is promoted to complex. If the two components are different lengths, the longer one is truncated (only for that operation).
If the new component being created is complex, a MAGNITUDE component is automatically generated. If the component is being added to an existing result set and a MAGNITUDE component already exits, an error will be issued.
7. If the component is to be stored in an existing result set, then the name entered must include the result set. For example, assume you have read a request file called "SHIFT.REQ", and this request file contains the result set REQ1. If you wish to store the new result set component in result set REQ1 with the component name NEW, enter .SHIFT.REQ1.NEW (The .SHIFT. can be left off if SHIFT is the "current" analysis_name). If you wish to store the component in a new result set named REQ99 in the analysis run SHIFT, enter .SHIFT.REQ99.NEW. The number of components to be stored is inferred by the number of components named in this parameter. Multiple names can be entered separated by commas (,).
This is a required parameter and the component name given must be unique even though it may be stored in an existing result set. A result set name may be arbitrarily long and a combination of letters of the alphabet and numbers may be used. The leading character must be a letter.
Result Sets are associated with an analysis run and can be identified as such. A result set associated with request 101 from an analysis named "test" is referred to as .test.req101.
Several predefined result set types are created when Adams request and result files are read into Adams View. For example, assume you have read a request file called "SHIFT.REQ", and this request file contains the result information for the Adams statement REQUEST/1. The result set will be named REQ1, and may also be referred to relatives of the analysis name .shift.req1. If you wish to refer to a component in the same result set, the full name for the X component would be .SHIFT.REQ1.X.
The following table illustrates the default names assigned to result sets and result set components read from request (.REQ) and results (.RES) files.
Result set type | Result set name | Component names | File that result is from |
|---|
part | PARxxx... | x y z e1 e2 e3 e4 mag vx vy vz wx wy wz accx accy accz wdx wdy wdz | results file |
diff | DIFxxx... | q dq | results file |
joint | JOIxxx... | fx fy fz tx ty tz fmag tmag | results file |
jprim | JPRxxx... | fx fy fz tx ty tz fmag tmag | results file |
motion | MOTxxx... | fx fy fz tx ty tz fmag tmag | results file |
gear | GEAxxx... | fx fy fz | results file |
coupler | COUxxx... | fx1 fy1 fz1 tx1 ty1 tz1 fmag1 tmag1 fx2 fy2 fz2 tx2 ty2 tz2 fmag2 tmag2 fx3 fy3 fz3 tx3 ty3 tz3 fmag3 tmag3 | results file |
sforce | SFOxxx... | fx fy fz tx ty tz fmag tmag | results file |
spring damp | SPRxxx... | fx fy fz tx ty tz fmag tmag | results file |
bushing | BUSxxx... | fx fy fz tx ty tz fmag tmag | results file |
beam | BEAxxx... | fx fy fz tx ty tz fmag tmag | results file |
field | FIExxx... | fx fy fz tx ty tz fmag tmag | results file |
user request | UREQxxx... | u1 u2 u3 u4 u5 u6 u7 u8 | results file |
request | REQxxx... | x y z r1 r2 r3 mag amag | request file |
ucon | (not implemented) | | |
8. Once the unit type is set, Adams View can perform the proper unit conversion on the data.
If the value for this parameter is calculated, Adams View will try to determine the units to use for this operation. For example, if velocities are ADDed (length/time), the calculated units for the new result set component will be a velocity (length/time). If the derivative of a velocity is taken, the calculated units will be acceleration (length/time**2).
Adams View, at this time, can only handle calculated units with a maximum exponent for the base units (force, length, mass, time) is plus or minus four (4). For example, if a result set component with the units (length/time**3) is multiplied with a result set component with the same units, The calculated units would be (length**2/time**6). Since the exponent is greater than 4, Adams View will use NO_UNITS and issue a warning.