numeric_results create interpolation
Allows you to create an evenly spaced sampling of the component.
This operation does not assume the points are evenly spaced, it uses the "TIME" or "FREQUENCY" component as the dependent variable.
The "TIME" or "FREQUENCY" component is also interpolated to be evenly spaced. The new TIME/FREQUENCY component is stored with the new component
Format:
numeric_results create interpolation |
|---|
result_set_component_name = | an existing component |
new_result_set_component_name = | a new component |
interpolate_type = | interpolation_type |
number_of_points = | integer |
units = | units_type_with_calc |
Example:
numeric_results create interpolation & |
|---|
result_set_component_name = | time & |
new_result_set_component_name = | rsc__1 & |
units = | time |
Description:
Parameter | Value Type | Description |
|---|
result_set_component_name | An Existing Component | Identifies the component of an existing result set. |
new_result_set_component_name | A New Component | Allows you to identify where the new data components are to be stored. |
interpolate_type | Interpolation_Type | Specifies the three methods used to interpolate the result set component. |
number_of_points | Integer | Specifies the number of interpolation points used in the fitting of data contained in a result set component. |
units | Units_Type_With_Calc | Allows you to specify the type of units to be used for the new result set component. |
Extended Definition:
1. The component 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) | | |
2. 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 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) | | |
3. Once the unit type is set, Adams View can perform the proper unit conversion on the data. If the value for the “units” parameter is calculate, Adams View tries to determine the units to use for this operation. For example, if velocities are added (length/time), then the calculated “units” parameter for the new result set component is velocity (length/time). If the derivative of a velocity is taken, the calculated “units” parameter is acceleration (length/time**2).
Adams View can only handle calculated units with a maximum exponent for the base units (force, length, mass, time) of plus or minus four. For example, if a result set component with the units (length/time**3) is multiplied with a result set component having the same units, it gives the calculated units (length**2/time**6). Because the exponent of time is greater than four, Adams View uses no_units and issues a warning.
4. The three methods used to interpolate the result set component:
linear - uses the first order LaGrangian interpolation
cubic - uses the second order LaGrangian interpolation
akima - uses the Akima method, as documented in Journal of the Association Computing Machinery Vol 17, No 4, October 1970.
5. This curve fitting operation could be desired by the user, in preparation for an FFT operation, etc.
If the interpolation operation is in preparation for an FFT, then the number of points must be an even power of two. (e.g. 256, 512, 1024, etc.).
This is an optional parameter and if not entered, will be set to 1024.
If entered, the NUMBER_OF_POINTS parameter must be a positive integer.
Also, once changed by the user, the new value will be remembered and used as default the next time the parameter is needed.